site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Oct 31, 2007, at 12:16 AM, Terry Simons wrote: http://developer.apple.com/technotes/tn2005/tn2137.html e.g. (for autoconf.2.5.x projects) ./configure CC=/path/to/gcc CXX=/path/to/g++ ... and for older autoconf env CC=/path/to/gcc CXX=/path/to/g++ ./configure ... Peter -- Peter O'Gorman http://pogma.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... This may not be the correct place to ask this question, though it seems potentially relevant to Darwin as well as Mac OS X. If there's a better place to ask please point me in the right direction. I read something in an XCode note about Leopard having the ability to allow you to install XCode in an arbitrary directory... How does this affect -isysroot? Is there an environment variable set that one can query to determine the location of the dev tools? Most "./configure" based projects that support building universal binaries are likely using the instructions posted at: to set up their autoconf scripts for building universal. That technote recommends setting -isysroot to /Developer/SDKs/ MacOSX10.4u.sdk, which obviously may be located in a different location on Leopard. I'm just wondering if there's a better way to deal with this on Leopard. The xcode-users ist might be more appropriate. Anyway, the only differences that would apply if you chose not to install the package that puts compilers in /usr/bin is to explicitly set CC, CXX etc when calling configure. I believe most/many will install the package that puts the compiler in /usr/bin, iirc it defaults to on and has to be customized to not be installed. This email sent to site_archiver@lists.apple.com