On 6/27/11 4:08 AM, Pierre Ossman wrote: >> 64-bit or 32-bit. I also want to implement a BUILD_STATIC option in >> CMake that statically links with libstdc++ and libgcc (if possible-- >> note that on Mac, there is no libstdc++.a.) >> > > Note that there can be if using something other than Apple's gcc.
That's fine. The same procedure should work that works on Linux in that case-- i.e. using gcc -print-file-name libstdc++.a to figure out where the static version is and pulling some tricks to link against it instead of the dynamic version. Not sure why anyone would want to use a non-vendor-supplied version of GCC on Mac, though. The thing about libgcc and libstdc++ on Mac is that Apple maintains full backward compatibility in these dynamic libraries, so, for instance, if you link with the 10.4 compatibility SDK, your binary will run on that or any later version, even though it depends on libgcc.dylib and libstdc++.dylib. With Linux, not so much the case. Generally the distros either don't supply backward-compatible versions of libgcc/libstdc++, or they supply them only for the previous release of the distro. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
