Difference between revisions of "CompilingMacOsX"

From Inkscape Wiki
Jump to navigation Jump to search
(Modified the package requirement in DarwinPorts install + info on MMX)
(Moved to GitLab)
Tag: Replaced
 
(193 intermediate revisions by 32 users not shown)
Line 1: Line 1:
== Compiling Inkscape ==
{{MovedToOtherSite|topic=compiling Inkscape|new_url=https://gitlab.com/inkscape/inkscape/-/blob/master/doc/building/mac.md|new_site=GitLab}}
 
=== 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 [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ SVN snapshot] or a copy of the [http://www.inkscape.org/svn.php?lang=en SVN repository].
*XCode 2.3 on OS X 10.4 (gcc 4.0.1)
 
To install Inkscape dependencies you can use:
*Fink with an [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable installation] (does not provide support for loudmouth, the librarie that Inkboard uses, therefore you won't be able to use Inkboard)
*[http://darwinports.opendarwin.org/ 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:
<pre>fink show-deps inkscape</pre>
 
Some are mandatory and you must install them:
<pre>fink install gtkmm2.4-dev  gconf2-dev gnome-vfs2-dev\
  gtkspell2-dev intltool lcms libbonobo2-dev libxslt gc</pre>
 
Some provide additional functionality in Inkscape
* <code>aspell</code> : check spelling of text elements [Note: I have never seen it working on OS X]
* <code>boost >= 1.32</code> : auto-organisation of connectors [Note: is boost still needed?]
* <code>gnome-print</code>
<pre>fink install aspell-dev boost gnome-print-dev</pre>
 
If you use [http://en.wikipedia.org/wiki/MMX MMX optimization] (available on Intel processors) you need version 1.8.5 of automake (and not 1.9.6 which is the latest in Fink). Otherwise you will need suppress the check on the version of automake (see the Configuring section).
<pre>fink install automake1.8</pre>
 
====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 <code>set_env_variables.sh</code> and copy/paste this inside:
<pre>
#!/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"
</pre>
 
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:
<pre>head -n 5 $FINK/etc/fink.conf | grep "Distribution"</pre>
If your fink distribution is 10.4 add:
<pre>
export CC="gcc-4.0"
export CXX="g++-4.0"
</pre>
to <code>set_env_variables.sh</code>, else (10.3, 10.4-transitional) add:
<pre>
export CC="gcc-3.3"
export CXX="g++-3.3"
</pre>
 
You can also use <code>[http://en.wikipedia.org/wiki/Ccache ccache]</code> (<code>fink install ccache</code>) to speed up the compilation a bit. To do so, modify the compiler lines accordingly:
<pre>
export CC="ccache gcc-??"
export CXX="ccache g++-??"
</pre>
 
Eventually, open a Terminal and, in the directory where you created the file <code>set_env_variables.sh</code>, type:
<pre>source set_env_variables.sh</pre>
 
You are ready to configure, compile and install Inkscape. Go to the section 'Configuring' now.
 
=== Preparing the build using DarwinPorts ===
====Installing dependencies====
You can use DarwinPorts to list Inkscape dependencies:
<pre>port deps inkscape</pre>
Some are mandatory and you can install them with the command:
<pre>sudo port install boehmgc gtkmm gnome-vfs intltool libxslt lcms popt</pre>
 
Others provide additional functionality to Inkscape:
* <code>aspell</code> : check spelling of text elements [Note: I have never seen it working on OS X]
* <code>boost</code> : auto-organisation of connectors [Note: is boost still needed?]
* <code>libgnomeprintui</code>
* <code>loudmouth</code> : jabber library used by InkBoard
<pre>sudo port install aspell boost gnome-vfs libgnomeprintui loudmouth</pre>
 
Using [http://en.wikipedia.org/wiki/MMX MMX optimization] (available on Intel processors only) requires that you use automake 1.8 but only automake 1.9.6 is available in DarwinPorts. Therefore, unless you install version 1.8.5 by hand ([http://ftp.gnu.org/gnu/automake/automake-1.8.5.tar.gz]) you will need to disable MMX optimization and to disable the check on automake version during the configure step.
 
====Setting the build environment====
 
 
 
 
=== 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:
<pre>./autogen.sh</pre>
 
Then run the configure script:
<pre>./configure --prefix=/path/to/build/products/ --enable-osxapp</pre>
 
The <code>--prefix</code> option sets the directory where the build products are placed. It must be somewhere you have write access to. The option <code>--enable-osxapp</code> allows you to package Inkscape into an <code>.app</code> 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 <code>--enable-lcms</code> for color management or <code>--enable-inkboard</code> for whiteboard functionality.
 
=== Building and Installing ===
 
Just run:
<pre>
make
make install
</pre>
 
 
===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.
[http://jo.irisson.free.fr/dropbox/inkscape/osxmake_fink.sh]
[http://jo.irisson.free.fr/dropbox/inkscape/osxmake_dp.sh]
 
To use this script, place it in the directory where Inkscape source code is and make it executable
<pre>chmod +x osxmake_???.sh</pre>
To obtain help on how to use it run it with the <code>-h</code> option:
<pre>./osxmake_???.sh -h</pre>
To run the whole process use the command:
<pre>./osxmake_???.sh -s -a -c -b -i -p</pre>
 
== Packaging Inkscape into an .app bundle ==
 
 
=== Creating the .app and a simple .dmg ===
 
Assuming that you have used the <code>--enable-osxapp</code> option during <code>configure</code>, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh -s /path/to/build/products/bin/inkscape ../Info.plist macosx
</pre>
The <code>-s</code> 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:
# download the source code from [http://sourceforge.net/project/showfiles.php?group_id=6473 sourceforge]
# unpack the <code>.tar.gz</code> file
# cd into the newly created directory
# set the variable <code>MACOSX_DEPLOYMENT_TARGET</code> 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:<pre>export MACOSX_DEPLOYMENT_TARGET=10.?</pre>
# move the python files and build C extensions<pre>python setup.py build</pre>
# install (the install is system wide so you need administrator rights)<pre>sudo python setup.py install</pre>and type your password.
 
== Links ==
 
=== Apple Documentation ===
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html 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 ===
 
* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html  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.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ 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 [http://gimp-app.sourceforge.net/gimp.app.howto.txt 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.
 
[[Category:Developer Documentation]]

Latest revision as of 17:53, 14 June 2025

The Inkscape Wiki is no longer used to host information about compiling Inkscape.

You can now find related information at GitLab.

This page is kept for historical reasons, e.g. to document specific decisions in Inkscape development.

Retrieved from "https://wiki.inkscape.org/wiki/index.php?title=CompilingMacOsX&oldid=123276"