From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-06-09 09:23:30
Vladimir Prus <ghost_at_[hidden]> writes:
> David Abrahams wrote:
>> "Konstantin M. Litvinenko" <gclbb-jamboost_at_[hidden]> writes:
>> > Hello, Vladimir!
>> > You wrote on Mon, 9 Jun 2003 16:42:24 +0400:
>> > VP> I think the idea is that "using msvc" and the like occurs in
>> > VP> user-config.jam and site-config.jam -- and that those files don't
>> > VP> declare toolsets which are not installed.
>> > I know that, but as for me it is bad solution, or maybe i have missed
>> > somithing :). We use boost.Build as main build system. Some of projects
>> > require only subset of libraries and compilers that should be in
>> > user-config.jam. So when someone will do cvs up and try to build project,
>> > it will not builds, coz of lack of libraries and compilers specified in
>> > user-config.jam for all projects.
>> That's a very good point. I think we may need a feature attribute
>> something like "unchecked" which means that any value is acceptable.
> Isn't that a bit too sloppy? I was thinking about
> feature.extend-if-not-yet-extended-with-this-value toolset : msvc ;
Very cumbersome for users, though.
> This rule can be used in project-root.jam to make sure that
> <toolset>msvc is valid, regardless of whether you have in
> configured, or not.
Sounds awfully hard-nosed. I'd like something easier-to-understand.
Maybe something like:
using msvc : : optional ;
-- 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