Re: [Boost-build] msvc express toolset.

From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2008-07-22 19:53:08

   Hi Steven.

> I compile using a windows bjam for both windows and cygwin.
> My user-config.jam contains this:
> 
> using gcc : 3.4.4 : g++ ;
> using gcc : 4.2.3 : g++-4.2.3 ;
> using gcc : 4.3.0 : g++-4.3.0 ;
> 
> If I am not running from the cygwin shell, these are not in my PATH,
> so initialization fails.  However, since the gcc toolset only issues a 
> warning,
> I can still build with msvc.

   Would that setup not be cleaner if you did something like this:

> import os ;
> if [ os.name ] = CYGWIN
> {
>     using gcc : 3.4.4 : g++ ;
>     using gcc : 4.2.3 : g++-4.2.3 ;
>     using gcc : 4.3.0 : g++-4.3.0 ;
> }

   Then you would make it clear that these toolsets are intended to be 
used only from CYGWIN.

   But I admit this 'executable could not be found' case is in a 
somewhat gray area. I can see how it could be deemed 'useful' to tell 
the build system to 'use this if possible', but I personally prefer to 
be explicit about such things. On the other hand, I personally do what 
it takes to remove warnings so a warning would get my attention just fine.

   Also, if we 'allow this' then do we really want this warning to be 
displayed always or only when you explicitly pass the 
--debug-configuration option on the command line? Or possibly display it 
without the --debug-configuration option but only if the same 
'incorrectly configured' toolset is explicitly requested by the user.

   I'd still report 'conflicting toolset configurations' as direct 
errors and not as warnings.

   Best regards,
     Jurko Gospodnetić