Thank you very much, the provided workaround works for me.

>>> "Steven Watanabe-4 [via Boost]" <[hidden email]> 24.02.2016 03:10 >>>

AMDG

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
path exists:

import path ;
if [ path.exists /path/to/g++ ]
{
using gcc : /path/to/g++ ;
}

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

If you reply to this email, your message will be added to the discussion below:

http://boost.2283326.n4.nabble.com/Boost-build-failed-if-custom-toolset-path-is-not-available-tp4683565p4683758.html

To unsubscribe from Boost build failed if custom toolset path is not available, click here.
NAML

Diese Nachricht und allfaellige angehaengte Dokumente sind vertraulich und nur fuer den/die Adressaten bestimmt. Sollten Sie nicht der beabsichtigte Epfaenger sein, ist jede Offenlegung, Weiterleitung oder sonstige Verwendung dieser Information nicht gestattet. In diesem Fall bitten wir Sie, den Absender zu verstaendigen und die Information zu vernichten. Für Uebermittlungsfehler oder sonstige Irrtuemer bei Uebermittlung besteht keine Haftung.

This message and any attached files are confidential and intended solely for the addressee(s). Any publication, transmission or other use of the information by a person or entity other than the intended addressee is prohibited. If you receive this in error please contact the sender and delete the material. The sender does not accept liability for any errors or missions as a result of the transmission