[Boost-build] Default build for specific Boost libraries. (was: Re: Boost 1.35.0 Jamroot patch to make install work n subprojects)

From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2008-09-01 17:38:07

[If I'm not mistaken Rene had much to do with the main Boost library 
Jamroot file so I'm CCing him in case he wants to chime in.]

   Hi Steven.

>>> Another related problem is to make
>>> bjam msvc -n --with-iostreams trunk//install
>>> work, where trunk is my working copy.
>>> After applying this patch, only the default-build
>>> is still wrong.
>>
>>   Nice to know it's getting better. When you do get it working 
>> completely - just send the patch in.
> 
> Before I work on this, I'd like to be clear on exactly what the behavior
> ought to be.  The current behavior is that the default build
> will be set according to --build-type=... with the default being
> --build-type=minimal only if the current working directory is
> BOOST_ROOT.  This is set in Jamroot's project default-build.
> 
> I think that the correct behavior is to apply the default build only to
> 
> /boost//install
> /boost//stage
> /boost//build_all
> and the targets created by boost_install.

   [By boost_install I'm guessing you mean the boost-install rule.]

   That sounds about right to me. And probably some of the intermediate 
targets like install-proper, install-unversioned, stage-proper & 
stage-unversioned.

   So to summarize, the targeted effect then would be:

   * When triggered for any target other than ones listed above 
(/boost//install, /boost//stage...) there would be no special 'default 
build'.
   * When triggered for one of targets listed above (/boost//install, 
/boost//stage...) there would be a 'default build' setting as there is now.
   * Whether the 'default build' settings are applied would not be 
affected by what folder the build has been started from.

   Is that summary correct and complete?

   Just as a heads up - in the main Boost Jamroot file I see the 
following code & comment that would need to be taken into consideration 
  and dealt with when designing and implementing this.

> # We only use the default build when building at the root to avoid having it
> # impact the default regression testing of "debug".
> # TODO: Consider having a "testing" build type instead of this check.
> if $(__file__:D) != ""
> {
>     default-build = debug ;
> }

   Best regards,
     Jurko Gospodnetić