[Boost-build] using variant, define and install together ...

From: Ren Zhi Zhang (icouldnotsee_at_[hidden])
Date: 2006-08-06 00:34:23

Apologies for resending this mail and starting a new thread, but replies to 
my previous question seems to be lost (or at least I've seen or hear about 
it again during the past month), so I hope you guys won't mind if I restart 
the question.

Attached to the mail is a simple self build project illustrating the 
problems I ran into. I have derived a new variant call "package" from the 
default "release" variant so when "package" is built, the final product 
would be copied into a new directory using the install rule. However, I run 
into problems when "package" is built with additional defines to control 
compilation. For example, the following commands are known to work:

    bjam
    bjam release
    bjam package
    bjam define=ANYTHING
    bjam release define=ANYTHING

However, the following command would fail and just emit a bunch of errors:

    bjam package define=ANYTHING

Ironically, the following would work:

    bjam package define=NDEBUG

I managed to track down the issue (or at least I think I have) to using the 
install rule. If the "install" line is commented out, everything would build 
just fine. So I'm wondering if anyone can figure out why it happens?

I'm running on Windows XP using Visual C++ 2005, bjam 3.1.13 and Boost.Build 
V2 (Milestone 11).

Ren Zhi

P.S. We run additional tests on the final product (using the "release" 
built) before it's released, so it's desirable to have a separate variant 
derive from "release" rather than having everything mixed up.