Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2004-06-09 06:44:37


Vladimir Prus <ghost_at_[hidden]> writes:

> David Abrahams wrote:
>
>> I meant
>>
>> <target-platform>linux # building objects for linux
>> <toolset>intel # using an intel compiler
>> ...
>>
>> The target platform and the compiler are orthogonal; I see no reason
>> to bind them together.
>
> Personally, I think.
>
> <toolset>intel-win:<cxxflags>-be-good-compiler
>
> is a bit better than
>
> <toolset>intel,<target-platform>win:<cxxflags>-be-good-compiler

I think it's better "in the small", but I think it's very bad for the
"big picture" view. At some point someone *will* want to change the
way, e.g. GCC works on particular target platforms. I don't think
it's appropriate to have a special way of controlling Intel works on
win/linux.

> This is mostly an UI issue, so I wonder what others think? (We have 'os'
> feature already

I think OS is different; it tells us about the host OS, right?

> , for changing the intel toolsets should be simple).
>
>> At some point you might want to do
>> cross-compilation... so it's not clear whether intel's different
>> options should be associated with the source-platform or the
>> target-platform, since they don't support cross-compilation (yet).
>
> I don't understand what consequences this has on subfeature vs. top-level
> feature.

OK.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com
 

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