You can build a multi-architecture binary using the configure and make method, but it's a bit more involved: making each arch, then using lipo to stick them all together.
Michael Tughan On 2009-09-22, at 4:28 PM, Charlie Fenton wrote: > Actually, the ./configure is not suitable for building the client on > the Mac for general distribution, because we need to build for three > different architectures (PowerPC, i386, x86_64) and combine them in > universal binaries. For this reason, the Mac build (using XCode) > also uses its own manually generated config.h file. > > So please do _not_ delete version.h. > > For those who really want to build their own Mac client using > configure & make, they can still do a single-architecture build that > way. > > As Rom wrote: >> Why not just leave the version stuff alone? >> >> version.h is available for Mac and Windows, and it is recreated for >> ./configure. In the end everybody gets what they need. > > Cheers, > --Charlie > > At 5:53 PM +0200 9/22/09, Gabor Gombas wrote: >> On Tue, Sep 22, 2009 at 11:45:28AM -0400, Rom Walton wrote: >> >>> Charlie uses XCode to generate the BOINC binaries and not the >>> ./configure script. >> >> Well, he could still call ./configure and then ignore the generated >> Makefiles :-) >> >> The correct fix would be to have the version information in a static >> file and let autoconf/Windows build/Mac build all read it from there. >> Probably it's not worth the complication. >> >> Gabor > > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
