Building BOINC Clients on Macintosh OSX
Written by Charlie Fenton
Last updated 9/8/05
This document has instructions for building BOINC for Macintosh OSX, plus information for building science projects to run under BOINC Macintosh OSX.
Building BOINC Manager with embedded Core Client plus libraries libboinc.a and libboinc_graphics_api.a
Substitute the appropriate path for [boincparent] throughout this document. This is the parent directory containing the boinc/ 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:
ln -s [realpath] [boincparent]/wxMac-2.6.1
(Note that the GNU compiler and linker will not recognize a Macintosh alias created by the Finder.)
Throughout this document, [boincpath] is shorthand for [boincparent]/boinc.
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.
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, all BOINC software must be compiled using GCC version 3.3, including the WxWidgets and cURL libraries.
Beware of using the wrong compiler! Apple's release notes for GCC 4.0 say:
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
Elsewhere on Apple's web site is the warning:
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:
export CC=/usr/bin/gcc-3.3;export CXX=/usr/bin/g++-3.3
To make sure that other XCode projects (such as client science applications) use GCC 3.0, do the following:
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."
One-Time Setup for BOINC Manager and embedded Core Client
This section describes building two libraries needed by BOINC: wxWidgets for the Macintosh, wxMac-2.6.1, and curl-7.14.0.
XCode 1.5 installs autoconf version 2.57 and automake 1.63. XCode 2.0 installs autoconf 2.59 and automake 1.63. 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:
export PATH=/usr/local/bin:$PATH
The wxWidgets library is needed only by the BOINC Manager. If you are not building the BOINC Manager, you can skip ahead to step 2 below.
(1) First download wxMac-2.6.1 from www.wxwidgets.org into your [boincparent]directory and build it:
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.
First set the CPPFlags environment variable. If you are building under OS 10.4:
If you have installed autoconf or automake at this path:
export PATH=/usr/local/bin:$PATH
export CPPFLAGS="-isysroot /Developer/SDKs/MacOSX10.3.9.sdk -DMAC_OS_X_VERSION_MAX_ALLOWED=1030";export CC=/usr/bin/gcc-3.3;export CXX=/usr/bin/g++-3.3
If you are building under OS 10.3:
export CPPFLAGS="-DMAC_OS_X_VERSION_MAX_ALLOWED=1030"
Then continue building wxMac-2.6.1:
cd [boincparent]/wxMac-2.6.1
mkdir osx-build
cd osx-build
../configure --disable-shared --with-opengl --disable-webkit
If you are building under OS 10.4, set the LDFlags environment variable after the configure but before the make:
export LDFLAGS="-isysroot /Developer/SDKs/MacOSX10.3.9.sdk -Wl,-syslibroot,/Developer/SDKs/MacOSX10.3.9.sdk"
make
(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).
Download curl-7.14.0 from http://curl.haxx.se/download.html into your [boincparent] directory.
Open a new terminal window to reset your session environment variables and set the working directory:
f you have installed autoconf or automake at this path:
export PATH=/usr/local/bin:$PATH
export CC=/usr/bin/gcc-3.3;export CXX=/usr/bin/g++-3.3
cd [boincparent]/curl-7.14.0
./configure --enable-shared=NO
If you are building under OS 10.4, set the CPPFlags and LDFlags environment variables after the configure but before the make:
export CPPFLAGS="-isysroot /Developer/SDKs/MacOSX10.3.9.sdk"
export LDFLAGS="-isysroot /Developer/SDKs/MacOSX10.3.9.sdk -Wl,-syslibroot,/Developer/SDKs/MacOSX10.3.9.sdk"
make
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.
Building the BOINC Manager with embedded Core Client, plus
BOINC libraries, screensaver and helper applications
(1) Double-click on [boincpath]/mac_build/boinc.pbproj to launch the XCode development IDE with the BOINC project.
(2) Select the appropriate cross-development sdk as follows:
- 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.
If you wish to build only the libraries, then just build the 3 targets libboinc, gfxlibboinc and api_libboinc.
(4) In the Active Build Style popup, choose Development (for debugging) or Deployment (for release builds.)
(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.
(6) If you are building the screensaver, be sure to unstuff the file:
[boincpath]/clientgui/mac/BOINCSaver.nib.sit
(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,
Info.plist (under the resources group)
SystemMenu-Info.plist
ScreenSaver-Info.plist
Installer-Info.plist
(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:
-dir /Library/Application\ Support/BOINC\ Data/
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:
-redirectio
These arguments will be used only when running the BOINC Core Client from XCode using XCode's Run or Debug commands.
Building the installer and packaging it for disribution
After creating the deployment build of all targets using Build_All, do the following in Terminal.
Set root permission:
sudo sh
Set the current directory to the root directory of the boinc tree:
cd [boincpath]
Invoke the release_boinc.sh script with the three parts of version number as arguments. For example, if the version is 3.2.1:
source mac_installer/release_boinc.sh 3 2 1
(This will create a director "BOINC_Installer" in the parent directory of the current directory. Inside that will be three directories and two zip files.
If the version is 3.2.1, the zip files will be boinc_3.2.1_macOSX.zip and boinc_3.2.1_powerpc-apple-darwin.zip, and the directories will have the same names as their zipped counterparts.
An additional directory named SymbolTables contains the executables with full debugging symbols; these are useful when interpreting stack dumps in error reports.
BOINC SETI client application
ONE_TIME SETUP for BOINC SETI client application
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:
export PATH=/usr/local/bin:$PATH
(1) Open a new terminal window to reset your session environment variables and set the working directory:
cd [setipath]
(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.
export PROJECTDIR=[setipath]
export BOINCDIR=[boincpath]
If your autoconf and automake are in /usr/local/bin/:
export PATH=/usr/local/bin:$PATH
(2) Run Configure to create the correct config.h file:
./_autosetup
./configure --disable-server --with-apple-opengl-framework --disable-dynamic-graphics
(3) Copy the correct libjpeg.a into [path]/seti_boinc/jpeglib/
(4) Create a symbolic link [setipath]/boinc pointing to the boinc directory
cd [setipath]
ln -s [boincpath] ./boinc
Building the BOINC SETI client application
The XCODE project for building the BOINC SETI@home client application is
[setipath]/mac_build/seti_boinc.xcode.
There is an optional api setMacIcon() in the libboinc_api.a library. This allows science applications to 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:
(1)Use "/Developer/Applications/utilities/Icon Composer.app" to create a xxx.icns file. (Use any name you wish instead of xxx.)
(2) Convert the xxx.icns file to an app_icon.h file as follows: in Terminal, run:
MakeAppIcon_h <source_file> <dest_file>
(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.
(3) In the science application's main(), add
#include "app_icon.h"
and call:
setMacIcon(argv[0], MacAppIconData, sizeof(MacAppIconData));
(4) The science application must link with Carbon.framework to use setMacIcon().