[Pythonmac-SIG] The PantherPythonFix installer and C++ extensions
Bob Ippolito
bob at redivi.com
Thu Dec 30 18:49:11 CET 2004
On Dec 30, 2004, at 11:44 AM, Jack Jansen wrote:
>
> On 30-dec-04, at 10:02, Ronald Oussoren wrote:
>>
>> In the quick-and-dirty-hacks category: you could write two simple
>> shell-scripts that start the compiler with the right environment
>> variables:
>>
>> run-cc:
>> #!/bin/sh
>>
>> env MACOSX_DEPLOYMENT_TARGET=10.3 gcc "${@}"
>>
>> run-c++:
>> #!/bin/sh
>> env MACOSX_DEPLOYMENT_TARGET=10.3 gcc "${@}"
>
> Here's an even better idea (I think), please think about whether it
> would fly:
> In the Makefile we not only change LDSHARED and BLDSHARED to start
> with " env MACOSX_DEPLOYMENT_TARGET=10.3", but also CXX. That'll teach
> distutils to fiddle with our command lines:-)
>
> Only question is: would this have any adverse side efffects?
Same problem. If you replace the first word, you'll end up with either
"g++ gcc..." or "g++ MACOSX_DEPLOYMENT_TARGET=10.3 gcc..." depending on
whether "env" was used or not.
-bob
More information about the Pythonmac-SIG
mailing list