Re: [jamboost] Autolinking and Boost.Build

From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-08-03 15:25:07

John Maddock wrote:

> 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.

I have a patch for this bug. It is already on the list, but I need to 
make a diff against last CVS and resubmit it again. I'll get to it as 
soon as we finish with MSVC patch by Aleksey Pakhunov.
> 
> 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 :-)

There are also other potentially dangerous cases like building a DLL 
with a static runtime, linking two projects with different runtime-link 
together etc.

> 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 :-)

I like "shared" more, because DLLs on Windows are rarely "dynamically 
loaded". I'd call loading by system loader (even if delayed) is 
"static", unlike loading by LoadLibrary() call. :)

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

For MSVS it isn't important until we stop using setenv.bat. I think 
there are reasons to stop using these scripts at some point in the future.

We'll try to address this issue during the review of Aleksey's patch. 
The patch includes new <mspsdk> feature which basically changes 
<sysinclude> path from built-in to external Microsoft Platform SDK.

Andrey