PyXML on MacOSX 10.3
hi i have some trouble getting this to work..
when i want to build setup.py i get the following error:
Traceback (most recent call last): File "setup.py", line 127, in ? config_h_vars = parse_config_h(open(config_h)) IOError: [Errno 2] No such file or directory: '/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3/pyconfig.h'
i have no idea how to go on from that...
am I missing something else? there is no /include-Folder @ ../System/Library/Frameworks/Python.framework/Versions/2.3/ and i don't have pyconfig.h in the python2.3 - folder (which is @ ..Versions/2.3/lib/) ..if this info is of any help..
thanks for any help manuel
Hi Manuel
On 16 déc. 05, at 23:11, Manuel Kostka wrote:
when i want to build setup.py i get the following error:
Traceback (most recent call last): File "setup.py", line 127, in ? config_h_vars = parse_config_h(open(config_h)) IOError: [Errno 2] No such file or directory: '/System/Library/ Frameworks/Python.framework/Versions/2.3/include/python2.3/pyconfig.h'
i have no idea how to go on from that...
am I missing something else? there is no /include-Folder @ ../ System/Library/Frameworks/Python.framework/Versions/2.3/ and i don't have pyconfig.h in the python2.3 - folder (which is @ ..Versions/2.3/lib/) ..if this info is of any help..
I read somewhere that you had to set an environment variable before compiling pyXML. It sets the version of Mac OS X you build for and so probably sets the paths correctly (2.3 is the version of python shipped with Tiger, it might be different on Panther). You can find instructions in the wiki: http://wiki.inkscape.org/cgi-bin/wiki.pl?CompilingMacOsX basically, in bash syntax you need to write: MACOSX_DEPLOYMENT_TARGET=10.3 export MACOSX_DEPLOYMENT_TARGET before building setup.py.
Before that it would be useful if you tested a build I've made in order to see if we can distribute it as a dmg. The dmg is here: http://jo.irisson.free.fr/dropbox/inkscape/PyXML.dmg instructions are in the README
Thanks in advance for testing.
JiHO --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- http://jo.irisson.free.fr/
On 12/17/05, jiho <jo.irisson@...400...> wrote:
On 16 déc. 05, at 23:11, Manuel Kostka wrote:
When I want to build setup.py I get the following error:
Traceback (most recent call last): File "setup.py", line 127, in ? config_h_vars = parse_config_h(open(config_h)) IOError: [Errno 2] No such file or directory: '/System/Library/ Frameworks/Python.framework/Versions/2.3/include/python2.3/pyconfig.h'
As you can see, the framework has an include directory within it; but you shouldn't need to know about that as we specify the framework names and search paths in their own right.
i have no idea how to go on from that...
am I missing something else? there is no /include-Folder @ ../ System/Library/Frameworks/Python.framework/Versions/2.3/ and i don't have pyconfig.h in the python2.3 - folder (which is @ ..Versions/2.3/lib/) ..if this info is of any help..
The @ symbols probably refer to the executable path that will exist when the app has been 'bundled'; although you would very definitely need to take this into account when creating your own frameworks, when using someone else's, it si just a matter of adding it to the project and checking that the files are copied (which is usually, but not always, necessary) as part of the build operations.
I read somewhere that you had to set an environment variable before compiling pyXML. It sets the version of Mac OS X you build for and so probably sets the paths correctly (2.3 is the version of python shipped with Tiger, it might be different on Panther). You can find instructions in the wiki: http://wiki.inkscape.org/cgi-bin/wiki.pl?CompilingMacOsX basically, in bash syntax you need to write: MACOSX_DEPLOYMENT_TARGET=10.3 export MACOSX_DEPLOYMENT_TARGET before building setup.py.
JiHO, I will verify the MacOS instructions on the Wiki page and perhaps make them a bit clearer. If one is building an application to run on the same system as it is being built on, it shouldn't be necessary to do anything other than use the defaults.
Ben.
participants (3)
-
Ben Fowler -
jiho -
Manuel Kostka