On 8/6/06, Ren Zhi Zhang <icouldnotsee@hotmail.com > wrote:

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.

FWIW, I've asked you for extra information in:

http://article.gmane.org/gmane.comp.lib.boost.build/13384

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:

What errors, specifically? I assume the errors are similar to what you've reported before, but they can't be exactly same, at all counts.

Can you provide the output of --debug-building?

I suspect that <define>ANYTHING does not work for the following reason -- you request a build of exe with that define.

You also require a build of 'install' target with the define. When install target tries to build exe, it does not pass the define,

since <define> is a free property. So, you now get two requests for building exe -- with and without <define>ANYTHING, and V2

does not know what you want. You can be more explit by requesting just exe or just install target.

- Volodya