Hi, Thanks for the sympathy and info. I wish I knew about this before. I understand the reasoning behind this policy decision however it's obviously not a perfect decision since it means that any application compiled with g++ will not be able to use libraries compiled with CC. I think the real solution (if possible at all) would be to use a consistent ABI (that would still cause backward compatibility issues).
Regards, Faramarz Vladimir Marek wrote: > Hi Faramarz, > > First of all thank you for your work. And sorry for the disappointment. > > > > >> I have a hard time to conclude the from the link you sent that GCC >> cannot be used. Also almost all of the links in the appendix C do not >> work. Can you point me to the specific point in the material? >> > > I don't know about the material, but the reason is, that C++ library compiled > by g++ can not be used by CC, and vice versa. For C code this is not a > problem, > C compilers use the same ABI. > > This led to decision that g++ won't be allowed. > > > > >> Based on this link (sorry folks outside the SWAN): >> >> http://ostest.central.sun.com/wiki/index.php/Package_Delivery_Project#3._Develop_Software >> >> It seems that the use of GCC is allowed. If this is not the case, then >> perhaps we need to update the above. >> > > gcc is c compiler, g++ is C++ compiler. > > > >> So if a package requires GCC for compilation and making the changes is >> not trivial to make it compatible with Studio, then that >> package cannot be ported to OpenSolaris? >> > > The problem with Qt is not Sun Studio, but standard template library used in > {,Open}Solaris (distributed with SunStudio). And only WebKint (the Qt html > component) had the issue (yes, I was also one of many compiling Qt on my own, > and sending patches to Trolltech). > > > > The biggest problem is that it's not clearly documented anywhere, AFAIK. > > I started > > http://wikis.sun.com/display/SFWNotes/Package+writing+guidelines >
