Subject: Re: [Boost-build] unexpected requirement
From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2012-06-27 10:07:32
> If you know where the tool's executable is located - simply pass the
> correct path here. And if you do not have the executable - do not call
> the 'using xsltproc' rule in the first place.
Just remembered some more things...
If you need the features from tools/xsltproc.jam defined so your
project build configuration can get parsed correctly - just do an
'import xsltproc'. That will load the module, registering its features
in the process, but will not initialize the module with information on
where the xsltproc executable is located.
However, if you are using xslt and xslt-dir rules - that would
require that the toolset be initialized before hand, and there is no way
of avoiding that other then to modify the xsltproc.exe toolset to do
some sort of lazy checking only when their targets actually get built
and not at the Boost Build code processing stage...
Really can't go on with these what-if scenarios without a valid
example project. Feels like I'm searching for a needle in a haystack... :-(
Hope this helps.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk