[C++-sig] How to configure makefile for different build platforms

[Jim Bosch]

On 10/06/2011 10:02 AM, David Aldrich wrote:
>
>
>> -----Original Message-----
>> From: cplusplus-sig-bounces+david.aldrich=emea.nec.com at python.org
>> [mailto:cplusplus-sig-bounces+david.aldrich=emea.nec.com at python.org]
>> On Behalf Of Wichert Akkerman
>> Sent: 06 October 2011 14:51
>> To: cplusplus-sig at python.org
>> Subject: Re: [C++-sig] How to configure makefile for different build platforms
>>
>> On 10/06/2011 03:09 PM, David Aldrich wrote:
>>>> pkg-config does not use Debian packages names. Try using "python" for
>>>> the current standard python 2 version, or pythonX.Y for specific
>>>> versions. Boost appears to be installed in a standard location, so
>>>> doesn't need any special compiler or linker options.
>>> Thanks but --list-all only lists notify-python and  dbus-python.
>>
>> Odd. Try python2.6-config.
>
> No, that's not there either.
>
> http://bugs.python.org/issue3585  suggests that pkg-config support in Python was not added until at least 2.6.  Perhaps it did not make it in the version I have.  Besides, I also wanted it to detect Python 2.4. So this method won't work unfortunately.

You can also extract this information from various methods in the 
distutils package.  Even if you aren't using distutils to control the 
build, you could ask Python itself to print out the configuration 
variables.  For instance:

python -c "import distutils.sysconfig; print 
distutils.sysconfig.get_python_inc()"

That should give you the Python include directory.  There are other 
methods to get library names, compiler flags, and other things.

Jim