Difference between revisions of "CompilingMacOsX"
(slight refactoring of the page to add --enable-osxapp)
Revision as of 10:56, 10 November 2005
Compiling and Packaging Inkscape under Mac OS X
Before you start
If you want an Official Release, 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:
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 Apple's X Server (requires Mac OS X 10.3 or above) here:
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 useful.
- Mac OS X 10.3 of higher
- A full unstable fink installation
- Inkscape's 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")
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 � popt popt-shlibs � gc gc-shlibs automake1.8
You need automake 1.8 and not the latest in fink (1.9.6-1). 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 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="gcc" export CXX="g++" export CPPFLAGS="-I$FINK/include" export LDFLAGS="-L$FINK/lib" export CFLAGS="-O3 -Wall" export CXXFLAGS="$CFLAGS"
Optionaly, to speed up the compilation a bit you could use
ccache if you have it installed:
export CC="ccache gcc" export CXX="ccache g++"
Note: Inkscape won't link properly on OS X 10.4.x using gcc 4 (the default) since many of the libraries it needs in fink are still built with gcc-3.3. Thus, Tiger users will probably want to modify a couple of lines:
export CC="gcc-3.3" export CXX="g++-3.3"
Then, open a Terminal and, in the directory where you created the file
bash source set_variables
Then you need to build the configure script. Cd to Inkscape's source directory and run:
Cd to Inkscape's sources directory and type
./configure --prefix=/path/to/build/products/ --enable-osxapp
--prefix option sets the directory where the build products are placed. It must be somwhere 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.
make make install
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 /path/to/build/products/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
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