Compiling Inkscape on Windows 32-bit - Revision history

Patrick87: The information on this page is outdated. Please see '''Compiling Inkscape on Windows''' for the updated instructions.

2017-10-25T19:03:15Z

The information on this page is outdated. Please see '''Compiling Inkscape on Windows''' for the updated instructions.

← Older revision		Revision as of 19:03, 25 October 2017
Line 1:		Line 1:
	{{Note\|~~We're currently investigating to move to '''[http://www.msys2.org/ MSYS2]''' for building Inkscape~~ on ~~Windows~~. Please see '''[[Compiling Inkscape on Windows ~~with MSYS2~~]]''' for the updated instructions.		{{Note\|The information on this page is outdated. Please see '''[[Compiling Inkscape on Windows]]''' for the updated instructions.}}

	You're encouraged to test the new method and give feedback regarding any issues you might encounter. If no severe issues are found it's likely this will become the recommended method for building trunk in future and might also be considered for building the 0.92.x stable branch.}}

	'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''<br />		'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''<br />
	'''Warning: As our 32-bit development libraries (devlibs) currently do not offer GTK+ 3 (which is required by trunk) you have to follow the instructions for 64-bit builds or use MSYS2 if you want to compile the latest code (lp:inkscape)!'''

	----		----

Patrick87: Eduard moved page Compiling Inkscape on Windows to Compiling Inkscape on Windows 32-bit: move (outdated) instructions out of the way to make room for MSYS2 instructions

2017-10-25T18:55:15Z

Eduard moved page Compiling Inkscape on Windows to Compiling Inkscape on Windows 32-bit: move (outdated) instructions out of the way to make room for MSYS2 instructions

← Older revision	Revision as of 18:55, 25 October 2017
(No difference)

Patrick87: /* Compiling Inkscape using CMake */ Remove wrong information on "DESTDIR". It does not work with cmake-generated makefiles on Windows, e.g. see https://cmake.org/cmake/help/v3.0/variable/CMAKE_INSTALL_PREFIX.html

2017-05-09T19:06:18Z

Compiling Inkscape using CMake: Remove wrong information on "DESTDIR". It does not work with cmake-generated makefiles on Windows, e.g. see https://cmake.org/cmake/help/v3.0/variable/CMAKE_INSTALL_PREFIX.html

← Older revision		Revision as of 19:06, 9 May 2017
Line 129:		Line 129:
	''Note: The version of mingw32-make included in TDM GCC 4.6.1 (this is what you should be using when building 32-bit Inkscape) does not have jobserver support, yet. As CMake makes use of recursive make calls the <code>-j</code> option won't have any effect on the recursively spawned instances. You can work around this by executing <code>set MAKE=mingw32-make -j 2</code> before starting the compilation process (this will make each spawned instance use up to 2 jobs).''		''Note: The version of mingw32-make included in TDM GCC 4.6.1 (this is what you should be using when building 32-bit Inkscape) does not have jobserver support, yet. As CMake makes use of recursive make calls the <code>-j</code> option won't have any effect on the recursively spawned instances. You can work around this by executing <code>set MAKE=mingw32-make -j 2</code> before starting the compilation process (this will make each spawned instance use up to 2 jobs).''

	Collect all the needed files and create a selfcontaing directory:		Collect all the needed files and create a selfcontaing directory in <code>./build/inkscape/</code>:

	<pre>		<pre>
	mingw32-make ~~DESTDIR=mydir~~ install		mingw32-make install
	</pre>		</pre>

	See [http://stackoverflow.com/questions/11307465/destdir-and-prefix-of-make this article] in stackoverflow about the difference in DESTDIR and PREFIX of make. After this step we have a mydir/Program Files/inkscape/ where everything ''should'' be. ''(Note: Using relative paths with <code>DESTDIR</code> is currently broken. Usually you can just omit the command to simply install into <code>./build/inkscape/</code>)''

	As cmake hides the actual compiler calls, here is a way how to see what make is doing.		As cmake hides the actual compiler calls, here is a way how to see what make is doing.

Mc at 21:43, 6 May 2017

2017-05-06T21:43:43Z

← Older revision		Revision as of 21:43, 6 May 2017
Line 261:		Line 261:

	Step-by-step instructions can be found in the file [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/packaging/wix/README <code>…\packaging\wix\README</code>].		Step-by-step instructions can be found in the file [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/packaging/wix/README <code>…\packaging\wix\README</code>].


			=== Windows store (*.appx) ===

			In order to upload the installer on [https://www.microsoft.com/fr-fr/store/p/inkscape/9pd9bhglfc7h the windows store], you need to use the [https://www.microsoft.com/fr-fr/store/p/desktop-app-converter/9nblggh4skzw desktop app converter] to create a .appx from the msi installer. The correct commandline is :

			C:\src\inkscape\trunk> desktopAppConverter -Installer Inkscape-0.92.1-x64.msi -Destination C:/Users/Inkscape/SomeFolder/ -PackageName 25415Inkscape.Inkscape -Publisher CN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -Version 0.92.1.0 -MakeAppx -AppDisplayName Inkscape -PackagePublisherDisplayName Inkscape -PackageDisplayName Inkscape -AppID Inkscape

			The correct CN name can be found on the [https://developer.microsoft.com/en-us/dashboard/apps/overview windows developer admin panel] where you upload the package.

	== Note about Unicode ==		== Note about Unicode ==

Patrick87 at 13:42, 1 April 2017

2017-04-01T13:42:13Z

← Older revision		Revision as of 13:42, 1 April 2017
Line 4:		Line 4:

	'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''<br />		'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''<br />
	'''Warning: As our 32-bit development libraries (devlibs) currently do not offer GTK+ 3 (which is required by trunk) you have to follow the instructions for 64-bit builds or use MSYS2!'''		'''Warning: As our 32-bit development libraries (devlibs) currently do not offer GTK+ 3 (which is required by trunk) you have to follow the instructions for 64-bit builds or use MSYS2 if you want to compile the latest code (lp:inkscape)!'''

	----		----

Patrick87 at 13:40, 1 April 2017

2017-04-01T13:40:42Z

← Older revision		Revision as of 13:40, 1 April 2017
Line 3:		Line 3:
	You're encouraged to test the new method and give feedback regarding any issues you might encounter. If no severe issues are found it's likely this will become the recommended method for building trunk in future and might also be considered for building the 0.92.x stable branch.}}		You're encouraged to test the new method and give feedback regarding any issues you might encounter. If no severe issues are found it's likely this will become the recommended method for building trunk in future and might also be considered for building the 0.92.x stable branch.}}

	'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''		'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''<br />
	'''Warning: As our 32-bit development libraries (devlibs) currently do not offer GTK+ 3 (which is required by trunk) you have to follow the instructions for 64-bit builds or use MSYS2!'''		'''Warning: As our 32-bit development libraries (devlibs) currently do not offer GTK+ 3 (which is required by trunk) you have to follow the instructions for 64-bit builds or use MSYS2!'''

Patrick87: Add note about lacking support for gtk3 in devlibs

2017-04-01T13:40:01Z

Add note about lacking support for gtk3 in devlibs

← Older revision		Revision as of 13:40, 1 April 2017
Line 4:		Line 4:

	'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''		'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''
			'''Warning: As our 32-bit development libraries (devlibs) currently do not offer GTK+ 3 (which is required by trunk) you have to follow the instructions for 64-bit builds or use MSYS2!'''

	----		----

Patrick87: Add note regarding MSYS2

2017-03-25T22:56:43Z

Add note regarding MSYS2

← Older revision		Revision as of 22:56, 25 March 2017
Line 1:		Line 1:
			{{Note\|We're currently investigating to move to '''[http://www.msys2.org/ MSYS2]''' for building Inkscape on Windows. Please see '''[[Compiling Inkscape on Windows with MSYS2]]''' for the updated instructions.

			You're encouraged to test the new method and give feedback regarding any issues you might encounter. If no severe issues are found it's likely this will become the recommended method for building trunk in future and might also be considered for building the 0.92.x stable branch.}}

	'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''		'''For 64 bit: see [[Compiling Inkscape on Windows 64-bit]]'''

Patrick87: /* Compiling Inkscape using CMake */

2017-02-14T20:38:50Z

Compiling Inkscape using CMake

← Older revision		Revision as of 20:38, 14 February 2017
Line 99:		Line 99:
	=== Compiling Inkscape using CMake ===		=== Compiling Inkscape using CMake ===

	''Note: To significantly ~~reduced~~ the time needed for incremental rebuilds consider [[CMake#Using CMake with Ninja to build Inkscape\|using CMake in combination with Ninja]].''		''Note: To significantly reduce the time needed for incremental rebuilds consider [[CMake#Using CMake with Ninja to build Inkscape\|using CMake in combination with Ninja]].''

	Go to the directory containing your Inkscape source and create the build output directory. In example:		Go to the directory containing your Inkscape source and create the build output directory. In example:

Patrick87: /* Compiling Inkscape using CMake */ add note about Ninja

2017-02-14T20:38:35Z

Compiling Inkscape using CMake: add note about Ninja

← Older revision		Revision as of 20:38, 14 February 2017
Line 98:		Line 98:

	=== Compiling Inkscape using CMake ===		=== Compiling Inkscape using CMake ===

			''Note: To significantly reduced the time needed for incremental rebuilds consider [[CMake#Using CMake with Ninja to build Inkscape\|using CMake in combination with Ninja]].''

	Go to the directory containing your Inkscape source and create the build output directory. In example:		Go to the directory containing your Inkscape source and create the build output directory. In example: