This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Matthias.Braun
Recipients Joe.Neeman, Matthias.Braun, doko, erickt, georg.brandl, loewis, sacha, terry.reedy
Date 2013-03-28.11:44:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1364471062.63.0.657428462833.issue3290@psf.upfronthosting.co.za>
In-reply-to
Content
It's less of a problem when building python extenions, where you are probably fine with using "just the same" as the installed python.

However in my case I am embedding python as a scripting language into another application. So there is very few python related code and alot of other code. The python-config script "injecting" unnecessary build flags that in fact even change things (-DNDEBUG) is very annoying as it changes all the non-python code too.

A simple thing like the --includes that just outputs the -I flags would be the best solution IMO. But to have this working you would need to have a guarantee that there is no actual code in the form of #define / inline functions in the headers which potentially breaks if you use different flags from the python library. In fact --includes is what I am using now, I just hope that I won't hit any of the preproc macros by accident...
History
Date User Action Args
2013-03-28 11:44:22Matthias.Braunsetrecipients: + Matthias.Braun, loewis, georg.brandl, terry.reedy, doko, erickt, sacha, Joe.Neeman
2013-03-28 11:44:22Matthias.Braunsetmessageid: <1364471062.63.0.657428462833.issue3290@psf.upfronthosting.co.za>
2013-03-28 11:44:22Matthias.Braunlinkissue3290 messages
2013-03-28 11:44:21Matthias.Brauncreate