CREMARENCO Cosmin wrote:
Hi
We have a solaris distribution of our software and we would like to use the boost libraries. In my understanding you recommend compiling and linking with stlport. However we depend on third party libraries that were built with libCstd, which is the old standard non-conformant library from sun. Sun docs clearly state that one should use either stlport or libCstd in the same program but not both. Also, we use sun studio 11.
Now, we tried building boost with libCstd. A number of libraries built without problems: date, iostreams, prg, signals, system.
In our application we use mostly header-only libraries and a small number of libraries that need to be linked with the program.
We could get program-options (which we use extensively) to build by patching it (a tentative patch for 1.39 is attached). Of course one also needs to change tools/build/v2/tools/sun.jam in order to disable compiling and linking with stlport.
My question is: if we send patches that allow boost to be compiled and linked with libCstd is there a chance that you will accept them in your main codeline?
A chance -- of course. But please be sure to explain exactly what is the problem the compiler is having and produce minimal patch to address that problem. Using svn.boost.org is the best way to submit patches. - Volodya