> > How would I get that from the command line please?
>
> python -c "import sys; print '%d.%d' % sys.version_info[:2]"
Fantastic. Thank you very much.
David
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinf
On 10/06/2011 05:17 PM, David Aldrich wrote:
> sys.version_info
How would I get that from the command line please?
python -c "import sys; print '%d.%d' % sys.version_info[:2]"
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.py
> sys.version_info
How would I get that from the command line please?
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
On 10/06/2011 05:08 PM, David Aldrich wrote:
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 dis
> 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
> distutil
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 app
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
>
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 option
> 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 no
On 10/06/2011 02:55 PM, David Aldrich wrote:
On Ubuntu you can call pkg-config to figure out the right compiler and linker
options for both Boost and Python. I would expect CentOS to support that as
well.
Hi Wichert
Thanks for your suggestion. However, on my Ubuntu system:
pkg-config --list-a
> On Ubuntu you can call pkg-config to figure out the right compiler and linker
> options for both Boost and Python. I would expect CentOS to support that as
> well.
Hi Wichert
Thanks for your suggestion. However, on my Ubuntu system:
pkg-config --list-all
lists neither python-dev not libboost
On 2011-10-5 18:12, David Aldrich wrote:
Hi
I have a C++ application that uses Boost.Python. We build it on Centos
5.3, with Python 2.4 and Boost 1.34.
Our makefile uses explicit paths to find Python and Boost. For the
headers we use:
PYTHON = /usr/include/python2.4
BOOST_INC = /usr/include/b
12 matches
Mail list logo
