CompilingMacOsX

Compiling Inkscape

Requirements

To compile Inkscape from source you will need:

• Mac OS X 10.3 (Power PC) or higher
• Inkscape's source code. You can get the official release source code, a SVN snapshot or a copy of the SVN repository.
• XCode 2.3 on OS X 10.4 (gcc 4.0.1)

To install inkscape dependencies you can use:

• Fink with an unstable installation (does not provide support for loudmouth, the librarie that Inkboard uses, therefore you won't be able to use Inkboard)
• DarwinPorts

Preparing the build using Fink

Installing dependencies

Inkscape can be installed via Fink. Therefore, as for any other package, Fink provides you with a list of its dependencies:

fink show-deps inkscape

Some are mandatory and you must install them:

fink install gtkmm2.4-dev  gconf2-dev gtkspell2-dev intltool libbonobo2-dev libxslt gc automake1.8

You need version 1.8 of automake 1.8 (and not 1.9, the latest in Fink)

Some provide additional functionality in Inkscape

• aspell : check spelling of text elements [Note: I have never seen it working on OS X]
• boost >= 1.32 : auto-organisation of connectors
• gnome-vfs2
• gnome-print
• lcms : color management via LittleCMS

fink install aspell-dev boost gnome-vfs2-dev gnome-print-dev lcms

You may also need to build popt from source (tested on 10.4): [1]

Setting the build environment

Fink's hierarchy is not searched for libraries by default. Therefore, before the configuration starts, some environment variables need to be set. The environment variables are presented in bash syntax here. You can create a file named set_env_variables.sh and copy/paste this inside:

#!/bin/bash
FINK="/sw"
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="-I$FINK/include"
export LDFLAGS="-L$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export PKG_CONFIG_PATH="$FINK/lib/pkgconfig"

In addition, you must make sure that Inkscape is compiled with the compiler version that Fink uses, otherwise Inkscape will not link properly. To determine which compiler to use type:

head -n 5 $FINK/etc/fink.conf | grep "Distribution"

If your fink distribution is 10.4 add:

export CC="gcc-4.0"
export CXX="g++-4.0"

to set_env_variables.sh, else (10.3, 10.4-transitional) add:

export CC="gcc-3.3"
export CXX="g++-3.3"

You can also use ccache (fink install ccache) to speed up the compilation a bit. To do so, modify the compiler lines accordingly:

export CC="ccache gcc-??"
export CXX="ccache g++-??"

Eventually, open a Terminal and, in the directory where you created the file set_env_variables.sh, type:

source set_env_variables.sh

You are ready for to compile and install Inkscape.

Preparing the build using DarwinPorts

Installing dependencies

You can use DarwinPorts to list Inkscape dependencies:

port deps inkscape

Some are mandatory and you can install them with the command:

sudo port install boehmgc gtkmm intltool libxslt

Others provide additional functionality to Inkscape:

• aspell : check spelling of text elements [Note: I have never seen it working on OS X]
• boost : auto-organisation of connectors
• gnome-vfs
• libgnomeprintui
• lcms : color management via LittleCMS
• loudmouth : jabber library used by InkBoard

sudo port install aspell boost gnome-vfs libgnomeprintui lcms loudmouth

Configuring

You might need to build the configure script first (if you compile Inkscape for the first time). Cd to Inkscape's source directory and run:

./autogen.sh

Then run the configure script:

./configure --prefix=/path/to/build/products/ --enable-osxapp

The --prefix option sets the directory where the build products are placed. It must be somewhere you have write access to. The option --enable-osxapp allows you to package Inkscape into an .app bundle in order to access it like a regular OS X application. Remove this option if you only want to build Inskscape, not to package it afterwards. Of course you can add here classic configuration options such as --enable-lcms for color management or --enable-inkboard for whiteboard functionality.

Building and Installing

Just run:

make
make install

Automated compilation

You can try downloading a bash script which automates the processes of updating Inkscape from the svn repository, setting the build environment, building and producing a package of Inkscape. Modify it with your favorite text editor in order to set a correct install prefix and to change configuration options according to your needs. Two scripts are prodived, depending on wether you use Fink or DarwinPorts. [2] [3]

To use this script, place it in the directory where Inkscape source code is and make it executable

chmod +x osxmake_???.sh

To obtain help on how to use it run it with the -h option:

./osxmake_???.sh -h

To run the whole process use the command:

./osxmake_???.sh -s -a -c -b -i -p

Packaging Inkscape into an .app bundle

Creating the .app and a simple .dmg

Assuming that you have used the --enable-osxapp option during configure, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:

cd packaging
./osx-app.sh -s /path/to/build/products/bin/inkscape ../Info.plist macosx

The -s options produces an app bundle stripped of debugging information (which is therefore smaller). Omit this option if you want to keep debugging info.

Either way, this creates two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

Creating a more complete .dmg

The steps that used to comprise this section have since been integrated into the official Inkscape.app build script, refered to above.

Enabling python effects

Many "effects" in the Effect menu of Inkscape use python as a scripting language. Mac OS X ships with python but not with pyXML which is needed by Inkscape effects. You can install a binary version downloadable with the developement builds of Inkscape:

http://inkscape.modevia.com/macosx-snap/?M=D

Or you can install it from source:

1. download the source code from sourceforge
2. unpack the .tar.gz file
3. cd into the newly created directory
4. set the variable MACOSX_DEPLOYMENT_TARGET to the number of your operating system (10.3 for Panther, 10.4 for Tiger. It probably won't work on previous systems). In bash syntax this means typing:

   export MACOSX_DEPLOYMENT_TARGET=10.?

5. move the python files and build C extensions

   python setup.py build

6. install (the install is system wide so you need administrator rights)

   sudo python setup.py install

   and type your password.

Links

Apple Documentation

• Introduction to Runtime Configuration Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

Packaging

• Sveinbjorn Thordarson's Website The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
• Creating OS X application bundles step by step Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
• Bringing your Java Application to Mac OS X I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
• The Gimp .app Howto This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.