Installing Code::Blocks from source on Mac OS X

From Code::Blocks
Revision as of 12:11, 23 August 2006 by Afb (talk | contribs) (Libtool library used but `LIBTOOL' is undefined)

These are instructions on how to build Code::Blocks under Apple Mac OS X. They have been tested under Mac OS X version 10.3, but should work under Mac OS X 10.4 (PowerPC and Intel) and old Mac OS X 10.2 and 10.1 as well.

We will be building everything from scratch using the source code, and not use any available package managers like DarwinPorts, Fink, Gentoo or RPM. Packaging can be done later, once it has reached a more stable release.

Install Xcode 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/

This will install Apple versions of:

http://www.gnu.org/software/gcc/ http://www.gnu.org/software/gdb/ http://www.gnu.org/software/make/

Note: 2006/04 Apple pulled all the old links in order to promote Mac OS X 10.4, 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.3, you want Xcode 1.5. For Mac OS X 10.1-10.2, latest Dev Tools.

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/ http://www.gnu.org/software/automake/ http://www.gnu.org/software/libtool/

Currently Code::Blocks requires versions:

  • autoconf 2.50+
  • automake 1.7+
  • libtool 1.4+

Check what you have, with --version (note that GNU libtool is called glibtool on Mac)

Universal Binaries

If you are building for Mac OS X 10.4, you might want to build "Universal Binaries " These are binaries that contain code for both PowerPC ("powerpc") and Intel ("i686")

The basic flags that needs to be added are: 

CFLAGS += "-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"

Some caveats:

  • 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

Build wxWidgets 2.6

Download the Mac release

http://wxwidgets.org/downloads/#latest_stable

Configure and (GNU) Make

./configure --enable-shared --enable-monolithic --with-opengl --with-mac \
            --with-png=builtin --with-tiff=builtin --with-jpeg=builtin && make

Install into Destination

sudo make install

Install Subversion client

http://subversion.tigris.org/

Build CodeBlocks from SVN

Download the source code

https://www.codeblocks.org/source_code.shtml

Bootstrap with Autotools

The "bootstrap" script doesn't work on Mac OS X, so do it manually: 

./update_revision.sh
glibtoolize --force --copy && \
aclocal-1.7 && \
cat /usr/share/aclocal/libtool.m4 >> aclocal.m4 && \
autoheader && \
automake-1.7 --include-deps --add-missing --foreign --copy && \
autoconf

Configure and (GNU) Make

./configure --disable-code-completion && make

Note: couldn't get the code completion code to work, so disabling it (for now, rev 2886) 

nativeparser.cpp: In member function `size_t 
   NativeParser::FindAIMatches(Parser*, std::queue<ParserComponent, 
   std::deque<ParserComponent, std::allocator<ParserComponent> > >, 
   TokenIdxSet&, int, bool, bool, bool, short int, TokenIdxSet*)':
nativeparser.cpp:1379: error: no match for `std::_Rb_tree_iterator<int, const 
   int&, const int*>& == int' operator
nativeparser.cpp:1381: error: no match for `std::_Rb_tree_iterator<int, const 
   int&, const int*>& != int' operator
nativeparser.cpp:1394: error: no match for `std::_Rb_tree_iterator<int, const 
   int&, const int*>& == int' operator

Install into Destination

sudo make install

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.

Way 1. Mac OS (resource)

http://developer.apple.com/documentation/Carbon/Reference/Resource_Manager/

Handy while developing, as you only need to add an icon.

Files needed:

First we install the program to the PREFIX directory of your choice: 

$PREFIX/bin
$PREFIX/lib
$PREFIX/share/codeblocks

Add a custom icon to the application, and make it receive events: 

gunzip CodeBlocks.r.gz
sudo /Developer/Tools/Rez -d __DARWIN__ -t APPL -d __WXMAC__ \
                          CodeBlocks.r Carbon.r -o $PREFIX/bin/codeblocks
sudo /Developer/Tools/SetFile -a C $PREFIX/bin/codeblocks

Without the icon part, this could also have be written as just: 

sudo `wx-config --rezflags` $PREFIX/bin/codeblocks

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


Way 2. NeXT (bundle)

http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFBundles/

This does not involve resources, and is more relocatable.

Files needed:

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).

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/CodeBlocks.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.

Retrieved from "https://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X&oldid=3697"