From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-09-14 14:01:44
See my comments below.
Andrey Melnikov wrote:
> What is "an SDK"? Is it more than just a library/collection of
It is a collection of related headers, libraries, binaries. Minimal SDK
may contain only headers, for example - WTL. This can be an issue.
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.
> What other SDKs do we have?
WTL? I'm not sure about it.
> Should we have STL and Platform
> SDK handled the same way?
> How should we specify different Platform SDK
> configurations? Should we use features or projects?
Can one module (win32.jam) define several projects? 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.
> At the moment I have to specify 174 lines like
> lib user32 ;
> lib kernel32 ;
I think GLOB plus filtering out libcXX.lib will work.
> MY_INIT RULE LOOKS LIKE A HACK
'msvc.init' rule looks even worse. :-)
Best regards/Venlig hilsen,
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