Subject: Re: [boost] [build] Default compiler options for a toolset
From: Edward Diener (eldiener_at_[hidden])
Date: 2013-11-20 20:42:36
On 11/20/2013 6:59 PM, Gavin Lambert wrote:
> On 21/11/2013 12:33, Quoth Edward Diener:
>> I did not think I was removing them, justy changing them to produce no
>> compiler option. It seems a flaw in the system that one cannot specify
>> generating no compiler option for some Boost Build option(s). What do
>> you do when some compiler has no equivalent compiler option for a Boost
>> Build option ?
>
> You don't specify it in the first place.
>
> The problem you're having is because your jamfile is including the msvc
> jamfile, but the compiler is not 100% msvc compliant.
>
> Another way you could have done it would have been to copy the msvc file
> and edit it to match the real capabilities of clang-win, instead of
> including the msvc file.
You may be right about this but someone else created the jam file, not
me. I am just trying to modify it. OTOH inheriting flags from msvc seems
logically much cleaner than having to duplicate them, or even duplicate
almost all of them.