[Sun] Using stlport4 by default
Does anybody know why -library=stlport4 and -features=tmplife are not turned on by default in the sunpro-tools.jam? -- Simon Atanasyan
Simon Atanasyan wrote:
Does anybody know why -library=stlport4 and -features=tmplife are not turned on by default in the sunpro-tools.jam?
I suppose because nobody has suggested this to be done. Next Boost release will be using Boost.Build V2, and the documentation for its sun.jam module will recommend using those flags. As for using them by default -- I don't know, I suppose there might be some reason why those options are not on by default in Sun compiler itself? - Volodya
2006/12/6, Vladimir Prus <ghost@cs.msu.su>:
Simon Atanasyan wrote:
Does anybody know why -library=stlport4 and -features=tmplife are not turned on by default in the sunpro-tools.jam?
I suppose because nobody has suggested this to be done.
Next Boost release will be using Boost.Build V2, and the documentation for its sun.jam module will recommend using those flags. As for using them by default -- I don't know, I suppose there might be some reason why those options are not on by default in Sun compiler itself?
Some users still link with libCstd.2.1.1 - old version of std library. Sometimes because they do not know about stlport4, sometimes because they have third party binary code depends on libCstd.2.1.1. So if we (at Sun) make -library=stlport4 is on by default these users have to change their Makefiles. IMHO it's not the problem but ... Anyway a lot of Boost code cannot be used without modern std library so if user want to use Boost it has to use stlport4 and this option should be on by default in Boost. -- Simon Atanasyan
"Simon Atanasyan" <atanasyan@gmail.com> wrote in message news:593202450612060536k2d924f9bg99cb16ce664e143b@mail.gmail.com...
2006/12/6, Vladimir Prus <ghost@cs.msu.su>:
Simon Atanasyan wrote:
Does anybody know why -library=stlport4 and -features=tmplife are not turned on by default in the sunpro-tools.jam?
I suppose because nobody has suggested this to be done.
Next Boost release will be using Boost.Build V2, and the documentation for its sun.jam module will recommend using those flags. As for using them by default -- I don't know, I suppose there might be some reason why those options are not on by default in Sun compiler itself?
Some users still link with libCstd.2.1.1 - old version of std library. Sometimes because they do not know about stlport4, sometimes because they have third party binary code depends on libCstd.2.1.1. So if we (at Sun) make -library=stlport4 is on by default these users have to change their Makefiles. IMHO it's not the problem but ... Anyway a lot of Boost code cannot be used without modern std library so if user want to use Boost it has to use stlport4 and this option should be on by default in Boost.
I second that. I believe this option should be on by default. The reason why Sun keeps non-conformant STL as default I understand, but I don't think they are applicable here. Gennadiy
On 12/6/06, Gennadiy Rozental <gennadiy.rozental@thomson.com> wrote:
"Simon Atanasyan" <atanasyan@gmail.com> wrote in message
[snip]
Some users still link with libCstd.2.1.1 - old version of std library. Sometimes because they do not know about stlport4, sometimes because they have third party binary code depends on libCstd.2.1.1. So if we (at Sun) make -library=stlport4 is on by default these users have to change their Makefiles. IMHO it's not the problem but ... Anyway a lot of Boost code cannot be used without modern std library so if user want to use Boost it has to use stlport4 and this option should be on by default in Boost.
I second that. I believe this option should be on by default. The reason why Sun keeps non-conformant STL as default I understand, but I don't think they are applicable here.
+1
participants (4)
-
Gennadiy Rozental -
Michael van der Westhuizen -
Simon Atanasyan -
Vladimir Prus