Hi Joerg, hi Laurent , > yes, the pythonloader.dll is linked to pyuno.dll. The standard windows > import lib mechanism looks for pyuno.dll only and will not find a pyuno.pyd. > > There are 2 ways to solve this.
Thank you very much. > - The build process itself must create a pyuno.pyd instead of a > pyuno.dll. The created import lib will then look for a pyuno.pyd. > > - create a wrapper pyuno.pyd shared library, which has only one method > (initpyuno()), the implementation of the method loads pyuno.dll > dynamically (using win32 LoadLibrary() function) and calls the > initpyuno() function implemented in pyuno.dll. pyuno.pyd thus would just > be a proxy for pyuno.dll I write a source file pyuno_loadwrapper.c, to load the pyuno.dll using LoadLibrary() function and call the initpyuno() function. I change the makefile, now the pyuno_loadwrapper.obj has been built, but I don't know how to generate the wrapper pyuno.pyd shared library using the pyuno_loadwrapper.obj . Could you give me some advice? Thanks Liyuan > Maybe the second step is a little easier to implement. There is a > special handling already for the unix pyuno shared library (see the > PYUNO_MODULE target in the makefile and the pyuno_dlopenwrapper.c source > file). > > Bye, > > Joerg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
