Re: [Boost-build] Problem with mingw flavour

Subject: Re: [Boost-build] Problem with mingw flavour
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2008-11-03 22:54:16

Sorry about the silence... But I've been horribly busy this past week, 
and this week too for that matter. So don't expect much... Since I 
luckily noticed this...

Vladimir Prus wrote:
> On Friday 31 October 2008 11:42:20 Juergen Hunold wrote:
>> On Thursday 30 October 2008 21:28:03 Vladimir Prus wrote:
>>> Now the question is which features should be the key for compiler
>>> selection, and which should be deduced from the compiler. Consider:
>>>
>>> 	using gcc : 4.3.1 ; 			         # native (x86-linux) compiler
>>> 	using gcc : 4.3.1 : i586-mingw32msvc-g++ ; 	 # x86-windows compiler
>>> 	using gcc : 4.3.1 : arm-none-linux-gnueabi-g++ ; # cross to arm bare metal
>>>
>>> The features involved are possibly:
>>>
>>> 	<toolset-gcc:version>
>>> 	<toolset-gcc:flavour>
>>> 	<target-os>
>>> 	<architecture>
>>>
>>> I suggest we first deal with the flavour. It seems to me that it basically
>>> duplicates <target-os> -- we can use <target-os>windows to detect the same,
>>> and for cygwin compiler we'll have <target-os>cygwin. So, I suggest we drop
>>> this feature, and use target-os instead.

>> +1 from me.

> Rene, do you have a comment on this?

+1; Except for the part about not being able to add a target-os feature 
automatically when MinGW is auto-detected as we do with flavour.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail