David Abrahams wrote:
on Tue May 22 2007, "John Maddock" <john-AT-johnmaddock.co.uk> wrote:
Existing supported toolsets remain unchanged. The 99% case where the user is using a version of gcc but with custom invoke/compiler options could be detected (autoconf does this already) and forwarded to our gcc toolset presumably.
I had meant to test this out by now, but you know time etc...
You're not answering my questions. What about the platform/compiler-independent build properties when they appear in Jamfiles? Are they ignored, or do they get translated somehow, or what?
Yes, they would be ignored, what else can you do if you don't recognise the compiler? The thing is true whatever the build system.
FWIW, it was a design goal of Boost.Build v2 to get away from builds that depend on environment variables.
Absolutely, but the suggestion is meant to help folks that are doing unusual things with unusual compilers, not for folks with known toolsets. Likewise to make the configure script behave as most folks expect them to. John.