Hi,

on windows, python does not come with makefiles but instead with msdev
projects.

In order to make python buildable in OOo build environment under
windows, I generated makefiles via the msdev

These new makefiles are part of the patch file. You will need to replace
them for 2.5.

Please see

http://external.openoffice.org/ext_dmake.html

on how you create such patchfiles. What you need to do is

- create new makefiles with msdev and make sure, that they would work in
ooo buildenvironemnt
- dmake create_clean
 (will just extract the tarball)
- dmake patch
 (would apply the old patch file. It might be, that this does not make
sense, I would probably prefer to leave this step away and evaluate by
hand, which patchfiles still make sense)
- Apply your new patches. For every new file you add, you will need to
extend the PYPROJECTS list in the makefile.mk
- dmake create_patch will create a new patch file. Then you can test,
whether a fresh new build will give you what you want.

This is just a very rough explanation, and it is certainly not
completely understandable, but you have to work your way through it.
Exchanging python is NOT an easy task at all and it is even harder, when
you are unfamilar with ooo build environement ...


Bye,

Joerg


blueeagle wrote:
> hi,all
>  I am working on the the pyUNO bridge. the first task would be migrate to 
> python2.5 instead of actual 2.3.5. I have migrated and have complied on linux 
> sucessful. But there are build issues when I test to build on Windows.As 
> follows:
>    cl.exe /nologo /MD /W3 /GX /Zi /O2 /I "..\Include" /I "..\PC" /D "NDEBUG
> " /D "WIN32" /D "_WINDOWS" /D "USE_DL_EXPORT" 
> /Fp".\x86-temp-release\pythoncore\
> pythoncore.pch" /YX /Fo".\x86-temp-release\pythoncore\\" 
> /Fd".\x86-temp-release\
> pythoncore\\" /FD /Zm200 /c ..\Python\exceptions.c
> exceptions.c
> c1 : fatal error C1083: Cannot open source file: '..\Python\exceptions.c': No 
> such file or directory
> NMAKE : fatal error U1077: 'cl.exe' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: 'C:\progra~1\micros~2.net\vc7\bin\nmake.exe' : 
> return code '0x2'
> Stop.
> dmake.exe:  Error code 130, while making 
> '.\wntmsci10.pro\misc\build\so_built_so_python'
> '---*tg_merge.mk*---'
> 
> How to solve the build issue? 
> I searched the python2.5 and find there are indeed no "exception.c" in that 
> directory but exist in another directory( \Objects\exceptions.c). I copied 
> that file to \python . that can solve the issue , but another issue is as 
> follows:
> 
> c1 : fatal error C1083: Cannot open source file: '..\Modules\md5c..c': No 
> such file or directory. 
> 
> I searched the python2.5 and can not find the file "md5c.c" anywhere. But the 
> file "md5c.c" can be found in that directory in python2.3.
> 
> I have build the python2.5 on Windows(VC6.0) the build issues are as follows:
> fatal error C1083: Cannot open source file: 
> 'D:...\Python-2.5\Python\exceptions.c': No such file or directory
> fatal error C1083: Cannot open source file: 
> 'D:...\Python-2.5\Modules\md5c.c': No such file or directory
> fatal error C1083: Cannot open source file: 
> 'D:...\Python-2.5\Modules\structmodule.c': No such file or directory
> 
> what should I do now?
> ----
> 刘涛
> 
> Beijing Redflag CH2000 Software Co., Ltd. 
> Address: 北京亦庄经济技术开发区地盛北街 1号A区3号楼 
> Postalcode: 100176 
> Tel: 8610-58022828-605
> Mobile: 13126869000 
> Email: [EMAIL PROTECTED] 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to