darwin and command-line / user-config.jam precedence

From: Ian Fasel (ianfasel_at_[hidden])
Date: 2004-10-06 23:01:07

I've noticed that if I specify 
using gcc
in user-config then Boost attempts to use gcc even if
I specify darwin on the command line, so
bjam release toolset=darwin
produces errors as shown below. However, if I specify
"using darwin" in user-config.jam, then
bjam release toolset=gcc
works correctly when I am on a linux machine.

Its minor of course, but the inconsistency can be a
slight annoyance when rapidly going back and forth
between platforms to test changes.

This is 
Boost.Build V2 (Milestone 9.1)
Boost.Jam 03.01.08
-Ian

(note: user-config.jam says "using gcc")
$ bjam release toolset=darwin
MyProj/boost-build/build/feature.jam:443: in
feature.validate-value-string from module feature
error: "darwin" is not a known value of feature
<toolset>
legal values: "gcc"
MyProj/boost-build/build/property.jam:200: in
validate1 from module property
MyProj/boost-build/build/property.jam:222: in
property.validate from module property
MyProj/boost-build/build/build-request.jam:201: in
convert-command-line-element from module build-request
MyProj/boost-build/build/build-request.jam:163: in
build-request.from-command-line from module
build-request
MyProj/boost-build/build-system.jam:92: in load from
module build-system
MyProj/boost-build/kernel/modules.jam:259: in import
from module modules
MyProj/boost-build/kernel/bootstrap.jam:120: in
boost-build from module
MyProj/boost-build.jam:1: in module scope from module

_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com