Re: [Boost-build] Boost build failed if custom toolset path is not available

Subject: Re: [Boost-build] Boost build failed if custom toolset path is not available
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-02-24 15:39:08

AMDG

On 02/24/2016 01:01 PM, Edward Diener wrote:
> 
> The larger issue, which I have made in the past on this mailing list, is
> that Boost build "executes" a "using xxx" even when the xxx toolset is
> not being used in any way. If it waited until toolset xxx was actually
> being used before "executing" a "using xxx" Boost build would be much
> faster and much simpler to use for the end-user. Is it really too much
> work to make this change in the Boost build logic ?
>

Yes.

- Delaying the actual configuration to some
  unspecified point will make any problems
  that much harder to debug.  As things stand,
  at least anyone can figure out why it's
  failing: user-config.jam runs exactly what
  you tell it to.
- The implementation of laziness needs to
  be handled separately by each toolset, as
  we still need to do enough initialization
  to determine when a toolset is "used"
- Instead of having two states, initialized
  or not initialized, each toolset would have
  three states: ready to use, initialized but
  not fully configured, and not initialized.
  This increase in complexity is likely to
  propagate everywhere, possibly even into
  user Jamfiles.

  With that being said, this change is on my
long-term todo list, but it's a fairly major
project and is unlikely to happen in the
immediate future.

In Christ,
Steven Watanabe