Re: [jamboost] Autolinking and Boost.Build

From: John Maddock (john_at_[hidden])
Date: 2005-08-03 12:32:16

> Can you try with the attached patch?

It doesn't appear to make any difference.

I have a few issues more as well:

1) The static libraries aren't getting prefixed with "lib": this is needed 
to be able to give the static and dynamic libraries distinct names when they 
both end in ".lib" under Windows.

2) If I build with "<runtime-link>shared <threading>single" and msvc it goes 
ahead and builds.... a multithreaded build: there is no single threaded 
option for:

msvc with a dynamic runtime.
msvc 8 and any kind of runtime.

Rene managed to suppress this behaviour for bbv1, although it's not ideal as 
building with "<runtime-link>shared <threading>single" just causes nothing 
to happen, and some kind of warning would be nice :-)

3) I notice that bbv2 uses <runtime-link>shared rather than 
<runtime-link>dynamic as bbv1, although once you're used to it I kind of 
like the former as it's shorter :-)

4) I notice that there is still no <sysinclude> option. Not sure if this is 
important or not.

5) bbv2 is quite slow in loading: it seems to be scanning jamfiles it 
doesn't need to. For example even if I'm just building the docs I'm still 
seeing the Regex and Python Jamfiles getting scanned. This is bad for a 
number of reasons:

* Users really don't need to see informative messages from regex and python 
unless they're building/using those libraries.
* It has the potential for trouble: if one library author breaks their 
Jamfile, everything stops working.
* It doesn't scale: imagine an arbitrarily large number of arbitrarily 
complex projects being added to Boost. Presumably it would take an 
arbitrarily large amount of time before bjam actually did anything?

Thanks again for your help, John.