site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Andrew http://www.stone.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I'm really grooving on how XCODE lets you build universal binaries with different minimum deployment targets and architecture specific flags - ie - you want your executable to be able to run on PPC 10.2, 10.3 and 10.4, and on intel for 10.4. It really provides a nice GUI for using GCC 4.0. When it comes to CLI building traditional unix source that might use autoconf and setup headers based on the endianness of the compiler, you can bet that you'll get the wrong result for the non-native architecture, so XCODE might be the way to go, passing flags as needed to get the correct results. #ifdef GROVEL So, given these two points, I'm wondering if anyone has already made XCODE projects out of source for libtiff, libjpeg and libz. #endif // GROVEL One problem I've had with g++ 10.3 built binaries on 10.2 is that libstdc++ became a dylib in 10.3, so if you link against libstdc++ on 10.3 or greater, the app won't load in 10.2 where it cannot find the dylib (and I don't think its in the 2.8.sdk either). So, that's why I sometimes need to make static library versions of these things... This email sent to site_archiver@lists.apple.com