Overview
Artifact ID: | efffeaf9a3e553ec962967d013378a25bf25f174 |
---|---|
Ticket: | e5e2e0408ed3d237e803a06a221291e909f55ea8
Universal binary builds for Mac OS X |
User & Date: | anonymous 2010-04-22 18:12:06 |
Changes
- comment changed to:
The downloads available on: [http://www.fossil-scm.org/download.html] are for Mac OS X 10.5/10.6 intel only. Please build a universal binary that works with Mac OS X 10.4+. If the 10.4 SDK is installed (should be installed by default with the 10.5 developer tools -- it may be an optional install with the 10.6 tools) into the normal default location of <tt>/Developer/SDKs/MacOSX10.4u.sdk</tt> then simply using this command: <pre> make \ CFLAGS='-arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4' \ LDFLAGS='-arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4' </pre> instead of just "<tt>make</tt>" in the fossil source checkout will produce a universal binary that runs on 10.4 or later on PowerPC or Intel machines. (Of course it doesn't hurt to run <tt>strip</tt> on the final <tt>fossil</tt> file produced either.) There are still a lot of PowerPC machines out there (and a fair number of 10.4 ppc machines -- that's the last version of Mac OS X that will run classic apps) and this change is a relatively painless thing to do to support more platforms and make fossil accessible to more folks who are unwilling (or unable) to build from sources themselves on Mac OS X. I have verified that the universal binary fossil executable built this way runs successfully on these platforms: <ul> <li>10.4 PowerPC G4 <li>10.5 PowerPC G5 <li>10.5 Intel x86_64 <li>10.6 Intel x86_64 </ul> and so believe there are no problems with the universal binary produced this way.
- foundin changed to: "[7c37b46b12] 2010-04-15 23:53:15"
- private_contact changed to: "ae1a74676bb0d1ac520802109f926567b1637ac7"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to: "Universal binary builds for Mac OS X"
- type changed to: "Feature_Request"