Re: [boost] Python paths in linux_gcc.mak?

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-27 16:37:31

I'm not maintaining those makefiles; I'm not sure that anyone is. The
official way to build/test Boost is by using Boost.Build.

-Dave

----- Original Message -----
From: "Craig Rodrigues" <rodrigc_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Wednesday, February 27, 2002 3:13 PM
Subject: [boost] Python paths in linux_gcc.mak?

> Hi,
>
> In linux_gcc.mak, why is the following set up this way:
>
> #PYEXE=PYTHONPATH=. /usr/bin/python
> #PYINC=-I/usr/include/python1.5
> #PYEXE=PYTHONPATH=. /usr/local/Python-1.5.2/bin/python
> #PYINC=-I/usr/local/Python-1.5.2/include/python1.5
> PYEXE=PYTHONPATH=. /usr/local_cci/Python-2.1.1/bin/python
> PYINC=-I/usr/local_cci/Python-2.1.1/include/python2.1
>
> It would be handy to have the commented out lines set as the
> defaut, because on many Red Hat Linux based systems,
> /usr/bin/python and /usr/include/python1.5 are the default
> locations of the standard install for these packages.
>
> This would make regression testing directly from CVS easier
> on Linux + gcc setups.
>
> Thanks.
> --
> Craig Rodrigues
> http://www.gis.net/~craigr
> rodrigc_at_[hidden]
>
> Info: http://www.boost.org  Send unsubscribe requests to:
<mailto:boost-unsubscribe_at_[hidden]>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>