Re: [Boost-build] BBv2 integrated into VS2005 - relative path problem

From: Andrei Melnikov (andy.melnikov_at_[hidden])
Date: 2006-06-01 15:28:03

On 01/06/06, Bojan Resnik <resnikb_at_[hidden]> wrote:
> > I think this confusion would be fixed if I could invoke bjam from
> > project/vc current folder and pass it Jamroot location explicitly. Is
> > this possible?
> >
> > Andrey
>
>  Yes, I use it this way also. I invoke bjam using:
>      %BOOST_ROOT%\bjam --v2 -d0 ..
>
>  (note the two dots at the end - they are the relative path from the
> vcproj to Jamfile.v2)

It worked. Thank you.

I wonder if this is documented. bjam --help-usage just says the following:

Boost.Jam Usage:

  bjam [ options... ] targets...

This text comes from util/doc.jam, and it definitely has to be changed
to something more correct and informative. The following line is still
a valid bjam command line, but  ".." and  "cxxflags=xxx" command line
arguments are neither targets nor options.

bjam release .. cxxflags=xxx -d0

http://boost.org/boost-build2/doc/html/jam/usage.html is a bit more
precise, and can be easily extended:

bjam ( -option [value] | target ) *

Is ".." really a target, or it is not? From gnu make perspective I
wouldn't call it a build target.

What is the right name for "cxxflags=xxx" expression? Is it a "build
requirement"? What is "release"? It's a build variant, but are build
variants also targets?

I'll be glad to propose a path as soon as I get these questions answered.

Andrey