Changes between Version 1 and Version 2 of BuildMacApp

Timestamp:

Apr 2, 2008, 3:47:15 AM (17 years ago)

Author:

charlief

Comment:

--

BuildMacApp

@@ -11 +11 @@
 
 Building applications for Macintosh OS X is complicated by the fact that Mac OS X is actually 3 different platforms:
-* powerpc-apple-darwin: PowerPC processors running OS 10.3.0 and above
-* i686-apple-darwin 32-bit intel processors running OS 10.4.0 and above
-* x86_64-apple-darwin: 64-bit intel processors running OS 10.5.0 and above 
+ * powerpc-apple-darwin: PowerPC processors running OS 10.3.0 and above
+ * i686-apple-darwin 32-bit intel processors running OS 10.4.0 and above
+ * x86_64-apple-darwin: 64-bit intel processors running OS 10.5.0 and above 
 BOINC does not support 64-bit PowerPC applications for the Mac.
 
@@ -19 +19 @@
 
 Although BOINC version 6.1.0 supports only Mac OS X 10.3.9 and later, earlier versions supported all versions back to OS 10.3.0.  The GCC compiler version 4.0 was introduced in OS 10.3.9.  OS 10.3.0 through 10.3.8 can't run applications built with GCC 4.0, so you have 2 choices if you want to support PowerPC (G3, G4 and G5) processors:
-* Build  your PowerPC application with GCC 4.0 and only distribute your application to Macs running 10.3.9 or later.
-* Build your PowerPC application with GCC 3.3.
+ * Build  your PowerPC application with GCC 4.0 and only distribute your application to Macs running 10.3.9 or later.
+ * Build your PowerPC application with GCC 3.3.
 
 The libraries supplied with different versions of OS X support different APIs.  You need to take certain steps to ensure that you use only APIs that are available in all the OS versions you plan to support.  There are two basic ways to accomplish this:
-* Build each platform on a system running the oldest OS you need to support:
+ * Build each platform on a system running the oldest OS you need to support:
     * A PowerPC development system running OS 10.3.0 through 10.3.8 (or 10.3.9 if you won't support the older systems)
     * An Intel development system running OS 10.4.x
     * A 64-bit development Intel system running OS 10.5.x (The original Intel Macs used an Intel Core Duo processor which was 32-bit only.  You must have an Intel Core 2 Duo or newer processor to run 64-bit applications.)
-* Use a single development system running OS 10.5.x and cross-compile for the various platforms.  The remainder of this document describes that process.
+ * Use a single development system running OS 10.5.x and cross-compile for the various platforms.  The remainder of this document describes that process.
 
 You will also need to build the BOINC libraries on each platform and any other libraries your application needs.  You can use the Makefiles supplied in the BOINC CVS tree to build the BOINC libraries with this approach, or build them as Universal Binaries using the BOINC XCode project, as described later in this document.
@@ -117 +117 @@
  * On any other Intel Mac, it runs the i386 executable.
 
+== Build Any Other Needed Libraries ==
 
-**** Build Any Other Needed Libraries ****
+If you are building a third-party library (such as JPEG), you will need to take the steps listed above in the section Cross-Platform Development.  See the files `boinc_samples/example_app/Makefile_mac2` and `boinc_samples/example_app/MakeMacExample.sh` for examples of how to accomplish this.
 
-If you are building a third-party library (such as JPEG), you will need to take the steps listed above in the section Cross-Platform Development.  See the files boinc_samples/example_app/Makefile_mac2 and boinc_samples/example_app/MakeMacExample.sh for examples of how to accomplish this.
-
-
-**** Build Your Application ****
+== Build Your Application ==
 
 We will use the example_app to illustrate the 3 methods of cross-compiling.   Download this sample project from Subversion, and put it in the same BOINC_dev folder.  To do this, type the following in Terminal:
 
+{{{
 cd {path}/BOINC_dev/
 mkdir boinc_samples
 cd boinc_samples/
 svn co http://boinc.berkeley.edu/svn/trunk/boinc_samples  
+}}}
 
+=== Using an XCode Project ===
 
-**** Using an XCode Project ****
-
-Double-click on the project file boinc_samples/mac_build/UpperCase2.xcodeproj.  At the top of the main window, select Build_All for the Active Target, and ppc_Deployment for the Active Build Configuration.  Then click on the Build icon (or select Build from the Build menu.)  Repeat for Active Build Configurations i386_Deployment and x86_64_Deployment.
+Double-click on the project file `boinc_samples/mac_build/UpperCase2.xcodeproj`.  At the top of the main window, select '''Build_All'' for the ''Active Target'', and '''ppc_Deployment''' for the ''Active Build Configuration''.  Then click on the Build icon (or select Build from the Build menu.)  Repeat for ''Active Build Configurations'' '''i386_Deployment''' and '''x86_64_Deployment'''.
 
 Use the example XCode project as a guide or a starting point to create an XCode project for your own application.
 
-**** Using a Generic Makefile With a Custom Shell Script ****
+=== Using a Generic Makefile With a Custom Shell Script ===
 
 Type the following in Terminal:
 
+{{{
 cd {path}/BOINC_dev/boinc_samples/example_app/Mac/
 sh MakeMacExample.sh -clean
+}}}
 
 Again, you can use this shell script as a guide or starting point to create one for your application.  Let's examine the details:
 
-In this case, there is no autoconf file, so we had to modify the generic Makefile slightly.  The most significant change was to add the variable VARIANTFLAGS to the list of arguments in CFlags.  The remaining changes were to ensure that the search paths included the needed BOINC headers and  libraries.
+In this case, there is no autoconf file, so we had to modify the generic Makefile slightly.  The most significant change was to add the variable `VARIANTFLAGS` to the list of arguments in `CFlags`.  The remaining changes were to ensure that the search paths included the needed BOINC headers and  libraries.
 
-If your application uses an autoconf file, you can set the various environment variables for configure directly.  For examples, see the scripts buildc-ares.sh, buildcurl.sh and buildjpeg.sh in the directory 
-{path}/BOINC_dev/boinc/mac_build/.
+If your application uses an autoconf file, you can set the various environment variables for configure directly.  For examples, see the scripts `buildc-ares.sh`, `buildcurl.sh` and `buildjpeg.sh` in the directory `{path}/BOINC_dev/boinc/mac_build/`.
 
 Here are the elements of our script:
 
+{{{
 export PATH=/usr/local/bin:$PATH
-XCode 2.4.1 installs autoconf 2.59 and automake 1.6.3.  If you installed a later version of either or both, they will be in the /usr/local/bin/ directory.  This line ensures that the system will look there first.
+}}}
+XCode 2.4.1 installs autoconf 2.59 and automake 1.6.3.  If you installed a later version of either or both, they will be in the '/usr/local/bin/' directory.  This line ensures that the system will look there first.
 
+{{{
 export MACOSX_DEPLOYMENT_TARGET=10.3
+}}}
 Specifies the Mac OSX Deployment Target, which is the minimum target OS X version.  This tells the compiler to reject any attempts to use APIs not available in that version of OS X.
 
+{{{
 export CC=/usr/bin/gcc-3.3;export CXX=/usr/bin/g++-3.3
-Specify the compiler to use
+}}}
+Specifies which compiler to use.
 
+{{{
 export LDFLAGS="-Wl,-syslibroot,/Developer/SDKs/MacOSX10.3.9.sdk -arch ppc"
-Specify the appropriate SDK for the minimum target OS X version and the architecture for the linker.
+}}}
+Specifies the appropriate SDK for the minimum target OS X version and the architecture for the linker.
 
+{{{
 export VARIANTFLAGS="-arch ppc -D_NONSTD_SOURCE -isystem /Developer/SDKs/MacOSX10.3.9.sdk"
-Specify the appropriate SDK for the minimum target OS X version and the architecture for the compiler.  For an explanation of _NONSTD_SOURCE, see:
+}}}
+Specifies the appropriate SDK for the minimum target OS X version and the architecture for the compiler.  For an explanation of _NONSTD_SOURCE, see:
 http://developer.apple.com/documentation/Darwin/Reference/ManPages/man5/compat.5.html
 
-**** Using a Custom Makefile ****
+=== Using a Custom Makefile ===
 
 Type the following in Terminal:
 
+{{{
 cd {path}/BOINC_dev/boinc_samples/example_app/
 Make -f MakeMacExample.sh clean all
+)))
 
-The elements of our custom Makefile correspond to those described in our script, except that we include in the CXXFLAGS either 
--DMAC_OS_X_VERSION_MIN_REQUIRED=1030 (for GCC-3.3), or  either -mmacosx-version-min=10.4 or -mmacosx-version-min=10.5 (for GCC-4.0) instead of setting the environment variable MACOSX_DEPLOYMENT_TARGET.
+The elements of our custom Makefile correspond to those described in our script, except that we include in the `CXXFLAGS` either 
+`-DMAC_OS_X_VERSION_MIN_REQUIRED=1030` (for GCC-3.3), or  either `-mmacosx-version-min=10.4` or `-mmacosx-version-min=10.5` (for GCC-4.0) instead of setting the environment variable `MACOSX_DEPLOYMENT_TARGET`.