From: David Abrahams (dave_at_[hidden])
Date: 2003-03-05 10:46:47
Vladimir Prus <ghost_at_[hidden]> writes:
>> In my system, the default behavior is the same as Boost, but there
>> are two ways of modifying it. Say project exe/foo depends on
>> project lib/bar. First, I can specify in project lib/bar that its
>> default configuration is "release" instead of the configuration of
>> its super-project.
> Boost.Build allows the same via "requirements".
It really sounds to me as though he's talking about default-build
rather than requirements. Am I missing something?
>> Second, I can explicitly specify in project
>> exe/foo that the "release" config of lib/bar is to be linked in the
>> "debug" configuration of exe/foo (more precisely, I derive a new
>> configuration from "debug" and alter the new config, but either way
>> works for me).
> Yes, this is possible as well in V2. For example
> exe main : main.cpp lib/<optimization>speed ;
>> 3 - May be problem with non-GCC compilers on Cygwin? Are there
>> problems building with MSVC on Cygwin with bjam/Boost.Build?
> I can't comment, since I'm not a Windows person. Maybe Dave can add.
I have not tried to build with MSVC on Cygwin, though I think others
have succeeded with this under v1.
I don't see why there should be a major problem; the Boost.Build code
may need to be tweaked a little to support it, but it seems as though
it should work.
The issue of supporting non-cygwin compilers like MSVC under cygwin
is essentially the same as that of supporting Cygwin compilers like
gcc under NT... and we do handle that already.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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