Installing Code::Blocks from source on Mac OS X
These are instructions on how to build Code::Blocks under Apple Mac OS X. They have been tested under Mac OS X version 10.4 (PowerPC and Intel), and should work similarly on the newer Mac OS X 10.5 and 10.6 as well.
We will be building everything from scratch using the source code, and not use any available package managers like MacPorts, Fink, Gentoo or RPM. Packaging can be done later, once it has reached a more stable release.
Update: building for MacPorts can be found at the end of the document.
- 1 Install Developer Tools
- 2 Check Autotools versions
- 3 FYI: Universal Binaries
- 4 FYI: Compilers
- 5 FYI: ANSI or UNICODE
- 6 FYI: 32-bit or 64-bit
- 7 Build wxWidgets
- 8 Bundle library for Mac
- 9 Install Subversion client
- 10 Build CodeBlocks from SVN
- 11 Bundle application for Mac
- 12 FYI: Darwin vs. Mac OS X
- 13 Install with MacPorts
Install Developer Tools
If they didn't come bundled with Mac OS X, get the Xcode Tools (or Developer Tools for older Mac OS X) from http://developer.apple.com/tools/ or from your install disk.
This will install Apple versions of:
- http://www.gnu.org/software/gcc/ (GNU Compilers)
- http://www.gnu.org/software/gdb/ (GNU Debugger)
- http://www.gnu.org/software/make/ (GNU Make)
Apple regularly pulls all older links in order to promote newer Mac OS X, but all the old developer tools can be downloaded from ADC at http://connect.apple.com/
You need a (free) developer registration with Apple first, in order to log in there. For Mac OS X 10.4, you want (at least) Xcode 2.2, since earlier versions were buggy.
Check Autotools versions
Depending on your OS version, you might need to download and compile new versions of these:
- http://www.gnu.org/software/autoconf/ (GNU Autoconf)
- http://www.gnu.org/software/automake/ (GNU Automake)
- http://www.gnu.org/software/libtool/ (GNU Libtool)
Check what you have, with --version (note that GNU libtool is called "glibtool" on Mac OS X)
Currently Code::Blocks requires versions:
- autoconf 2.50+
- automake 1.7+ (1.9+ needed in order to build the dist tarball)
- libtool 1.4+ (1.5.8+ highly recommended to get some bug fixes)
For Mac OS X 10.4, you will only need an upgraded (local) installation of automake 1.9.x.
You can download "automake-1.9.6.tar.gz" and configure and install it with something like:
./configure --prefix=/usr/local --program-suffix=-1.9 make sudo make install sudo cp -pi /usr/share/aclocal/libtool.m4 /usr/local/share/aclocal-1.9/
Since it's now known as "automake-1.9", it won't interfere with the regular "automake"
If you would rather have the new version to be called when calling "automake", let it install into /usr/local and put /usr/local/bin before /usr/bin in your PATH.
Download libtool source. The following instructions will overwrite your current version of libtool with the one you just downloaded.
cd /libtool-*/ ./configure --prefix=/usr --program-prefix=g make sudo make install
Note that this will replace the system version of glibtool, which might have some compatibility issues with building other software.
FYI: Universal Binaries
If you are building for Mac OS X 10.4 or later, you might want to build "Universal Binaries " These are binaries that contain code for both PowerPC ("ppc" arch) and Intel ("i386" arch)
The basic flags that needs to be added are:
CFLAGS += "-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc" CXXFLAGS += "-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc"
(You only need the sysroot parameter on PowerPC Macintosh, not on a Intel Macintosh) The "-arch i386 -arch ppc" is what tells the compiler to build a "universal" (or "fat") binary.
Usually it's easiest to build one version for "powerpc-apple-darwin8", and one version for "i686-apple-darwin8", and then merge them with "lipo"
./configure --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 ./configure --host=i686-apple-darwin8 --target=i686-apple-darwin8
- pre-compiled headers might fail with a "no main" error. If they do, add a -c to only compile them
- when cross-compiling, tools like auto_revision might fail to build. copy these from a native build
- the Tiger compilers might crash from time to time, but that is only to be expected (it seems)...
See Technical Note TN2137: Building Universal Binaries from "configure"-based Open Source Projects
When building for older versions of the SDK, you want to make sure to use the same compiler.
CC = gcc-4.0 CXX = g++-4.0
Mac OS X 10.6 has GCC 4.2 as the default compiler, which won't work for the Mac OS X 10.4 SDK.
FYI: ANSI or UNICODE
For the moment we are using "ANSI" (--disable-unicode, default) for Mac OS X 10.3 and earlier, and "UNICODE" (--enable-unicode, optional) for Mac OS X 10.4 and later.
FYI: 32-bit or 64-bit
Code::Blocks currently uses wxMac (wxOSX/Carbon), which is 32-bit only. So it's not possible to build for "x86_64".
When Code::Blocks (and requirements) has been updated to use wxOSX/Cocoa, then a 64-bit version might be built too.
Download the source code
Download the tarball for the wxMac release:
Apply necessary patches
Don't forget to apply any released patches!
Configure and (GNU) Make
mkdir mac-build cd mac-build ../configure --enable-shared --enable-monolithic --enable-unicode --with-mac --with-opengl \ --with-png=builtin --with-jpeg=builtin --with-tiff=builtin --with-expat=builtin nice make
note: the easiest way to build a Universal Binary with wxWidgets is the new flag: --enable-universal_binary (you need wxWidgets 2.6.4+)
--enable-universal_binary --with-macosx-sdk=/Developer/SDKs/MacOSX10.4u.sdk --with-macosx-version-min=10.4
Install into Destination
sudo make install
Bundle library for Mac
To avoid having the Code::Blocks user having to compile or install wxWidgets themselves, we can bundle it with our application so that it is contained in the application bundle. This could also be done by statically linking wxWidgets, but with dynamic linking we can share the wxWidgets library between all applications using wxWidgets (not just Code::Blocks)
Way One: Library (dynamic)
/usr/local/include/wx-2.8/wx/wx.h /usr/local/lib/libwx_macu-2.8.dylib -> libwx_macu-2.8.0.dylib /usr/local/lib/libwx_macu-2.8.0.dylib -> libwx_macu-22.214.171.124.0.dylib /usr/local/lib/libwx_macu-126.96.36.199.0.dylib
To bundle our shared library with the application, we include it in "MacOS" and change the path:
install_name_tool -id @executable_path/libwx_macu-2.8.0.dylib
@executable_path will be replaced with e.g. /Developer/Applications/CodeBlocks.app/Contents/MacOS
Way Two: Framework (bundle)
/Library/Frameworks/wx.framework/Headers -> Versions/Current/Headers /Library/Frameworks/wx.framework/wx -> Versions/Current/wx /Library/Frameworks/wx.framework/Versions/Current -> 2.8 /Library/Frameworks/wx.framework/Versions/2.8/Headers/wx.h /Library/Frameworks/wx.framework/Versions/2.8/wx -> libwx_macu-2.8.0.dylib /Library/Frameworks/wx.framework/Versions/2.8/libwx_macu-2.8.0.dylib -> libwx_macu-188.8.131.52.0.dylib /Library/Frameworks/wx.framework/Versions/2.8/libwx_macu-184.108.40.206.0.dylib
To bundle our framework with the application, we include it in "Frameworks" and change the path:
install_name_tool -id @executable_path/../Frameworks/wx.framework/Versions/2.8/libwx_macu-2.8.0.dylib
This way it will first look in the framework path (-F), and then in for the shared library path (-L) as usual.
Install Subversion client
On Mac OS X 10.4, you need to install the Subversion (svn) program:
Note: you need SVN for the Code::Blocks revision scripts to work!
Build CodeBlocks from SVN
Download the source code
svn checkout svn://svn.berlios.de/codeblocks/trunk cd trunk
Apply necessary patches
For a list of all available patches, see:
You might need to convert line endings from DOS to Unix first.
Bootstrap with Autotools
You need to use the newer version of automake (see above), for the "bootstrap". (OS X 10.5 users may have recent enough autotools so they may not need to install them)
# if you installed newer autotools under names with suffixes. export AUTOMAKE=automake-1.9 export ACLOCAL=aclocal-1.9 # do bootstrap. you may need to adapt /usr/share/aclocal # to whatever other location you may use # (for instance, in my case, /usr/local/share/aclocal) ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
If you have the Mono.framework installed, then it probably set up a symlink like:
/usr/bin/pkg-config -> /Library/Frameworks/Mono.framework/Commands/pkg-config
Unless you have a "proper" pkg-config installation the Code::Blocks configure will fail, so move this symbolic link aside.
Note: the easiest way to build a Universal Binary for Code::Blocks is to build once for PowerPC (-arch ppc) and once for Intel (-arch i386), and then merge them (with lipo) afterwards.
mkdir ppc-build cd ppc-build ../configure --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 --with-contrib-plugins=all cd .. mkdir x86-build cd x86-build ../configure --host=i686-apple-darwin8 --target=i686-apple-darwin8 --with-contrib-plugins=all cd ..
Note: You need to patch the location of the pre-compiled headers, or it will generate them in the same place for both arch.
There is a bug in the glibtool of Mac OS X 10.4, that fails to link C++ libs:
ld: multiple definitions of symbol ___umoddi3 /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/libgcc.a(_umoddi3.o) private external definition of ___umoddi3 in section (__TEXT,__text) /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../libgcc_s.10.4.dylib(_umoddi3_s.o) definition of ___umoddi3 ld: multiple definitions of symbol ___umoddi3 /usr/lib/gcc/i686-apple-darwin8/4.0.1/libgcc.a(_umoddi3.o) private external definition of ___umoddi3 in section (__TEXT,__text) /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libgcc_s.10.4.dylib(_umoddi3_s.o) definition of ___umoddi3
To work around this, you need to edit the generated "libtool" script manually:
177c177 < whole_archive_flag_spec="-all_load \$convenience" --- > whole_archive_flag_spec="" 6921c6921 < whole_archive_flag_spec="-all_load \$convenience" --- > whole_archive_flag_spec=""
This bug has been fixed in GNU libtool 1.5.8 and later.
"nice" isn't strictly needed, it just makes the compile run at a lower process priority
For the Universal Binary build:
cd ppc-build nice make cd .. cd x86-build nice make cd ..
Install into Destination
"sudo" asks you for an admin password, in order to get install permissions
sudo make install
For the Universal Binary build:
cd ppc-build make install DESTDIR=/tmp/ppc cd .. cd x86-build make install DESTDIR=/tmp/x86 cd .. lipomerge /tmp/ppc /tmp/x86 /tmp/fat
Where "lipomerge" is a custom shell script:
Bundle application for Mac
After building codeblocks in the regular Unix way, you need to bundle it with the icons and various other info that it needs to make a regular stand-alone Macintosh application.
There are two ways of accomplishing this, old Mac OS-style resource or NeXT-style bundle. The old resources are handy while developing, while bundles are more suitable for release.
Note: You need to use either of these methods, or your application will launch in the background behind all other windows and will be unable to receive any events!
Way One: Mac OS (resource)
Handy while developing, as you don't need to create a whole bundle.
First we install the program to the PREFIX directory of your choice:
$PREFIX/bin $PREFIX/lib $PREFIX/share/codeblocks
Note: on the Intel Macintoshes, the icon comes up as "broken" (apparently it assumes that all apps with resforks are Classic)
Start the application with a small prefix shell wrapper like this:
DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:$PREFIX/lib export DYLD_LIBRARY_PATH $PREFIX/bin/codeblocks --prefix=$PREFIX
You don't need the "DYLD_LIBRARY_PATH" stuff, if you are installing to a system directory.
Common PREFIX Settings
Way Two: NeXT (bundle)
This does not involve resources, and is more relocatable.
- codeblocks.plist (generated, rename to "Info.plist")
- codeblocks.sh (shell wrapper, rename to "CodeBlocks")
#!/bin/sh DIR="`dirname \"$0\"`/.." BIN="$DIR/bin" LIB="$DIR/lib" DYLD_LIBRARY_PATH="$DYLD_LIBRARY_PATH:$LIB" export DYLD_LIBRARY_PATH exec "$BIN/codeblocks" --prefix="$DIR"
- app.icns (icons are available in src/src/resources/icons)
The MacOS program will just be a shell wrapper that calls "bin/codeblocks", like above. Traditionally the bundle would include Frameworks and Resources, but we'll just avoid those here and use the regular "lib" and "share/codeblocks" instead (just as with a regular install). These temporary directories are listed in italic below, they're not really used in bundles...
Setup a hierarchy like this, and copy the files from the regular build/install and the above file list to it:
CodeBlocks.app CodeBlocks.app/Contents/ CodeBlocks.app/Contents/Info.plist CodeBlocks.app/Contents/MacOS/ CodeBlocks.app/Contents/MacOS/CodeBlocks CodeBlocks.app/Contents/Resources/ CodeBlocks.app/Contents/Resources/app.icns CodeBlocks.app/Contents/bin/ CodeBlocks.app/Contents/lib/ CodeBlocks.app/Contents/share/codeblocks/
The CodeBlocks application can now be moved with the Finder, and started up like a regular Mac application. (the nightly build includes a more advanced Info.plist and more icons - for also mapping all the files that the application can open, like source code and header files and such)
Proper Application Bundling
To avoid the shell wrapper, the binary can now be moved from "bin/codeblocks" to "MacOS/CodeBlocks". Helper files are moved from "share/codeblocks" to "Resources". The dynamic libraries are moved from "lib" to "MacOS":
mv bin/codeblocks MacOS/CodeBlocks rmdir bin mv lib/* MacOS/ rmdir lib mv share Resources/
To avoid having to use a DYLD_LIBRARY_PATH, we rename the shared libraries (with the install_name_tool program) from e.g. /usr/local/lib/ to @executable_path/:
install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib \ @executable_path/libcodeblocks.0.dylib MacOS/CodeBlocks
The libraries can have their names changed using the -id parameter:
install_name_tool -id @executable_path/libcodeblocks.0.dylib MacOS/libcodeblocks.0.dylib
You also need to change all of the loadable bundles for the plugins:
for so in Resources/plugins/*.so do install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib \ @executable_path/libcodeblocks.0.dylib $so done
You can check the result, what libraries/frameworks it links to, with:
otool -L CodeBlocks
Optionally you can then repeat the process, for the wx library too...
Here is a full script to do the job... It assumes to be executed at the same directory level as the CodeBlockSVN.app directory that will receive all the stuff... maybe enhanced but it is a first try that do work when packaging an OS X SVN build.
#!/bin/sh cp /usr/local/bin/codeblocks ./CodeBlocksSVN.app/Contents/MacOS/CodeBlocks cp /usr/local/bin/cb_share_config ./CodeBlocksSVN.app/Contents/MacOS cp /usr/local/bin/cb_console_runner ./CodeBlocksSVN.app/Contents/MacOS cp /usr/local/bin/codesnippets ./CodeBlocksSVN.app/Contents/MacOS cp /usr/local/lib/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS cp /usr/local/lib/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS cp /usr/local/lib/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS install_name_tool -id @executable_path/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libcodeblocks.0.dylib install_name_tool -id @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libwx_macu-2.8.0.dylib install_name_tool -id @executable_path/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libwxsmithlib.0.dylib install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/CodeBlocks install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/CodeBlocks install_name_tool -change /usr/local/lib/libwxsmithlib.0.dylib @executable_path/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/CodeBlocks install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/codesnippets install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/codesnippets install_name_tool -change /usr/local/lib/libwxsmithlib.0.dylib @executable_path/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/codesnippets install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/cb_share_config install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/cb_share_config install_name_tool -change /usr/local/lib/libwxsmithlib.0.dylib @executable_path/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/cb_share_config install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/cb_console_runner install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/cb_console_runner install_name_tool -change /usr/local/lib/libwxsmithlib.0.dylib @executable_path/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/cb_console_runner install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libcodeblocks.0.dylib install_name_tool -change /usr/local/lib/libwxsmithlib.0.dylib @executable_path/libwxsmithlib.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libcodeblocks.0.dylib install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libwxsmithlib.0.dylib install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib ./CodeBlocksSVN.app/Contents/MacOS/libwxsmithlib.0.dylib cp -R /usr/local/share/codeblocks/ ./CodeBlocksSVN.app/Contents/Resources/share/codeblocks for dotso in ./CodeBlocksSVN.app/Contents/Resources/share/codeblocks/plugins/*.so do #echo $dotso # install_name_tool -id $dotso ./libcodeblocks.0.dylib CodeBlocks install_name_tool -change /usr/local/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib $dotso install_name_tool -change /usr/local/lib/libwx_macu-2.8.0.dylib @executable_path/libwx_macu-2.8.0.dylib $dotso install_name_tool -change /usr/local/lib/libwxsmithlib.0.dylib @executable_path/libwxsmithlib.0.dylib $dotso done
FYI: Darwin vs. Mac OS X
"Darwin is the UNIX technology-based foundation of Mac OS X."
"Pure Darwin" here refers to the Open Source version of the OS:
(that is: Darwin using X11 instead of Aqua for the user interface)
Install with MacPorts
You will need the wxWidgets library, install as port with:
sudo port install wxWidgets
If you want the X11/GTK version on Mac OS X, instead use:
sudo port install wxgtk
After that is installed, you can install Code::Blocks with:
sudo port install codeblocks-devel +aqua
If you want the X11/GTK version on Mac OS X, instead use:
sudo port install codeblocks-devel +x11
This will download the SVN trunk, and any dependencies:
---> Fetching codeblocks-devel ---> Verifying checksum(s) for codeblocks-devel ---> Extracting codeblocks-devel ---> Configuring codeblocks-devel ---> Building codeblocks-devel with target all ---> Staging codeblocks-devel into destroot ---> Packaging tgz archive for codeblocks-devel 1.0_0+aqua+macosx ---> Installing codeblocks-devel 1.0_0+aqua+macosx ---> Activating codeblocks-devel 1.0_0+aqua+macosx ---> Cleaning codeblocks-devel
Note: to upgrade from SVN, you need to uninstall first:
sudo port uninstall codeblocks-devel sudo port clean codeblocks-devel sudo port install codeblocks-devel
This is both because all SVN versions are numbered "0", but also due to a bug in the Code::Blocks build scripts.
Running +aqua (wxMac) version
After the build completes, you can start the program by:
Note that the wxMac application bundle in "MacPorts" is just a wrapper, with symbolic links to /opt/local...
Running +x11 (wxGTK) version
The non-bundled wxGTK version is instead started with:
When running X11/wxGTK programs in Mac OS X, you can use "open-x11" to first start up X11.app and set up $DISPLAY: