CompilingMacOsX

From Inkscape Wiki
Revision as of 11:23, 19 September 2005 by Jiho (talk | contribs) (Removed old information/new which are not relevant eanymore following Bryce advice)
Jump to navigation Jump to search

Compiling and Packaging Inkscape under Mac OS X

Before you start

If you want an Official Release of inkscape, note that from version 0.42 of Inkscape, a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from inkscape's downloads page:

http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the X Windows System. You will need an X Windows Server installed for it to work. You can get the Apple X Server (requires Mac OS X 10.3 or above) here:

http://www.apple.com/downloads/macosx/apple/x11formacosx.html

Compiling How To

Note: You could use the inkscape package from the Fink project to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem usefull.

Requirements:

  1. Mac OS X 10.3 of higher
  2. A full unstable fink installation
  3. Inkscape source code. You can get the official release source code, a CVS snapshot or a copy of the cvs repository (the module name is "inkscape")

Installing dependencies:

In a Terminal type:

fink install �
        intltool �
        glib2 glib2-dev glib2-shlibs �
        gtk+2 gtk+2-shlibs gtk+2-dev �
        libpng3 libpng3-shlibs �
        libsigc++2 libsigc++2-shlibs �
        gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
        libtool14 libtool14-shlibs �
        libxml2 libxml2-shlibs �
        libsigc++2 libsigc++2-shlibs �
        popt popt-shlibs �
        gc gc-shlibs

Fink installs many packages from source so this is usually long.

Setting the build environment:

You need set the following environment variables (taken right out of fink's .info file) for the compilation to work. They are is in bash syntax. You can create a file named set_variables for example and copy/paste this inside:

#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="ccache gcc"
export CXX="ccache g++"
export CFLAGS="-I$FINK/include -O3 -Wall"
export LDFLAGS="-L$FINK/lib"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="$CXXFLAGS"

Then, open a Terminal and, in the directory where yhou created the file, type:

bash
source set_variables

Building:

Open a Terminal and cd to Inkscape's sources directory. Type:

 ./configure --prefix=/some/directory/
 make
 make install

You have to put your build products somewhere you have write access to (for example you home directory) in order to be able to package the application from there afterwards. That is what the --prefix option is for.

Packaging:

The process is automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:

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

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson


Intersting links

Some packaging links: http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ http://gimp-app.sourceforge.net/gimp.app.howto.txt