Toolset naming conventions

On Tuesday 21 March 2006 10:20, Jim Douglas wrote:
> With bbv1 I used the toolset names
"qcc-3.3.5-cpp" and "qcc-3.3.5-qpp"
> which decodes roughly as
>
> <qnx toolchain> - <gcc compiler version> -
<C++ std lib variant>
>
> Now with bbv2 if I try to construct a toolset name from
the base toolset
> "qcc" with variant/version
"3.3.5-cpp" it fails due to the use of a
> hyphen, so I have to change it to an underscore i.e.
"3.3.5_cpp".
>
> The problem here is that all the bbv1 entries in
> explicit-failures-markup.xml no longer work for bbv2.
:-(
>
> Before I hack the xml file I thought I woukd just check
that the above
> is correct and there is no way I can construct bbv2
toolset names that
> are compatible with bbv1.

I'm afraid it's not possible. V2 believes that dash
separate values of 
"subfeatures", and "cpp"/qpp"
are just convenient names you use, so they must 
be joined to the version number with underscore. I'm afraid
this is a bit 
hard to change at the moment.

>
> PS Volodya - I had some machine problems recently so I
thought I would
> jump straight in with bbv2. It seems to be OK. Thanks
for your help.

Should you need further assistance, don't hesitate to ask.
In addition to 
email, alternative ways to reach me are Jabber
(vladimir_prusjabber.ru), ICQ (100422315), and Skype
(vladimir_prus).

Thanks,
Volodya


-- 
Vladimir Prus
http://vladimir_pru
s.blogspot.com
Boost.Build V2: http://boost.org/boost-
build2
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus wrote:
> On Tuesday 21 March 2006 10:20, Jim Douglas wrote:
> 
>>With bbv1 I used the toolset names
"qcc-3.3.5-cpp" and "qcc-3.3.5-qpp"
>>which decodes roughly as
>>
>><qnx toolchain> - <gcc compiler version>
- <C++ std lib variant>
>>
>>Now with bbv2 if I try to construct a toolset name
from the base toolset
>>"qcc" with variant/version
"3.3.5-cpp" it fails due to the use of a
>>hyphen, so I have to change it to an underscore i.e.
"3.3.5_cpp".
>>
>>The problem here is that all the bbv1 entries in
>>explicit-failures-markup.xml no longer work for
bbv2. :-(
>>
>>Before I hack the xml file I thought I woukd just
check that the above
>>is correct and there is no way I can construct bbv2
toolset names that
>>are compatible with bbv1.
> 
> 
> I'm afraid it's not possible. V2 believes that dash
separate values of 
> "subfeatures", and
"cpp"/qpp" are just convenient names you
use, so they must 
> be joined to the version number with underscore. I'm
afraid this is a bit 
> hard to change at the moment.

Does that mean that the subfeature of the C++ Std Library
could be 
specified using the "qcc-3.3.5-cpp" notation? Or
is this a topic for a 
future discussion after we have made the initial switch to
bbv2?

Jim

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build