Differentiating $(EXT) between build and install
Folks, there's so many bug reports and questions about needing the --with-suffix on Mac OS X when you're building on an HFS+ filesystem that I'd like to fix this. The warning in configure doesn't cut it because it gets lost in all the other messages. What I'd like to do is have a separate Makefile variable, BUILDEXT, that gives the extension to use for python while it lives in the build directory. It would default to EXT, except if on HFS+ when EXT is empty. But this might change a couple of other things as well, so my question is: is this an acceptable change so late in the beta stage? -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | ++++ see http://www.xs4all.nl/~tank/ ++++
Jack Jansen wrote:
Folks, there's so many bug reports and questions about needing the --with-suffix on Mac OS X when you're building on an HFS+ filesystem that I'd like to fix this. The warning in configure doesn't cut it because it gets lost in all the other messages.
What I'd like to do is have a separate Makefile variable, BUILDEXT, that gives the extension to use for python while it lives in the build directory. It would default to EXT, except if on HFS+ when EXT is empty.
But this might change a couple of other things as well, so my question is: is this an acceptable change so late in the beta stage?
Wouldn't tweaking the setup.py to introduce a special case for MacOS be much simpler ? (adding BUILDEXT would need patching of the Makefile.pre.in process as well as distutils) -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Consulting & Company: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
participants (2)
-
Jack Jansen -
M.-A. Lemburg