On Fri, 24 Aug 2007, Stefan Teleman wrote: > Barring some unforeseen problems in building and testing Boost 1.33.1 > with the Apache/RogueWave STL over the next few days, i am proposing > using the Apache/RogueWave Standard C++ Library for KDE Solaris.
This sounds like the best option to play well with others. > A permanent side-effect of this library change is that linking against > Sun's libCstd.so *and* the Apache/RogueWave Standard C++ Library is > no longer permitted. What about other programs that are linked against either library? Will they play well together? Does this mean that the entire stack which runs together, must be compiled with the same? IOW, if someone wanted to write a kde app, would they be required to use the same Apache/RogueWave Standard C++ Library? This might be a dumb question, but what about getting the compiler folks to change Studio 12 to be 100% compliant with the ANSI/ISO C++ Standard? This would allow us to use the libCstd.so from Sun, right? Have you asked them about that? -- Alan DuBoff - Solaris x86 IHV/OEM Group
