Compiling Inkscape - Revision history

Mgmax: use correct "movedToOtherSite" template

2025-05-31T12:10:27Z

use correct "movedToOtherSite" template

← Older revision		Revision as of 12:10, 31 May 2025
Line 1:		Line 1:
	{{~~Outdated~~\|~~message~~=~~Developer documentation has been moved to [~~https://gitlab.com/inkscape/inkscape/-/blob/master/doc/building/readme.md GitLab].}}		{{MovedToOtherSite\|topic=compiling Inkscape\|new_url=https://gitlab.com/inkscape/inkscape/-/blob/master/doc/building/readme.md\|new_site=GitLab}}

Mgmax: Mark as outdated - moved to GitLab

2025-05-31T11:51:17Z

Mark as outdated - moved to GitLab

← Older revision		Revision as of 11:51, 31 May 2025
Line 1:		Line 1:
	<mark>Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for. </mark>		{{Outdated\|message=Developer documentation has been moved to [https://gitlab.com/inkscape/inkscape/-/blob/master/doc/building/readme.md GitLab].}}


	<mark> '''If you've come here without reading the Getting Started page, [https://inkscape.org/develop/getting-started/ please do so first], as it mentions some important things that this page does not.'''
	~~</mark>~~


	Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.

	~~If legitimate bugs are found or patches developed, please move them to the [https://inkscape.org/contribute/report-bugs/ tracker] rather than inlining them here.~~

	~~== Notes ==~~

	~~Please use CMake instead of Automake for Inkscape 0.92 onwards.~~

	~~CMake is a crossplatform makefile generator similar to autotools. It tests dependencies and creates makefiles to be used with make.~~

	~~Please see the [[CMake]] wiki page.~~

	~~== OS & Distribution Specific ==~~

	* '''Linux'''
	** [[CompilingUbuntu\|~~Ubuntu]]~~
	** [[CompilingSlackware\|Slackware]]
	* [[CompilingMacOsX\|Mac OS X]]
	* [[Compiling Inkscape on Windows\|Windows]]
	* [[Compiling Inkscape on Chrome OS\|Chrome OS]]
	* '''Cross-compiling'''
	** [[CrossCompilingOsX\|For OS X (from Linux)]]
	** [[CrossCompilingWindows\|For Windows (from Linux)]]

	=~~= Package Config (pkg-config) ==~~

	~~If you must compile and install any of these from source, you may find an error like this when trying~~ to
	~~compile them or Inkscape itself:~~
	~~<pre>~~
	~~checking for gtk+-2.0 >= 2.0.0 libxml-2.0 >= 2-2.4.24 sigc++-1.2 gtkmm-2.0... Package gtkmm-2.0 was not found in the pkg-config search path.~~
	~~Perhaps you should add the directory containing `gtkmm-2.0.pc'~~
	~~to the PKG_CONFIG_PATH environment variable~~
	~~No package 'gtkmm-2.0' found~~
	~~</pre>~~

	~~A solution is to set the PKG_CONFIG_PATH variable as so:~~
	* for Bash: <code>export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig</code>
	* for csh: <code>setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig</code>

	~~A good place to put this line is in your .bashrc or .cshrc file.~~

	~~== Dependencies ==~~

	If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download and build source packages and/or install them yourself. See [[Tracking Dependencies]].

	~~== Developer Compilation ==~~

	~~Plain vanilla compilation is done as documented in INSTALL.~~

	~~Now, you should use [~~[~~CMake]] to compile Inkscape:~~
	~~<pre>~~
	~~mkdir build~~
	~~cd build~~
	~~cmake ..~~
	~~make~~
	~~</pre>~~

	~~For old versions of inkscape before 0.92, you can still use autoconf:~~
	~~<pre>~~
	~~./autogen.sh # optionally~~
	~~./configure~~
	~~make~~
	~~</pre>~~

	~~Then, to run tests and install Inkscape, you may do:~~
	~~<pre>~~
	~~make check~~
	~~sudo make install \|\| su -c "make install"~~
	~~</pre>~~

	~~See INSTALL.md for more on that.~~

	~~But if you're going to be doing a lot of development, there's some tricks and techniques you should know, to get best results.~~

	~~# Turn off optimization.~~
	~~# Use ccache for faster compilation.~~
	~~# Set up a separate build directory (nice for testing both gcc and g++, or cross-compiling).~~
	~~# Use ninja or the make -j N flag to increment the number of threads available to make, with N = 1 + number of processors.~~

	~~Example: Setting up the build environment (in separate tree), and using ccache for faster~~
	~~compilations on a dual-processor machine, with no optimization and full debug symbols, assuming /bin/bash:~~
	~~<pre>~~
	~~mkdir build~~
	~~git clone --recurse-submodules~~ https://gitlab.com/inkscape/inkscape~~.git~~
	~~cd build~~
	~~cmake ..~~/~~inkscape~~ -~~DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DCMAKE_BUILD_TYPE=Debug -G Ninja~~
	~~ninja~~
	</~~pre>~~

	~~See [[Testing Inkscape]] for information on~~ building ~~and executing (unit) tests.~~

	~~=== Internal lib2geom ===~~
	~~If the version of Inkscape you are trying to build depends on recent lib2geom features, you'll need to add <code>-DWITH_INTERNAL_2GEOM=ON<~~/~~code> to the cmake command to use the development version of lib2geom rather than the system version~~.
	~~[[Category:Developer Documentation]~~]

PBS: add internal lib2geom instructions

2023-02-07T18:46:32Z

add internal lib2geom instructions

← Older revision		Revision as of 18:46, 7 February 2023
Line 97:		Line 97:
	See [[Testing Inkscape]] for information on building and executing (unit) tests.		See [[Testing Inkscape]] for information on building and executing (unit) tests.

			=== Internal lib2geom ===
			If the version of Inkscape you are trying to build depends on recent lib2geom features, you'll need to add <code>-DWITH_INTERNAL_2GEOM=ON</code> to the cmake command to use the development version of lib2geom rather than the system version.
	[[Category:Developer Documentation]]		[[Category:Developer Documentation]]

Mc: --recurse-submodules

2021-01-17T20:23:50Z

--recurse-submodules

← Older revision		Revision as of 20:23, 17 January 2021
Line 89:		Line 89:
	<pre>		<pre>
	mkdir build		mkdir build
	git clone https://gitlab.com/inkscape/inkscape.git		git clone --recurse-submodules https://gitlab.com/inkscape/inkscape.git
	cd build		cd build
	cmake ../inkscape -DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DCMAKE_BUILD_TYPE=Debug -G Ninja		cmake ../inkscape -DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DCMAKE_BUILD_TYPE=Debug -G Ninja

Mc at 07:57, 20 August 2020

2020-08-20T07:57:29Z

← Older revision		Revision as of 07:57, 20 August 2020
Line 1:		Line 1:
	Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for.		<mark>Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for. </mark>


			<mark> '''If you've come here without reading the Getting Started page, [https://inkscape.org/develop/getting-started/ please do so first], as it mentions some important things that this page does not.'''
			</mark>

	~~'''If you've come here without reading the Getting Started page, [https://inkscape.org/develop/getting-started/ please do so first], as it mentions some important things that this page does not.'''~~

	Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.		Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.
Line 73:		Line 76:
	</pre>		</pre>

	See INSTALL for more on that.		See INSTALL.md for more on that.

	But if you're going to be doing a lot of development, there's some tricks and techniques you should know, to get best results.		But if you're going to be doing a lot of development, there's some tricks and techniques you should know, to get best results.
Line 80:		Line 83:
	# Use ccache for faster compilation.		# Use ccache for faster compilation.
	# Set up a separate build directory (nice for testing both gcc and g++, or cross-compiling).		# Set up a separate build directory (nice for testing both gcc and g++, or cross-compiling).
	# Use the -j N flag to increment the number of threads available to make, with N = 1 + number of processors.		# Use ninja or the make -j N flag to increment the number of threads available to make, with N = 1 + number of processors.

	Example: Setting up the build environment (in separate tree), and using ccache for faster		Example: Setting up the build environment (in separate tree), and using ccache for faster
Line 86:		Line 89:
	<pre>		<pre>
	mkdir build		mkdir build
	~~bzr checkout lp~~:inkscape		git clone https://gitlab.com/inkscape/inkscape.git
	cd inkscape		cd build
	~~./autogen~~.sh		cmake ../inkscape -DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DCMAKE_BUILD_TYPE=Debug -G Ninja
	cd ~~../~~build		ninja
	~~export CFLAGS="-g -O0 -Wall" CC="ccache gcc"~~
	~~export CXXFLAGS="-g -O0 -Wall" CXX="ccache g++"~~
	../inkscape~~/configure~~
	~~make~~ -~~j 3 -k~~
	~~</pre>~~

	~~Turning off just optimization:~~
	~~<pre>~~
	~~export CXXFLAGS~~="-~~g -O0 -Wall"~~
	~~export CFLAGS~~="-~~g -O0 -Wall"~~
	~~./configure~~
	</pre>		</pre>

Moini at 14:03, 7 February 2020

2020-02-07T14:03:08Z

← Older revision		Revision as of 14:03, 7 February 2020
Line 1:		Line 1:
	Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for. '''If you've come here without reading the Getting Started page, please do so first, as it mentions some important things that this page does not.'''		Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for.

			'''If you've come here without reading the Getting Started page, [https://inkscape.org/develop/getting-started/ please do so first], as it mentions some important things that this page does not.'''

	Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.		Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.

Moini: Add more emphasis on Getting Started page.

2020-02-07T14:02:36Z

Add more emphasis on Getting Started page.

← Older revision		Revision as of 14:02, 7 February 2020
Line 1:		Line 1:
	Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for.		Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for. '''If you've come here without reading the Getting Started page, please do so first, as it mentions some important things that this page does not.'''

	Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.		Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.

Mgmax: cleanup outdated details

2019-05-28T15:00:09Z

cleanup outdated details

← Older revision		Revision as of 15:00, 28 May 2019
Line 1:		Line 1:
	Hopefully, Inkscape will compile right out of the box. If it doesn't, well that's what this page is for.		Hopefully, Inkscape will compile right out of the box, according to the 'Getting Started' instructions on https://inkscape.org/develop/getting-started/ . If it doesn't, well that's what this page is for.

	Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.		Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.

	If legitimate bugs are found or patches developed, please move them to the [https://bugs~~.launchpad.net~~/~~inkscape~~ tracker] rather than inlining them here.		If legitimate bugs are found or patches developed, please move them to the [https://inkscape.org/contribute/report-bugs/ tracker] rather than inlining them here.

	== Notes ==		== Notes ==

	~~Inkscape 0.91 and earlier needs automake 1.7, 1.8, 1.10 or higher. Please consider NOT using automake 1.9, because it has a bug that may prevent Inkscape from compiling.~~

	~~You may want to also [[Related programs#Inkscape Plugins, Scripts, and Templates\|add plugins]] during or after compiling.~~

	Please use CMake instead of Automake for Inkscape 0.92 onwards.		Please use CMake instead of Automake for Inkscape 0.92 onwards.

	~~== CMake Notes ==~~

	CMake is a crossplatform makefile generator similar to autotools. It tests dependencies and creates makefiles to be used with make.		CMake is a crossplatform makefile generator similar to autotools. It tests dependencies and creates makefiles to be used with make.

	~~Work is in progress to build Inkscape using CMake.~~ Please see the [[CMake]] wiki page.		Please see the [[CMake]] wiki page.

	== OS & Distribution Specific ==		== OS & Distribution Specific ==
Line 64:		Line 58:
	</pre>		</pre>

	~~But~~ you can still use autoconf:		For old versions of inkscape before 0.92, you can still use autoconf:
	<pre>		<pre>
	./autogen.sh # optionally		./autogen.sh # optionally

Mgmax: /* OS & Distribution Specific */ remove links to removed outdated wikipages

2019-05-28T14:53:26Z

OS & Distribution Specific: remove links to removed outdated wikipages

← Older revision		Revision as of 14:53, 28 May 2019
Line 27:		Line 27:
	* [[Compiling Inkscape on Windows\|Windows]]		* [[Compiling Inkscape on Windows\|Windows]]
	* [[Compiling Inkscape on Chrome OS\|Chrome OS]]		* [[Compiling Inkscape on Chrome OS\|Chrome OS]]
	* [[CompilingSPARC\|SPARC]]
	* [[CompilingSunSolaris\|Sun Solaris]]
	* [[CompilingStatic\|Static Compiles]]
	* '''Cross-compiling'''		* '''Cross-compiling'''
	** [[CrossCompilingOsX\|For OS X (from Linux)]]		** [[CrossCompilingOsX\|For OS X (from Linux)]]

Mgmax: /* OS & Distribution Specific */ remove links to removed outdated wikipaged

2019-05-28T14:49:37Z

OS & Distribution Specific: remove links to removed outdated wikipaged

← Older revision		Revision as of 14:49, 28 May 2019
Line 22:		Line 22:

	* '''Linux'''		* '''Linux'''
	** [[CompilingAutopackage\|Autopackage]] (multi-distro)
	** [[CompilingGentoo\|Gentoo]]
	** [[CompilingUbuntu\|Ubuntu]]		** [[CompilingUbuntu\|Ubuntu]]
	** [[CompilingSuse\|Suse]]
	** [[CompilingSlackware\|Slackware]]		** [[CompilingSlackware\|Slackware]]
	** [[CompilingYoper\|Yoper]]
	** [[CompilingMandrake\|Mandrakelinux]]
	** [[CompilingRHEL\|Red Hat Enterprise Linux Version #4]]
	* [[CompilingMacOsX\|Mac OS X]]		* [[CompilingMacOsX\|Mac OS X]]
	* [[Compiling Inkscape on Windows\|Windows]]		* [[Compiling Inkscape on Windows\|Windows]]

← Older revision		Revision as of 14:53, 28 May 2019
Line 27:		Line 27:
	* [[Compiling Inkscape on Windows\|Windows]]		* [[Compiling Inkscape on Windows\|Windows]]
	* [[Compiling Inkscape on Chrome OS\|Chrome OS]]		* [[Compiling Inkscape on Chrome OS\|Chrome OS]]
	* [[CompilingSPARC\|SPARC]]
	* [[CompilingSunSolaris\|Sun Solaris]]
	* [[CompilingStatic\|Static Compiles]]
	* '''Cross-compiling'''		* '''Cross-compiling'''
	** [[CrossCompilingOsX\|For OS X (from Linux)]]		** [[CrossCompilingOsX\|For OS X (from Linux)]]

← Older revision		Revision as of 14:49, 28 May 2019
Line 22:		Line 22:

	* '''Linux'''		* '''Linux'''
	** [[CompilingAutopackage\|Autopackage]] (multi-distro)
	** [[CompilingGentoo\|Gentoo]]
	** [[CompilingUbuntu\|Ubuntu]]		** [[CompilingUbuntu\|Ubuntu]]
	** [[CompilingSuse\|Suse]]
	** [[CompilingSlackware\|Slackware]]		** [[CompilingSlackware\|Slackware]]
	** [[CompilingYoper\|Yoper]]
	** [[CompilingMandrake\|Mandrakelinux]]
	** [[CompilingRHEL\|Red Hat Enterprise Linux Version #4]]
	* [[CompilingMacOsX\|Mac OS X]]		* [[CompilingMacOsX\|Mac OS X]]
	* [[Compiling Inkscape on Windows\|Windows]]		* [[Compiling Inkscape on Windows\|Windows]]