From: Walter Landry (wlandry_at_[hidden])
Date: 2006-04-24 16:28:38
David Abrahams <dave_at_[hidden]> wrote:
> Walter Landry <wlandry_at_[hidden]> writes:
> > So different directories would use different compilers. I configure
> > once (with all sorts of esoteric commands and locations), but build
> > many times.
> Oh, you want per-directory sticky selection of default toolset.
> That's an interesting idea, and probably easy to add.
In particular, simply running "make" or "bjam" does no autodetection.
I don't want things to change just because I installed a new compiler
or new python headers. For example, the current system prints out
lots of warnings about Python whenenver I run bjam.
> > It also does not help that this is not at all like the instructions
> > given on the webpage. The webpage says that I can run configure in
> > libs/config and copy user.hpp to the right place.
> Wow, you're pretty confused I think.
Evidently. I followed "Getting Started", read through the whole thing
before seeing "Additional Steps" at the end, which pointed me to the
non-functional configure script.
> On the other hand, you can get a working *nix configure/make/make
> install script for all of boost at
> http://www.boost-consulting.com/boost/configure. It will go out at
> the top level of the next release.
This file is already there in 1.33.1. It depends on bjam to do the
autodetection during "make". It should do the autodetection during
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk