Laca: >> I don't think it is fair to say that needing to build glibmm is >> needing to build "the entire stack". But anyway... > > I meant sigcpp, cairomm, glibmm, gtkmm.
That's quite a few dependencies. >> I agree that fixing C++ issues that show up when using Sun Studio is a >> pain. However, most issues are due to bugs that can be fixed. Saying >> they "just don't build" is probably a bit unfair. > > Okay, so instead of don't build, let me say that unfortunately > inkscape is an app that I was personally unable to build with > Sun Studio, even with the help of the authors. > I'd love to be proven wrong. But at least it shows that it > can be somewhat difficult to build C++ apps with Sun Studio, > even with a reasonable amount of experience with building apps > on Solaris and with the code itself. Oh, agreed. I've had some miserable days keeping dasher working on Solaris. It seems to break badly every few releases due to nasty C++ Sun Studio specific compile nastyness. So I do feel your pain. Most of the programs we ship in the JDS team are not C++ programs, so I am not sure we're the best C++ experts. I think we should probably involve the right people before we make a decision that causes us to bring in a ton of possibly unnecessary new interfaces into Nevada (I mean shipping both Sun Studio and GCC versions of the libraries instead of just Sun Studio). Perhaps we can get the Sun Studio C++ compiler people involved to help us work through the problems if we are really stumped. Brian
