Substitute the appropriate path for [boincparent] throughout this document. This is the parent directory containing the boinc/ or boinc_public/ tree. If used, the following three directories must also be at the top level of [boincparent]/:\
wxMac-2.6.1/, curl-7.14.0 and jpeg-6b. If you wish to keep these directories elsewhere or to give them different names, you can create a UNIX symbolic link to the actual directory using the command, for example: \
These directions are for building under OS X version 10.4.x (Tiger) using XCode Developer Tools version 2.0, or OS X version 10.3.9 (Panther) using XCode 1.5. \
If you are building under OS 10.4, you must first install XCode's optional Cross-Development SDK for system 10.3.9 from the XCode Tools CD. This guarantees that all builds are backward compatible to OS 10.3.9. This is not necessary for building under OS 10.3.\
\cf0 If you are building with XCode 2.0 under OS 10.4, the default compiler is GCC 4.0. Software compiled with GCC 4.0 cannot run on systems earlier than OS 10.3.9. To ensure compatibility back to OS 10.3.0,
\f3\i \cf0 If your application must support versions of Mac OS X prior to 10.3.9, you must not use the GCC 4.0 compiler. Instead, build your project using the GCC 3.3 compiler\
\cf0 Elsewhere on Apple's web site is the warning:\
\f3\i Do not link C++ modules compiled with one of these compilers against modules compiled with the other. Even if the modules appear to link correctly, C++ ABI differences may still cause problems that will not manifest themselves until run time.
The BOINC XCode project is already set up to use GCC 3.3. For builds from the command-line under OS 10.4, you must set the environment variables CC and CXX. For the bash shell:\
In the XCode project, select your target under the Groups & Files column. Press command-I to open the info window for the target, and select the "Rules" tab. Press the "+" at the bottom of the window twice to create two new rules. Set one rule for C sources to use GCC 3.3, set the other rule for C++ sources to use GCC 3.3. Close the window. Repeat this for each target in the project.\
\
If you are building under OS 10.3.9, the default compiler is GCC 3.3, so these steps are not necessary (but they won't do any harm).\
If you are building a science project to run under BOINC Macintosh OSX, be sure to read the last section of this document, titled "Building the BOINC SETI client application."\
\f3\i To determine the version number, type "autoconf --version" or "automake --version" . Building wxMac-2.6.1 and curl-7.14.0 require autoconf 2.59 and automake 1.93 or later. Building the BOINC SETI application also requires these.\
Upgrades for autoconf and automake are available from www.gnu.org. XCode installed these utilities in the /usr/bin/ directory, but the upgrades by default will install in /usr/local/bin/. If you install there, you must also set your PATH environment variable to include that location before proceeding with any of the steps below; type the following at the start of your terminal session:\
You will need to set the environment variables CPPFLAGS and LDFLAGS as described below. These commands are for the bash shell; use the equivalent commands if you are running a different UNIX shell. Some of these environment variables allow the application to be built using the OS 10.3.9 compatibility SDK.\
(2) The cURL library is needed only by the BOINC Core Client. If you are not building either the BOINC Manager or the Core Client, you can skip ahead to step 3 below (The BOINC Manager includes the Core Client in its application bundle).\
This will create the static library at [boincparent]/curl-7.14.0/lib/.libs/libcurl.a. The Finder hides file and directory names which begin with a period, so you must use the Terminal tool to see or manipulate this file.\
\
(3) Building the BOINC graphics library libboinc_graphics.a uses jpeglib.h. If you aren't building this library, you can skip this step.\
\
Download jpeg-6b from www.ijg.org into your [boincparent] directory. You don't need to configure or build this library; BOINC only uses the jpeglib.h header file, and expects it to be at the path [boincparent]/ jpeg-6b/jpeglib.h.\
- select the boinc project icon at the top of the Groups & Files column\
- press command-i to open the Project "boinc" info window.\
- In the "General" tab, set the popup menu "Cross-Develop Using Target SDK." For OS 10.4, select "MacOSX10.3.9.sdk"; for OS 10.3 select "current Mac OS".\
(3) In the Active Target popup, select mgr_boinc or Build_All. Build_All also builds the three libraries libboinc_api.a, libboinc_graphics_api.a and libboinc.a, which are used to build science applications such as SETI@home. These libraries are not needed by the BOINC Manager or Core Client. In addition, Build_All builds the screensaver BOINCSaver.saver and the installer helper application Postinstall.app.\
(5) If you have switched Build Style, be sure to do a "Clean All Targets" from the Build menu; otherwise object files from the old build style will not be rebuilt in the new build style.\
(7) Select Build from the Build menu. I suggest you also open the Detailed Build Results window from the Build menu. Wait a long time while it compiles.\
(8) In addition to the BOINC Manager BOINC.app and Core Client boinc, the mgr_boinc target will also build the SystemMenu.bundle framework and a small helper utility SetVersion. \
(9) SetVersion is run automatically as part of the build process to update the following Mac version information files using the contents of version.h:\
InfoPlist.strings, \
\CocoaLigature0 Info.plist (under the resources group)\
(10) The boinc-client, SystemMenu.bundle and InfoPlist.strings will all be embedded automatically inside the BOINC.app application bundle as part of the build process.\
(11) If you wish to run the Core Client under the debugger, you will need to set up the command-line arguments. In the Groups & Files column of the XCode project window, select "BOINC_Client" under Executables. Then click on the round blue "info" button at the top of the project window to open the info window. In the info window's Arguments tab, add the following line to the Argument list:\
\f1 \cf0 Normally, stdio and stderr output will be sent to XCode's console. If you want stdio and stderr to be redirected to files as BOINC normally does, add a second line to the Argument list:\
NOTE: the file extensions (such as .app and .saver) may be hidden by the Finder. You can check an item's extension by selecting it in the Finder and using Get Info function from the Finder's File menu.\
(6) From the Finder, open [boincpath]/mac_installer/BOINC.pmproj (if running OS 10.3, use BOINC.pmsp). it will open in the PackageMaker application. In the Files tab, set the path to your Pkg_Root directory. in the Resources tab, set the path to your Installer_Resources directory. Update the version number in multiple places in the Description and Version tabs.\
(2)After selecting the directory you just created and populated, select \ul Create archive\ulnone from the Finder's File menu. This will zip the file. (Note: if you want to stuff the file instead of zipping it, be sure to uncheck "stuff originals instead of aliases" in DropStuff's preferences.)\
\f3\i \cf0 Please see the discussion about versions of autconf and automake in the section "ONE_TIME SETUP for BOINC Manager and embedded Core Client" above. If you install upgrades for these in /usr/local/bin/, type the following at the start of your terminal session:\
(2) You will need to set some environment variables as described below. These commands are for the bash shell; use the equivalent commands if you are running a different UNIX shell. \
There is an optional api setMacIcon() in the libboinc_api.a library. This allows science applications to \CocoaLigature0 display an application icon in the Dock) and in the Finder. (The icon does not appear in the Dock until the application displays graphics.) To implement this, do the following:\
\f1 (The MakeAppIcon_h command-line utility is built by the Mac boinc XCode project iin the "boinc/mac_build/build/" directory.) Add the app_icon.h file to your science application's project.\
