Re: [Boost-build] switching on toolset

Subject: Re: [Boost-build] switching on toolset
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-06-22 14:23:22

On 6/22/2015 7:49 PM, Paul A. Bristow wrote:

>> Unless I've missed something, you did neither, and you're making the same generic comment. Sadly,
> it's
>> not helpful. I have experience building stuff using all of make/automake, qmake, qbs, cmake, scons
> and
>> waf (if we only include tools for C++, and exclude various 'helpful' scripts on top of that). None
> of them
>> really isolate you from os or compiler version or other things - or make debugging issues
> particularly easy.
>> I'd even claim that Boost.Build --debug-* options are more useful than whatever these tools
> provide.
>>
>> So, if you're interesting in improving things, could you act on earlier responses, please?
>
> I have a simple suggestion that I believe would help matter greatly without being a major amount of
> work.
>
> Give lots (and lots and lots) more examples of command lines and entries in user-config.jam and
> jamfile.v2.
>
> Add a brief comment on what they do too.
>
> Perhaps you can update the docs source in /develop?
>
> But at least a release update would be really helpful in reducing the user fumbling - and googling
> to lots of often dodgy suggestions.
>
> If you added an example for every query you got, you might head off a lot more queries - and user
> frustration.

Paul,

that's a useful suggestion, thanks!

- Volodya