Subject: Re: [Boost-build] Boost build failed if custom toolset path is not available
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-02-23 21:35:58
On 02/17/2016 12:49 AM, marfro wrote:
> I am successfully compiling the boost library (1_46_0) for msvc and for gcc.
> For gcc I use a custom toolset path. Therefore I created an entry in the
> user-config.jam file. If that path is not available the whole boost build
> files even when I build it only for msvc.
> After enabling the debug information I see that the build process
> initializes and checks all using statements of the user-config.jam file. Why
> is that necessary, since I already named the toolset on the bjam call?
> Does anybody know if I can avoid this behaviour so the build still be
> successfull even though the path is missing?
It used to be that this was required to work,
and it still does with some tools, just not gcc.
The easiest workaround is to check whether the
import path ;
if [ path.exists /path/to/g++ ]
using gcc : /path/to/g++ ;
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