From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-09-14 16:43:04
Alexey Pakhunov wrote:
> See my comments below.
> Andrey Melnikov wrote:
> In fact instead of:
> lib a : a.cpp /win32//user32 ;
> we may use project name only:
> lib a : a.cpp /win32 ;
> As result all libraries will be included to the command line. We can use
> this for header-only SDKs. We can define some kind of zero-library
> target for this purpose and use it instead of "lib xxx ;" in the project.
AFAIK there is /boost//headers for the header-only Boost libraries. We
can recommend 'headers' target name for general usage. BTW, Boost itself
is an SDK.
>>How should we specify different Platform SDK
>>configurations? Should we use features or projects?
> Can one module (win32.jam) define several projects?
At the moment it can't :(
> If the answer is
> 'yes' than we can define 'win32-builtin', 'win32-external', etc
> projects. 'builtin' and 'external' will be different configurations
> configured via 'toolset.usage'. BTW we still need a way to pass PSDK
> path to win32.jam.
Multiple projects won't help. See the list of configuration requirements
in my answer to Vladimir.
>>At the moment I have to specify 174 lines like
>>lib user32 ;
>>lib kernel32 ;
> I think GLOB plus filtering out libcXX.lib will work.
The CRT isn't there in case of built-in SDK so I didn't filter.
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