Hi, all.
I found a small problem in build.xml that broke the build. In the "cxxtest" target, the path of the python executable was set to /target/python/python.exe . The problem with that is that the python you want at build time is the one that is native on your build machine. So on Linux, it would be /usr/bin/python or whatever. For win32/Mingw native builds, it would be preferable to add ${devlibs}/python to the PATH in mingwenv.bat rather than to explicitly invoke the one in /target/. Just "python" should be correct.
Can someome please commit this? I don't want to commit the cross-compile version and break native/mingw.
bob
On Tue, Jan 27, 2009 at 1:21 AM, Bob Jamison <rwjj@...127...> wrote:
I found a small problem in build.xml that broke the build. In the "cxxtest" target, the path of the python executable was set to /target/python/python.exe . The problem with that is that the python you want at build time is the one that is native on your build machine. So on Linux, it would be /usr/bin/python or whatever. For win32/Mingw native builds, it would be preferable to add ${devlibs}/python to the PATH in mingwenv.bat rather than to explicitly invoke the one in /target/. Just "python" should be correct.
Sorry - that was my change, for me "python" didn't work on a machine without any python so I changed it to the devlibs python. You can revert that change if it causes you problems.
-----Original Message----- From: bulia byak [mailto:buliabyak@...400...] Sent: dinsdag 27 januari 2009 8:27 To: Bob Jamison Cc: inkscape Subject: Re: [Inkscape-devel] Which python
On Tue, Jan 27, 2009 at 1:21 AM, Bob Jamison <rwjj@...127...> wrote:
I found a small problem in build.xml that broke the build. In the "cxxtest" target, the path of the python executable was set to /target/python/python.exe . The problem with that is that
the python
you want at build time is the one that is native on your build machine. So on Linux, it would be /usr/bin/python or whatever. For win32/Mingw native builds, it would be preferable to add ${devlibs}/python to the PATH in mingwenv.bat rather than to explicitly invoke the one in /target/. Just "python" should be correct.
Sorry - that was my change, for me "python" didn't work on a machine without any python so I changed it to the devlibs python. You can revert that change if it causes you problems.
${devlibs}/python is added to the path by mingwenv.bat. But that didn't work for Bulia, don't know why. For me, both work ('python' and '${devlibs}/python' ); without calling mingwenv.bat first, python is not found, after mingwenv.bat, it is found.
participants (3)
-
unknown＠example.com -
Bob Jamison -
bulia byak