Building BOINC Client and Manager on Macintosh OSX

Written by Charlie Fenton
Last updated 4/20/15

This document applies to BOINC version 7.4.42 and later.  It has instructions for building the BOINC Client and Manager for Macintosh OSX.  Information for building science project applications to run under BOINC on Macintosh OSX can be found here.  

Note: the information in this document changes from time to time for different versions of BOINC.  For any version of BOINC source files, the corresponding version of this document can be found in the source tree at:
                   boinc/mac_build/HowToBuildBOINC_XCode.rtf

Contents of this document:
• Important requirements for building BOINC software for the Mac.
• Cross-Platform Development.
• Building BOINC Manager with embedded BOINC Client.
• Building BOINC Manager Installer.
• Code Signing the BOINC Manager Installer and Uninstaller
• Debugging and BOINC security.
• Debugging into wxWidgets.
• Installing and setting up Xcode.

Important requirements for building BOINC software for the Mac

Building BOINC for Macintosh OS X is complicated by the fact that Mac OS X is actually 2 different platforms:
	•	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
As of version 6.13.0, BOINC does not support Macintosh PowerPC processors.
Although BOINC supports 64-bit Intel project applications on Mac OS 10.5.0 and above, the only parts of the BOINC client package built as 64-bit executables are the portion of the screensaver coordinator for OS 10.6.x and later, and the BOINC client itself.  The BOINC libraries also include a 64-bit build so that they can be linked with 64-bit project applications.
You need to take certain steps to ensure that you use only APIs that are available in all the OS versions BOINC supports for each architecture. The best way to accomplish this is to use a single development system running OS 10.8.x or later and cross-compile for the various platforms. The remainder of this document describes that process.

The above requirements apply not only to BOINC itself, but also to the WxWidgets, c-ares, cURL, openSSL,  freetype, ftgl and SQLite3 libraries, as well as all project applications.  

Be sure to follow the directions in this document to ensure that these requirements are met.

Starting with version 7.3.0, the BOINC Client supports only Mac OS X 10.5.0 and later. 
Cross-Platform Development
Apple provides the tools necessary to cross-compile for both BOINC Mac platforms on any Mac running OS 10.8.x or later.
You get these tools, including the GCC compilers and system library header files, by installing the Xcode Tools package. 
Building BOINC now requires Xcode Tools version 4.6 or later. Build with Xcode 5.1.1 or earlier to fully support OS X back to OS 10.5.  Xcode 6 or later will build a screensaver which requires OS 10.6 or later, but all other built components will work with OS 10.5 or later.  

You can download Xcode 4.6 or later from Apple's App Store (it is large: about 2 GB).  If you are a member of Apple's Mac Developer Program, you can also download it from Apple's web site: http://developer.apple.com.
Source files are now archived using git.  For details, see:
	http://boinc.berkeley.edu/trac/wiki/SourceCodeGit

Building BOINC Manager with embedded Core Client

Note: building BOINC Manager 7.3.0 and later requires the OS 10.8 SDK or later.

BOINC depends on seven third-party libraries: wxWidgets-3.0.0, c-ares-1.10.0, curl-7.39.0, openssl-1.0.1j,  freetype-2.4.10, ftgl-2.1.3~rc5 and sqlite-3.8.3.  You can obtain the source files from the following URLs.  Clicking on the first URL of each pair will download the tar file.  The second URL will open the third party’s home web page.  On Mac OS X the tar file will usually be downloaded into the Downloads folder.  You will need to expand the tar files by double-clicking on them, which will create a folder and place the appropriate files into that folder. You will need to move these folders later.

wxWidgets-3.0.0 (needed  only if you are building the BOINC Manager):
	http://sourceforge.net/projects/wxwindows/files/3.0.0/wxWidgets-3.0.0.tar.bz2/
	http://www.wxwidgets.org

sqlite-3.8.3 (needed  only if you are building the BOINC Manager):
	http://www.sqlite.org/2014/sqlite-autoconf-3080300.tar.gz
	http://www.sqlite.org/

curl-7.39.0:
	http://curl.haxx.se/download/curl-7.39.0.tar.gz
	http://curl.haxx.se

c-ares-1.10.0 (used by curl):
	http://c-ares.haxx.se/download/c-ares-1.10.0.tar.gz
	http://daniel.haxx.se/projects/c-ares/

openssl-1.0.1j:
	http://www.openssl.org/source/openssl-1.0.1j.tar.gz
	http://www.openssl.org/

freetype-2.4.10 (needed  only if you are building the BOINC default screensaver or a project screensaver):
	http://sourceforge.net/projects/freetype/files/freetype2/2.4.10/freetype-2.4.10.tar.bz2
	http://www.freetype.org/

ftgl-2.1.3~rc5 (needed  only if you are building the BOINC default screensaver or a project screensaver):
	http://sourceforge.net/projects/ftgl/files/FTGL%20Source/2.1.3%7Erc5/ftgl-2.1.3-rc5.tar.gz
	http://sourceforge.net/projects/ftgl

XCode will automatically check compatibility back to OS 10.5 if the following are defined during compilation:
MAC_OS_X_VERSION_MAX_ALLOWED=1050
MAC_OS_X_VERSION_MIN_REQUIRED=1050

These are not done automatically by either the Xcode projects which come with wxWidgets-3.0.0, nor  the AutoMake scripts supplied with wxWidgets-3.0.0, c-ares-1.10.0, curl-7.39.0, openssl-1.0.1j, freetype-2.4.10, ftgl-2.1.3~rc5 and sqlite-3.8.3.  So be sure to use our special scripts to build these packages.
[1] Make sure you are logged into the Mac using an account with administrator privileges.  Create a parent directory within which to work.  In this description; we will call it BOINC_dev, but you can name it anything you wish.

[2] Move the following 7 directories from the Downloads folder into the BOINC_dev folder (omit any you don't need):
    c-ares-1.10.0
    curl-7.39.0
    openssl-1.0.1j
    wf Xcode is obtained from the Apple Store then it will be installed automatically into the Applications folder.  Double-click on the installed Xcode icon to run Xcode.  Xcode will display a dialog allowing you to finish the installation; you must do this before running BOINC's build scripts.  (Some versions of Xcode may not display this dialog until you open a file with Xcode.)
xWidgets-3.0.0-3.0.0
    freetype-2.4.10
    ftgl-2.1.3~rc5
    sqlite-3.8.3

Important: do not change the names of any of these 7 directories.  Remember that the names are case sensitive.

[3] If you have not yet done so, install Xcode and launch it once to accept the license agreement and complete the installation.

[4] Get the BOINC source tree from the repository, and put it in the same BOINC_dev folder.  To do this, type the following in Terminal (if you have problems, you may need to enter sudo and a space before the git command):

cd {path}/BOINC_dev/
git clone http://boinc.berkeley.edu/git/boinc-v2.git boinc

(You may change the name of the boinc directory to anything you wish.)  

If the above method does not work try the following alternate method:

git clone git://boinc.berkeley.edu/boinc-v2.git boinc

The command above retrieves the source code from the HEAD / MASTER (TRUNK) or development branch of the git repository.  For more information on getting the BOINC source code, see:
	http://boinc.berkeley.edu/trac/wiki/SourceCodeGit

[5] Run the script to build the c-ares, curl, openssl, wxWidgets, freetype, ftgl and sqlite3 libraries as follows:

cd {path}/BOINC_dev/boinc/mac_build/
source setupForBoinc.sh -clean

If you don't wish to force a full rebuild of everything, omit the -clean argument.

Note 1: Be sure to run the script using the source command.  Do not double-click on the scripts or use the sh command to run them.
Note 2: This script tries to build all seven third-party libraries: wxWidgets-3.0.0, c-ares-1.10.0, curl-7.39.0, openssl-1.0.1j,  freetype-2.4.10, ftgl-2.1.3~rc5 and sqlite-3.8.3.  When the script finishes, it will display a warning about any libraries it was unable to build (for example, if you have not downloaded them.)  To make it easier to find the error messages, clear the Terminal display and run the script again without -clean.
Note 3: The {path} must not contain any space characters.
Hint: You don't need to type the path to a file or folder into Terminal; just drag the file or folder icon from a Finder window onto the Terminal window.

[6] Build BOINC as follows:

BOINC itself is built  using the boinc.xcodeproj file.  You can either build directly in Xcode (more information below) or run the BuildMacBOINC.sh script:

cd {path}/BOINC_dev/boinc/mac_build/
source BuildMacBOINC.sh

The complete syntax for this script is
source BuildMacBOINC.sh [-dev] [-noclean] [-all] [-lib] [-client] [-help]

The options for BuildMacBOINC.sh are:
	-dev		build the development (debug) build (native architecture only). 
			default is deployment (release) build (universal binary: i386 and x86_64).

	-noclean	don't do a "clean" of each target before building.
			default is to clean all first.

  The following arguments determine which targets to build
	-all		build all targets (i.e. target "Build_All" -- this is the default)

	-lib		build the six libraries: libboinc_api.a, libboinc_graphics_api.a, libboinc.a, libboinc_opencl.a, libboinc_zip.a, jpeglib.a

	-client		build two targets: boinc client and command-line utility boinccmd
			(also builds libboinc.a, since boinc_cmd requires it.)

 Both -lib and -client may be specified to build eight targets (no BOINC Manager or screensaver.)

Note 1: boinc.xcodeproj in the BOINC_dev/boinc/mac_build/ directory builds BOINC.  It can be used either with the BuildMacBOINC.sh script or as a stand-alone project.  The Development build configuration builds only the native architecture and is used for debugging.  The Deployment build configuration builds a universal binary and is suitable for release builds.  If there are any other build configurations, they should not be used as they are obsolete.  

Note 2: To perform a release build under Xcode 4.6 when not using the BuildMacBOINC.sh script, select "Build for archiving" or "Build for Profiling" from Xcode's Product menu.  Under Xcode 5.0 or later, select "Build for Profiling."  To save disk space, do not select "Archive."

Note 3: Using the BuildMacBOINC.sh script is generally easier than building directly in Xcode.  The script will place the built products in the directory BOINC_dev/boinc/mac_build/build/Deployment/ or BOINC_dev/boinc/mac_build/build/Development/ where they are easy to find.  Building directly in Xcode places the built products in a somewhat obscure location; you would normally need to determine this location using Xcode's Organizer window.  

The BOINC Xcode project has built-in scripts which create a text file with the path to the built products at either BOINC_dev/boinc/mac_build/Build_Deployment_Dir or BOINC_dev/boinc/mac_build/Build_Development_Dir.  These files are used by the release_boinc.sh script, but you can also use them to access the built products directly as follows; open the file with TextEdit and copy the path, then enter command-shift-G in the Finder and paste the path into the Finder's  dialog.

The standard release of BOINC version 7.4.42 and later builds only for Macintosh computers with Intel processors.  Most of the executables are built only for the i386 architecture, except the BOINC client which is built only for the x86_64 architecture.  The BOINC libraries and the screensaver are built as universal binaries containing builds for two architectures: i386 and x86_64.

Building BOINC Manager Installer

In order to execute BOINC Manager, you must install it using BOINC Manager Installer. Otherwise, you will encounter an error prompting for proper installation.

To build the Installer for the BOINC Manager, you must be logged in as an administrator.  If you are building BOINC version number x.y.z, type the following in Terminal, then enter your administrator password when prompted by the script:

cd {path}/BOINC_dev/boinc/
source {path}/BOINC_dev/boinc/mac_installer/release_boinc.sh x y z

Substitute the 3 parts of the BOINC version number for x y and z in the above.  For example, to build the installer for BOINC version 7.4.42, the command would be
source {path}/BOINC_dev/boinc/mac_installer/release_boinc.sh 7 4 42
This will create a directory "BOINC_Installer/New_Release_7_4_42" in the BOINC_dev directory, and the installer will be located in '{path}/BOINC_dev/BOINC_Installer/New_Release_7_4_42/boinc_7.4.42_macOSX_x86_64'.

The installer script uses the deployment (release) build of BOINC; it won't work with a development (debug) build.
You can find the current version number in the file {path}/BOINC_dev/boinc/version.h

Code Signing the BOINC Manager Installer and Uninstaller

Mac OS 10.8 introduces a security feature called Gatekeeper, whose default settings won't allow a user to run applications or installers downloaded from the Internet unless they are signed by a registered Apple Developer.  The release_boinc.sh script looks for a file ~/BOINCCodeSignIdentity.txt containing the name of a valid code signing identity stored in the user's Keychain.  If this is found, the script will automatically sign the BOINC installer and BOINC uninstaller using that identity.  For example, if your user name is John Smith, the first line of ~/BOINCCodeSignIdentity.txt would be something like the following:
Developer ID Application: John Smith

If there is no ~/BOINCCodeSignIdentity.txt file, then the script will not sign the installer or uninstaller.  Code signing is not necessary if you won't be transferring the built software over the Internet.   For more information on code signing identities see the documentation for the codesign utility and Apple's Code Signing Guide.  

Debugging and BOINC security

Version 5.5.4 of BOINC Manager for the Macintosh introduced new, stricter security measures.  For details, please see the file BOINC_dev/boinc/mac_installer/Readme.rtf and http://boinc.berkeley.edu/sandbox.php and http://boinc.berkeley.edu/trac/wiki/SandboxUser

The GDB debugger can't attach to applications which are running as a different user or group so it ignores the S_ISUID and S_ISGID permission bits when launching an application.  To work around this, the BOINC Development build does not use the special boinc_master or boinc_project users or groups, and so can be run under the debugger from Xcode.  

The Development build only of the BOINC Manager allows you to change the ownership and permission settings of the BOINC Data and executables by entering an administrator user name and password.  This also streamlines the development cycle by avoiding the need to run the installer for every change.  (To generate the development build under Xcode 4.6, choose "Build" from the product menu, or enter command-B on the keyboard.)

To restore the standard ownerships and permissions, run the installer.

For information on interpreting crash dumps and backtraces, see Mac Backtrace.
Debugging into wxWidgets

The BOINC Xcode project normally links the BOINC Manager with the non-debugging (Deployment) build of wxWidgets, even for the Development build configuration of the Manager.  However, there may be times when you wish to link the Development build of the Manager to the Development build of wxWidgets for debugging, as when you want to step into internal wxWidgets code or put breakpoints in wxWidgets.

You can find instructions for doing this in the comments in the file BOINC_dev/boinc/clientgui/mac/MacGUI.pch.

Installing and setting up Xcode

If Xcode is obtained from the Apple Store then it will be installed automatically into the Applications folder.  Double-click on the installed Xcode icon to run Xcode.  Xcode will display a dialog allowing you to finish the installation; you must do this before running BOINC's build scripts.  (Some versions of Xcode may not display this dialog until you open a file with Xcode.)