Re: boost-build.jam precedence over $BOOST_BUILD_PATH

From: Samuel Krempp (krempp_at_[hidden])
Date: 2004-01-23 07:41:21

le Friday 23 January 2004 12:46, ghost_at_[hidden] écrivit :

> Samuel Krempp wrote:
>> It can be confusing sometimes, since boost-build.jam can be in any parent
>> directory, knowing what is the actual boost-build root in use can be
>> non-trivial.
>>
>> couldn't bjam --version report it ?
>> or is there already a switch do do that ?
> 
> There's no switch yet. I think that since printing root is for
> troubleshooting, we should not include it to --version output.

in case there are several Boost.Build directory trees, the one in use is
part of the "version" in some way, I think users would find it normal to
see something like :

% bjam --version
Boost.Build V2 (Milestone 9.1) found from /home/sam/progs/boost-build.jam
at /home/sam/Boost/tools/build/v2
Boost.Jam 03.01.09

or a more compact :

% bjam --version
Boost.Build V2 (Milestone 9.1) at /home/sam/Boost/tools/build/v2
Boost.Jam 03.01.09

gcc -v does print its directory information (and more), and many apps print
verbose version messages, so there is precedent for it.

> There's --debug-configuration switch, which so far interpreted by msvc.jam
> only and tell where it find compiler.
> 
> Maybe, the same switch can cause Boost.Build to print where it found
> boost-build.jam and directory from where Boost.Build is loaded? What do
> you think?

yeah that could do the job too. but maybe needs more modification than
changing --version, no ?
it's true that bjam --version maybe shouldn't print debug details (like
saying whether the Boost.Build root was found from variable or
boost-build.jam (nd then which), so a debug switch would have more freedom
in its output.

-- 
Samuel