py2exe

Here's a batch file to build the dll:

-------------------------------------------------------
del /s /f /q dist >nul
del /s /f /q build >nul

echo Compiling .idl file:
midl MyTypeLib.idl
if errorlevel 1 goto error

echo Building distribution...
python.exe setup.py py2exe --packages encodings --bundle 2
if errorlevel 1 goto error

cd dist
regsvr32 testComServer.dll

goto end

:error
echo ERROR
:end



On Tue, May 19, 2009 at 12:25 PM, H.R.Gartenbauer <gartenbauer@...:

>
> I'm trying to build a com server as a stand-alone dll using comtypes and
> py2exe, using sample code found in the comtypes tutorial.
> The stand-alone DLL builds fine with --bundle 2.
> But the DLL cannot register.
> Using "regsvr32 testComServer.dll" this debug trace is produced:
>
>   Traceback (most recent call last):    File "boot_ctypes_com_server.py",
> line 52, in <module>
>     File "zipextimporter.pyc", line 82, in load_module
>     File "MyTypeLib.pyc", line 15, in <module>
>     File "comtypes\client\_generate.pyc", line 97, in GetModule
>     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
>     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in
> GetResult
>   WindowsError
>   :
>   [Error -2147312566] Error loading type library/DLL
>
>   Traceback (most recent call last):
>     File "<string>", line 1, in <module>
>   NameError
>   :
>   name 'DllRegisterServer' is not defined
>
> The regsvr32 error Message Box says:
>   DllRegisterServer in testComServer.dll failed
>   Return code was: 0x80040201
>
> Below are included the files to recreate the problem.
> The server works if  just running 'MyTypeLib.py /registerserver', and a
> small test program (tester.py, below) runs fine.
> But the stand alone DLL will not register.
>
> What am I doing wrong? Below are included the files to recreate the
> problem.
>
> I've seen that 'loewis' path "\loewis\25\python\Modules\_ctypes\callproc.c"
> before when testing comtypes in python without py2exe, and cleaning out the
> comtypes/gen directory seems to fix it.
>
> I realize this may not be a py2exe problem. Do py2exe and comtypes work
> together?
>
> Thanks,
> Gartenbauer
>
>
> ---------------------------
> file MyTypeLib.idl:
>
> import "oaidl.idl";
> import "ocidl.idl";
>
> [
>         uuid(D258EBF0-6247-4590-AF9E-7326FD975D61),
>         dual,
>         oleautomation
> ]
> interface IMyInterface : IDispatch {
>         [id(1)] HRESULT MyMethod([in] INT a, [in] INT b, [out, retval] INT
> *presult);
> };
>
> [
>       uuid(4E340492-C4BF-4AC8-B9F1-8816C8FE8C8A)
> ]
>
> library MyTypeLib
> {
>         importlib("stdole2.tlb");
>
>         [uuid(5B5A8EAA-9877-419D-BA67-960257A0A5B2)]
>               coclass MyObject {
>               [default] interface IMyInterface;
>         };
> };
>
> ---------------------------
> file MyTypeLib.py:
>
> from ctypes import *
> import comtypes
> import comtypes.server.localserver
>
> # force inclusion by p2exe of these in the DLL
> from win32com import *
> from pythoncom import *
> from win32com.server import *
> from win32com.server.util import *
> from win32com.server.policy import *
> from pywintypes import *
>
> from comtypes.client import GetModule
> # generate wrapper code for the type library, this needs
> # to be done only once (but also each time the IDL file changes)
> GetModule("MyTypeLib.tlb")
>
> from comtypes.gen.MyTypeLib import MyObject
>
> class MyObjectImpl(MyObject):
>     # registry entries
>     _reg_threading_ = "Both"
>     _reg_progid_ = "MyTypeLib.MyObject.1"
>     _reg_novers_progid_ = "MyTypeLib.MyObject"
>     _reg_desc_ = "Simple COM server for testing"
>     _reg_clsctx_ = comtypes.CLSCTX_INPROC_SERVER |
> comtypes.CLSCTX_LOCAL_SERVER
>     _regcls_ = comtypes.server.localserver.REGCLS_MULTIPLEUSE
>
>     # Note the 'this' second parameter
>     def MyMethod(self, this, a, b, presult):
>         presult[0] = a + b
>         return 0
>
>
> if __name__ == "__main__":
>     from comtypes.server.register import UseCommandLine
>     UseCommandLine(MyObjectImpl)
>
> ---------------------------
> file setup.py:
>
> import py2exe
> from distutils.core import setup
>
> MyTypeLib = dict(
>     modules = ["MyTypeLib"],
>     other_resources = [("TYPELIB", 1, file(r"MyTypeLib.tlb",
> "rb").read())],
>     dest_base = r"testComServer"
>     )
>
> setup(name="MyTypeLib",
>       ctypes_com_server = [MyTypeLib],
>       zipfile=None,
>       )
>
> ---------------------------
> file tester.py
>
> from comtypes.client import CreateObject
> x = CreateObject("MyTypelib.MyObject")
> print x
> print x.MyMethod(42, 5)
>
>
>

H.R.Gartenbauer schrieb:
> I'm trying to build a com server as a stand-alone dll using comtypes and
> py2exe, using sample code found in the comtypes tutorial.
> The stand-alone DLL builds fine with --bundle 2.
> But the DLL cannot register.
> Using "regsvr32 testComServer.dll" this debug trace is produced:
> 
>   Traceback (most recent call last):    File "boot_ctypes_com_server.py",
> line 52, in <module>
>     File "zipextimporter.pyc", line 82, in load_module
>     File "MyTypeLib.pyc", line 15, in <module>
>     File "comtypes\client\_generate.pyc", line 97, in GetModule
>     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
>     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in
> GetResult
>   WindowsError
>   :
>   [Error -2147312566] Error loading type library/DLL
> 
>   Traceback (most recent call last):
>     File "<string>", line 1, in <module>
>   NameError
>   :
>   name 'DllRegisterServer' is not defined
> 
> The regsvr32 error Message Box says:
>   DllRegisterServer in testComServer.dll failed
>   Return code was: 0x80040201

If you look into the first traceback, you can see the problem:
>     File "zipextimporter.pyc", line 82, in load_module
>     File "MyTypeLib.pyc", line 15, in <module>
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     File "comtypes\client\_generate.pyc", line 97, in GetModule
>     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
>     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in

Line 15, on MyTypeLib.py, is this one:

   12 from comtypes.client import GetModule
   13 # generate wrapper code for the type library, this needs
   14 # to be done only once (but also each time the IDL file changes)
-> 15 GetModule("MyTypeLib.tlb")

This line tries to load the type library FILE MyTypeLib.tlb, which
is not present in the current directory.  Also, calling GetModule('MyTypeLib.tlb')
is unneeded anyway because the wrapper module that it would generate IS
already inside your dll, put there by py2exe.

So, the simplest thing would be to delete this line from your script.

BTW:  You import a lot of modules into your MyTypeLib.py script, they are also unneeded:

> # force inclusion by p2exe of these in the DLL
> from win32com import *
> from pythoncom import *
> from win32com.server import *
> from win32com.server.util import *
> from win32com.server.policy import *
> from pywintypes import *

comtypes doesn't use or need anything from pywin32/win32com/pythoncom, so you
should delete these lines.

> I've seen that 'loewis' path "\loewis\25\python\Modules\_ctypes\callproc.c"
> before when testing comtypes in python without py2exe, and cleaning out the
> comtypes/gen directory seems to fix it.
> 
> I realize this may not be a py2exe problem. Do py2exe and comtypes work
> together?

This combination should work together, since both packages are by the same author ;-).

> Thanks,
> Gartenbauer

Thomas

Thomas,

I removed the lines as you suggested and now the DLL registers.
When the DLL is registered, the test script can't create an instance of the
object.

Traceback (most recent call last):
  File "c:\code\comtypes\tester.py", line 2, in <module>
    x = CreateObject("MyTypelib.MyObject")
  File "c:\Python25\lib\site-packages\comtypes\client\__init__.py", line
197, in CreateObject
    obj = comtypes.CoCreateInstance(clsid, clsctx=clsctx,
interface=interface)
  File "c:\Python25\lib\site-packages\comtypes\__init__.py", line 1119, in
CoCreateInstance
    _ole32.CoCreateInstance(byref(clsid), punkouter, clsctx, byref(iid),
byref(p))
WindowsError: exception: access violation reading 0x00000004

The access violation only occurs when the compiled DLL is registered, not
when the python code is registered.
Checking in the debugger, the arguments to CoCreateInstance are the same in
both cases.

I don't know my way around COM.
Thanks as always for your help.


On Wed, May 20, 2009 at 2:46 PM, Thomas Heller <theller@...> wrote:

> H.R.Gartenbauer schrieb:
> > I'm trying to build a com server as a stand-alone dll using comtypes and
> > py2exe, using sample code found in the comtypes tutorial.
> > The stand-alone DLL builds fine with --bundle 2.
> > But the DLL cannot register.
> > Using "regsvr32 testComServer.dll" this debug trace is produced:
> >
> >   Traceback (most recent call last):    File "boot_ctypes_com_server.py",
> > line 52, in <module>
> >     File "zipextimporter.pyc", line 82, in load_module
> >     File "MyTypeLib.pyc", line 15, in <module>
> >     File "comtypes\client\_generate.pyc", line 97, in GetModule
> >     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
> >     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in
> > GetResult
> >   WindowsError
> >   :
> >   [Error -2147312566] Error loading type library/DLL
> >
> >   Traceback (most recent call last):
> >     File "<string>", line 1, in <module>
> >   NameError
> >   :
> >   name 'DllRegisterServer' is not defined
> >
> > The regsvr32 error Message Box says:
> >   DllRegisterServer in testComServer.dll failed
> >   Return code was: 0x80040201
>
> If you look into the first traceback, you can see the problem:
> >     File "zipextimporter.pyc", line 82, in load_module
> >     File "MyTypeLib.pyc", line 15, in <module>
>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >     File "comtypes\client\_generate.pyc", line 97, in GetModule
> >     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
> >     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in
>
> Line 15, on MyTypeLib.py, is this one:
>
>   12 from comtypes.client import GetModule
>   13 # generate wrapper code for the type library, this needs
>   14 # to be done only once (but also each time the IDL file changes)
> -> 15 GetModule("MyTypeLib.tlb")
>
> This line tries to load the type library FILE MyTypeLib.tlb, which
> is not present in the current directory.  Also, calling
> GetModule('MyTypeLib.tlb')
> is unneeded anyway because the wrapper module that it would generate IS
> already inside your dll, put there by py2exe.
>
> So, the simplest thing would be to delete this line from your script.
>
> BTW:  You import a lot of modules into your MyTypeLib.py script, they are
> also unneeded:
>
> > # force inclusion by p2exe of these in the DLL
> > from win32com import *
> > from pythoncom import *
> > from win32com.server import *
> > from win32com.server.util import *
> > from win32com.server.policy import *
> > from pywintypes import *
>
> comtypes doesn't use or need anything from pywin32/win32com/pythoncom, so
> you
> should delete these lines.
>
> > I've seen that 'loewis' path
> "\loewis\25\python\Modules\_ctypes\callproc.c"
> > before when testing comtypes in python without py2exe, and cleaning out
> the
> > comtypes/gen directory seems to fix it.
> >
> > I realize this may not be a py2exe problem. Do py2exe and comtypes work
> > together?
>
> This combination should work together, since both packages are by the same
> author ;-).
>
> > Thanks,
> > Gartenbauer
>
> Thomas
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Py2exe-users mailing list
> Py2exe-users@...
> https://lists.sourceforge.net/lists/listinfo/py2exe-users
>

I wrote a simple C++ test program, using MFC to wrap the typelib in the DLL,
and successfully called the MyMethod function:

  IMyInterface tester; // IMyInterface wrapper created by MFC class wizard
from DLL
  tester.CreateDispatch("MyTypeLib.MyObject");
  long ret = tester.MyMethod(5,42);

The corresponding python code, using the registered DLL, generates the
access violation in the call to CreateObject:

from comtypes.client import CreateObject
x = CreateObject("MyTypelib.MyObject")
print x.MyMethod(42, 5)


On Thu, May 21, 2009 at 11:06 AM, H.R.Gartenbauer <gartenbauer@...:

> Thomas,
>
> I removed the lines as you suggested and now the DLL registers.
> When the DLL is registered, the test script can't create an instance of the
> object.
>
> Traceback (most recent call last):
>   File "c:\code\comtypes\tester.py", line 2, in <module>
>     x = CreateObject("MyTypelib.MyObject")
>   File "c:\Python25\lib\site-packages\comtypes\client\__init__.py", line
> 197, in CreateObject
>     obj = comtypes.CoCreateInstance(clsid, clsctx=clsctx,
> interface=interface)
>   File "c:\Python25\lib\site-packages\comtypes\__init__.py", line 1119, in
> CoCreateInstance
>     _ole32.CoCreateInstance(byref(clsid), punkouter, clsctx, byref(iid),
> byref(p))
> WindowsError: exception: access violation reading 0x00000004
>
> The access violation only occurs when the compiled DLL is registered, not
> when the python code is registered.
> Checking in the debugger, the arguments to CoCreateInstance are the same in
> both cases.
>
> I don't know my way around COM.
> Thanks as always for your help.
>
>
> On Wed, May 20, 2009 at 2:46 PM, Thomas Heller <theller@...> wrote:
>
>> H.R.Gartenbauer schrieb:
>> > I'm trying to build a com server as a stand-alone dll using comtypes and
>> > py2exe, using sample code found in the comtypes tutorial.
>> > The stand-alone DLL builds fine with --bundle 2.
>> > But the DLL cannot register.
>> > Using "regsvr32 testComServer.dll" this debug trace is produced:
>> >
>> >   Traceback (most recent call last):    File
>> "boot_ctypes_com_server.py",
>> > line 52, in <module>
>> >     File "zipextimporter.pyc", line 82, in load_module
>> >     File "MyTypeLib.pyc", line 15, in <module>
>> >     File "comtypes\client\_generate.pyc", line 97, in GetModule
>> >     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
>> >     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in
>> > GetResult
>> >   WindowsError
>> >   :
>> >   [Error -2147312566] Error loading type library/DLL
>> >
>> >   Traceback (most recent call last):
>> >     File "<string>", line 1, in <module>
>> >   NameError
>> >   :
>> >   name 'DllRegisterServer' is not defined
>> >
>> > The regsvr32 error Message Box says:
>> >   DllRegisterServer in testComServer.dll failed
>> >   Return code was: 0x80040201
>>
>> If you look into the first traceback, you can see the problem:
>> >     File "zipextimporter.pyc", line 82, in load_module
>> >     File "MyTypeLib.pyc", line 15, in <module>
>>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >     File "comtypes\client\_generate.pyc", line 97, in GetModule
>> >     File "comtypes\typeinfo.pyc", line 480, in LoadTypeLibEx
>> >     File "\loewis\25\python\Modules\_ctypes\callproc.c", line 757, in
>>
>> Line 15, on MyTypeLib.py, is this one:
>>
>>   12 from comtypes.client import GetModule
>>   13 # generate wrapper code for the type library, this needs
>>   14 # to be done only once (but also each time the IDL file changes)
>> -> 15 GetModule("MyTypeLib.tlb")
>>
>> This line tries to load the type library FILE MyTypeLib.tlb, which
>> is not present in the current directory.  Also, calling
>> GetModule('MyTypeLib.tlb')
>> is unneeded anyway because the wrapper module that it would generate IS
>> already inside your dll, put there by py2exe.
>>
>> So, the simplest thing would be to delete this line from your script.
>>
>> BTW:  You import a lot of modules into your MyTypeLib.py script, they are
>> also unneeded:
>>
>> > # force inclusion by p2exe of these in the DLL
>> > from win32com import *
>> > from pythoncom import *
>> > from win32com.server import *
>> > from win32com.server.util import *
>> > from win32com.server.policy import *
>> > from pywintypes import *
>>
>> comtypes doesn't use or need anything from pywin32/win32com/pythoncom, so
>> you
>> should delete these lines.
>>
>> > I've seen that 'loewis' path
>> "\loewis\25\python\Modules\_ctypes\callproc.c"
>> > before when testing comtypes in python without py2exe, and cleaning out
>> the
>> > comtypes/gen directory seems to fix it.
>> >
>> > I realize this may not be a py2exe problem. Do py2exe and comtypes work
>> > together?
>>
>> This combination should work together, since both packages are by the same
>> author ;-).
>>
>> > Thanks,
>> > Gartenbauer
>>
>> Thomas
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables
>> unlimited royalty-free distribution of the report engine
>> for externally facing server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Py2exe-users mailing list
>> Py2exe-users@...
>> https://lists.sourceforge.net/lists/listinfo/py2exe-users
>>
>
>

H.R.Gartenbauer schrieb:
> I wrote a simple C++ test program, using MFC to wrap the typelib in the DLL,
> and successfully called the MyMethod function:
> 
>   IMyInterface tester; // IMyInterface wrapper created by MFC class wizard
> from DLL
>   tester.CreateDispatch("MyTypeLib.MyObject");
>   long ret = tester.MyMethod(5,42);
> 
> The corresponding python code, using the registered DLL, generates the
> access violation in the call to CreateObject:
> 
> from comtypes.client import CreateObject
> x = CreateObject("MyTypelib.MyObject")
> print x.MyMethod(42, 5)

The problem is the unwanted interaction between the com object and the
com client in the one python interpreter they are using.

You could either use different Python versions for the client and the server,
or you use the '-b1' command line option for the py2exe build script, like this:
'python setup.py py2exe -b1'.

The '-b1' option creates a totally separated python interpreter.

Thomas

Thanks again.
I have another question: what do I need to change to build an out-of-process
(.exe) server instead of a DLL?
ctype_com_server in setup.py has to change, but to what?
Also _reg_clsctx_ in MyTypeLib.py?

On Mon, May 25, 2009 at 2:43 PM, Thomas Heller <theller@...> wrote:

> H.R.Gartenbauer schrieb:
> > I wrote a simple C++ test program, using MFC to wrap the typelib in the
> DLL,
> > and successfully called the MyMethod function:
> >
> >   IMyInterface tester; // IMyInterface wrapper created by MFC class
> wizard
> > from DLL
> >   tester.CreateDispatch("MyTypeLib.MyObject");
> >   long ret = tester.MyMethod(5,42);
> >
> > The corresponding python code, using the registered DLL, generates the
> > access violation in the call to CreateObject:
> >
> > from comtypes.client import CreateObject
> > x = CreateObject("MyTypelib.MyObject")
> > print x.MyMethod(42, 5)
>
> The problem is the unwanted interaction between the com object and the
> com client in the one python interpreter they are using.
>
> You could either use different Python versions for the client and the
> server,
> or you use the '-b1' command line option for the py2exe build script, like
> this:
> 'python setup.py py2exe -b1'.
>
> The '-b1' option creates a totally separated python interpreter.
>
> Thomas
>
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
> _______________________________________________
> Py2exe-users mailing list
> Py2exe-users@...
> https://lists.sourceforge.net/lists/listinfo/py2exe-users
>

H.R.Gartenbauer schrieb:
> Thanks again.
> I have another question: what do I need to change to build an out-of-process
> (.exe) server instead of a DLL?
> ctype_com_server in setup.py has to change, but to what?
> Also _reg_clsctx_ in MyTypeLib.py?

Yes, I *think* that you should have to change _reg_clsclx_ so that
it only contains CLSCTX_LOCAL_SERVER.  This restriction is no longer
present in the comtypes svn version.

Changes in the setup.py script, you don't have to use ctypes_com_server
anymore, out-of-process servers are started by the 'UseCommandLine(...)'
in your 'if __name__ == "__main__":' block.  You just use 'srcipts=[...]'
in the setup.py script.

Thomas