Inkscape Wiki - User contributions [en]

CMake

2016-04-24T15:44:15Z

TheAdib: /* Configuring your build further */

'''Work is a on going to get this build system functional!'''

Cmake is a cross-platform build system know to work on all major platforms we support (*nix, Windows, OSX).

CMake is an extensible, open-source system that has many powerful features.
Those features include:

* Supports complex, large build environments. CMake has been proven in several large projects (KDE, ParaView, SecondLife, Scribus)
* Generates native build files (e.g., makefiles on Unix; workspaces/projects on MS Visual C++). Therefore, standard tools can be used on any platform/compiler configuration.
* Powerful system introspection abilities including the ability to find installed include files, libraries and executables. Also the ability to test the compiler for supported features.
* Integrated testing system called CTest.
* Integrated packaging system called CPack.
* Easy integration with CDash and Dart dashboard servers.
* Powerful scripting language with simple syntax.
* Supports in-place and out-of-place builds. Multiple compilation trees are possible from a single source tree.
* Can be easily extended to add new features.
* CMake is open source, under a liberal BSD license.
* CMake operates with a cache designed to be interfaced with a graphical editor. The cache provides optional interaction to conditionally control the build process.
* Ability to create Mac OSX Frameworks and Application Bundles.
* Supports adding complex custom rules to the build.

== How you can help ==

We have completed the building of the CMakeLists.txt for almost everything needed.
We are now working on get the build to compile properly. See below Testing/Using to help.

There is a separate [[CMake Tasks]] page with things that are left to do w.r.t. cmake building of Inkscape.

== SIMPLE CmakeLists.txt ==
SET(libavoid_SRC
connector.cpp
geometry.cpp
graph.cpp
makepath.cpp
polyutil.cpp
region.cpp
router.cpp
shape.cpp
static.cpp
timer.cpp
vertices.cpp
visibility.cpp
)

== SIMPLE with single sub-directory Cmakelists.txt ==

SET(libavoid_SRC
connector.cpp
geometry.cpp
graph.cpp
makepath.cpp
polyutil.cpp
region.cpp
router.cpp
shape.cpp
static.cpp
timer.cpp
vertices.cpp
visibility.cpp
#Add our subdirectory sourcelist Var
${libavoid_parameter_SRC}
)
# this adds a single sub-directory
ADD_SUBDIRECTORY(parameter)

== Using CMake to build Inkscape ==

Experience with Scribus '''strongly''' suggests using an "out of source"build arrangement. E.g.

<pre>
mkdir buildinkscape
cd buildinkscape
cmake ./path/to/inkscape/sources
make
</pre>

References:
[http://docs.scribus.net/index.php?lang=en&page=install4 Installing Scribus with Cmake] 
[http://docs.scribus.net/index.php?lang=en&page=install5 Installing with CMake on OSX]

== Using CMake to run tests ==

First, install Google Test framework by running download-gtest.sh in the main directory of inkscape source:

<pre>
cd /path/to/inkscape
bash download-gtest.sh
</pre>

Then, toggle the CMake config var "WITH_GTEST" to ON, e.g. by editing CMakeCache.txt, or by passing "-DWITH_GTEST=ON" to cmake. Don't forget to re-run cmake after the configuration change:

<pre>
cd /path/to/buildinkscape
# modify CMakeCache.txt
cmake ../inkscape
</pre>

Finally, run "make check" from same directory to run the tests:

<pre>
make check
</pre>

== Configuring your build further ==

It is possible to change some more options of the build, e.g. whether to compile against GTK2 or GTK3 libraries. If you fiddle a lot with this, you may want to install the interactive cmake configuration tool "ccmake", like so:

<pre>
sudo apt-get install cmake-curses-gui
ccmake ../inkscape # In buildinkscape folder
</pre>

The ccmake utility will have features to re-run cmake for you before exiting.

=== adding options to cmake ===

you can specify some variable on cmake invokation. i.e.

<pre>
cmake .. -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Debug
</pre>

Useful CMake configuration variables include

* CMAKE_BUILD_TYPE: Either Release or Debug (a string).
* WITH_GTK3_EXPERIMENTAL: ON/OFF. Toggle between GTK2 or GTK3 ui toolkit.
* CMAKE_INSTALL_PREFIX: Path in which "make install" installs Inkscape.

Compiling Inkscape

2016-04-20T20:36:55Z

TheAdib: /* CMake Notes */

Hopefully, Inkscape will compile right out of the box. 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.

If legitimate bugs are found or patches developed, please move them to the tracker at Sourceforge
rather than inlining them here.

= Notes =
Inkscape needs automake 1.7, 1.8 or 1.10 and higher. Please consider NOT using automake1.9, because it has a bug ( link: http://sourceforge.net/mailarchive/message.php?msg_id=10288631 ) that prevents compiling of Inkscape. If you have already tried to do a $ make with automake1.9 then $ ./autogen.sh from your inkscape-cvs dir and proceed as normal. (On the other hand, I've repeatedly built it with automake-1.9.4. ralf)

You may want to also [http://wiki.inkscape.org/wiki/index.php/OtherProjects#Inkscape_Plugins.2C_Scripts.2C_and_Templates add plugins] during or after compiling.

= CMake Notes =

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. For windows developers some notes are on the [[Compiling Inkscape on Windows 64-bit]] page.

= OS & Distribution Specific =
* '''Linux'''
** [[CompilingAutopackage|Autopackage]] (multi-distro)
** [[CompilingFedora|Fedora]]
** [[CompilingGentoo|Gentoo]]
** [[CompilingDebian|Debian]]
** [[CompilingUbuntu|Ubuntu]]
** [[CompilingYellowDog|Yellow Dog]]
** [[CompilingSuse|Suse]]
** [[CompilingSlackware|Slackware]]
** [[CompilingYoper|Yoper]]
** [[CompilingMandrake|Mandrakelinux]]
** [[CompilingRHEL|Red Hat Enterprise Linux Version #4]]
* [[CompilingMacOsX|Mac OS X]]
* [[Compiling Inkscape on Windows|Windows]]
* [[CompilingSPARC|SPARC]]
* [[CompilingSunSolaris|Sun Solaris]]
* [[CompilingStatic|Static Compiles]]
* '''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:

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

A solution is to set the PKG_CONFIG_PATH variable as so:

for bash:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
for csh:
setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig

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; ./autogen.sh (optionally); ./configure; make; su && make check; make install (optional). See INSTALL 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 the -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:

mkdir build
bzr checkout lp:inkscape
cd inkscape
./autogen.sh
cd ../build
export CFLAGS="-g -O0 -Wall" CC="ccache gcc"
export CXXFLAGS="-g -O0 -Wall" CXX="ccache g++"
../inkscape/configure
make -j 3 -k

Turning off just optimization:

export CXXFLAGS="-g -O0 -Wall"
export CFLAGS="-g -O0 -Wall"
./configure

See [[TestingInkscape]] for information on building and executing (unit) tests.

[[Category:Developer Documentation]]

Compiling Inkscape

2016-04-20T20:34:29Z

TheAdib: add cmake naotes

Hopefully, Inkscape will compile right out of the box. 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.

If legitimate bugs are found or patches developed, please move them to the tracker at Sourceforge
rather than inlining them here.

= Notes =
Inkscape needs automake 1.7, 1.8 or 1.10 and higher. Please consider NOT using automake1.9, because it has a bug ( link: http://sourceforge.net/mailarchive/message.php?msg_id=10288631 ) that prevents compiling of Inkscape. If you have already tried to do a $ make with automake1.9 then $ ./autogen.sh from your inkscape-cvs dir and proceed as normal. (On the other hand, I've repeatedly built it with automake-1.9.4. ralf)

You may want to also [http://wiki.inkscape.org/wiki/index.php/OtherProjects#Inkscape_Plugins.2C_Scripts.2C_and_Templates add plugins] during or after compiling.

= CMake Notes =

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.

= OS & Distribution Specific =
* '''Linux'''
** [[CompilingAutopackage|Autopackage]] (multi-distro)
** [[CompilingFedora|Fedora]]
** [[CompilingGentoo|Gentoo]]
** [[CompilingDebian|Debian]]
** [[CompilingUbuntu|Ubuntu]]
** [[CompilingYellowDog|Yellow Dog]]
** [[CompilingSuse|Suse]]
** [[CompilingSlackware|Slackware]]
** [[CompilingYoper|Yoper]]
** [[CompilingMandrake|Mandrakelinux]]
** [[CompilingRHEL|Red Hat Enterprise Linux Version #4]]
* [[CompilingMacOsX|Mac OS X]]
* [[Compiling Inkscape on Windows|Windows]]
* [[CompilingSPARC|SPARC]]
* [[CompilingSunSolaris|Sun Solaris]]
* [[CompilingStatic|Static Compiles]]
* '''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:

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

A solution is to set the PKG_CONFIG_PATH variable as so:

for bash:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
for csh:
setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig

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; ./autogen.sh (optionally); ./configure; make; su && make check; make install (optional). See INSTALL 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 the -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:

mkdir build
bzr checkout lp:inkscape
cd inkscape
./autogen.sh
cd ../build
export CFLAGS="-g -O0 -Wall" CC="ccache gcc"
export CXXFLAGS="-g -O0 -Wall" CXX="ccache g++"
../inkscape/configure
make -j 3 -k

Turning off just optimization:

export CXXFLAGS="-g -O0 -Wall"
export CFLAGS="-g -O0 -Wall"
./configure

See [[TestingInkscape]] for information on building and executing (unit) tests.

[[Category:Developer Documentation]]

Compiling Inkscape on Windows 64-bit

2016-04-18T12:15:39Z

TheAdib: /* Compiling Inkscape using CMake */

'''For 32 bit: see [[Compiling Inkscape on Windows]]'''

----

Compiling Inkscape on Windows 64-bit works similar to [[Compiling Inkscape on Windows|compiling Inkscape on Windows 32-bit]] where you can find additional information.

This page only describes the basic steps that are required while highlighting the differences compared to a 32-bit build.

== Requirements ==
=== MinGW-w64 ===

Get [http://mingw-w64.org/ MinGW-w64] which contains the necessary GNU developer tools to build Inkscape on Windows.

You have to download a version that is configured for building native win64 applications with ''win32 threading model'' and ''SEH exception handling'', to ensure compatibility with the inkscape-devlibs64.

A matching build based on GCC 5.3 can be downloaded [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/ here]. The exact version used for building the inkscape-devlibs64 is [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z/download MinGW-w64 x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z].

=== CMake ===

CMake is a Cross-Platform buildsystem generator similar to autotools. It generates '''makefiles''' to be processed by '''make'''.
Get CMake from the [https://cmake.org/ official website cmake.org]. As of writing [https://cmake.org/files/v3.5/cmake-3.5.2-win32-x86.msi version 3.5.2] is the most recent version.

=== Inkscape development libraries for Windows 64-bit ===

Get the [https://code.launchpad.net/inkscape-devlibs64 inkscape-devlibs64] which include pre-compiled binaries of all Inkscape dependencies.

To checkout via Bazaar use the command
<pre>bzr checkout --lightweight lp:inkscape-devlibs64 C:\devlibs64</pre>
The <code>--lightweight</code> switch ensures that you only have to download the latest version of all binaries, <code>C:\devlibs64</code> is the folder you want them to be downloaded to.

See also [[Inkscape Devlibs 64-bit]] ''(only relevant if you want to update the development libraries)''

=== Inkscape source code ===

Get the [https://launchpad.net/inkscape Inkscape source code] from launchpad

To checkout via Bazaar use the command
<pre>bzr checkout lp:inkscape C:\inkscape</pre>

See also additional information on [[Compiling_Inkscape_on_Windows#Obtaining_Inkscape_source_code|obtaining Inkscape source code]] and [[Working with Bazaar|working with Bazaar]].

== Building ==

=== Environment variables ===

Edit the file <code>mingwenv.bat</code> in the root directory of the Inkscape source to match you local paths. Most importantly the two lines
<pre>
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64
</pre>
should point to the folders containing MinGW-w64 and the inkscape-devlibs64.

Whenever you want to build Inkscape open a command prompt (<code>cmd.exe</code>), change into the root directory of the Inkscape source and execute <code>mingwenv.bat</code> to set environment variables.

=== Compiling build tool ===

Compile <code>btool</code> (the command line tool that handles the actual build) using
<pre>g++ buildtool.cpp -o btool -fopenmp</pre>

=== Compiling Inkscape ===

Use <code>btool</code> to compile Inkscape compile and create the distribution directory:
<pre>btool -file build-x64.xml -j 2</pre>
The file <code>build-x64.xml</code> contains the necessary instructions for creating a standard 64-bit build. 
If you want to make a GTK+ 3 build use <code>build-x64-gtk3.xml</code> instead (please note that GTK+ 3 builds are experimental and not ready for production yet).

The <code>-j</code> switch allows to instruct btool to use multiple parallel threads to speed up compilation (e.g. 2 in the example above).

=== Compiling Inkscape using CMake ===

Go to source code directory.

Create the output directory, where the intermediate output goes to.
<pre>
mkdir build
cd build
</pre>

Create the makefiles using CMake.
<pre>cmake .. -G "MinGW Makefiles"</pre>

Start the build proccess. The INkscape.exe will be in build/bin directory afterwards.
<pre>mingw32-make -j 2</pre>

Collect all the needed files and create a selfcontaing directory. ''This currently does not work as with btool.''
<pre>mingw32-make DESTDIR=mydir install</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.

As cmake hides the actual compiler calls, here is a way how to see what make is doing.
<pre>mingw32-make -j 2 VERBOSE=1</pre>

Compiling Inkscape on Windows 64-bit

2016-04-18T12:07:42Z

TheAdib: /* Compiling Inkscape using CMake */

'''For 32 bit: see [[Compiling Inkscape on Windows]]'''

----

Compiling Inkscape on Windows 64-bit works similar to [[Compiling Inkscape on Windows|compiling Inkscape on Windows 32-bit]] where you can find additional information.

This page only describes the basic steps that are required while highlighting the differences compared to a 32-bit build.

== Requirements ==
=== MinGW-w64 ===

Get [http://mingw-w64.org/ MinGW-w64] which contains the necessary GNU developer tools to build Inkscape on Windows.

You have to download a version that is configured for building native win64 applications with ''win32 threading model'' and ''SEH exception handling'', to ensure compatibility with the inkscape-devlibs64.

A matching build based on GCC 5.3 can be downloaded [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/ here]. The exact version used for building the inkscape-devlibs64 is [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z/download MinGW-w64 x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z].

=== CMake ===

CMake is a Cross-Platform buildsystem generator similar to autotools. It generates '''makefiles''' to be processed by '''make'''.
Get CMake from the [https://cmake.org/ official website cmake.org]. As of writing [https://cmake.org/files/v3.5/cmake-3.5.2-win32-x86.msi version 3.5.2] is the most recent version.

=== Inkscape development libraries for Windows 64-bit ===

Get the [https://code.launchpad.net/inkscape-devlibs64 inkscape-devlibs64] which include pre-compiled binaries of all Inkscape dependencies.

To checkout via Bazaar use the command
<pre>bzr checkout --lightweight lp:inkscape-devlibs64 C:\devlibs64</pre>
The <code>--lightweight</code> switch ensures that you only have to download the latest version of all binaries, <code>C:\devlibs64</code> is the folder you want them to be downloaded to.

See also [[Inkscape Devlibs 64-bit]] ''(only relevant if you want to update the development libraries)''

=== Inkscape source code ===

Get the [https://launchpad.net/inkscape Inkscape source code] from launchpad

To checkout via Bazaar use the command
<pre>bzr checkout lp:inkscape C:\inkscape</pre>

See also additional information on [[Compiling_Inkscape_on_Windows#Obtaining_Inkscape_source_code|obtaining Inkscape source code]] and [[Working with Bazaar|working with Bazaar]].

== Building ==

=== Environment variables ===

Edit the file <code>mingwenv.bat</code> in the root directory of the Inkscape source to match you local paths. Most importantly the two lines
<pre>
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64
</pre>
should point to the folders containing MinGW-w64 and the inkscape-devlibs64.

Whenever you want to build Inkscape open a command prompt (<code>cmd.exe</code>), change into the root directory of the Inkscape source and execute <code>mingwenv.bat</code> to set environment variables.

=== Compiling build tool ===

Compile <code>btool</code> (the command line tool that handles the actual build) using
<pre>g++ buildtool.cpp -o btool -fopenmp</pre>

=== Compiling Inkscape ===

Use <code>btool</code> to compile Inkscape compile and create the distribution directory:
<pre>btool -file build-x64.xml -j 2</pre>
The file <code>build-x64.xml</code> contains the necessary instructions for creating a standard 64-bit build. 
If you want to make a GTK+ 3 build use <code>build-x64-gtk3.xml</code> instead (please note that GTK+ 3 builds are experimental and not ready for production yet).

The <code>-j</code> switch allows to instruct btool to use multiple parallel threads to speed up compilation (e.g. 2 in the example above).

=== Compiling Inkscape using CMake ===

Go to source code directory.

Create the output directory, where the intermediate output goes to.
<pre>
mkdir build
cd build
</pre>

Create the makefiles using CMake.
<pre>cmake .. -G "MinGW Makefiles"</pre>

Start the build proccess. The INkscape.exe will be in build/bin directory afterwards.
<pre>mingw32-make -j 2</pre>

Collect all the needed files and create a selfcontaing directory. ''This currently does not work as with btool.''
<pre>mingw32-make DISTDIR=mydir install</pre>
See [http://stackoverflow.com/questions/11307465/destdir-and-prefix-of-make this article] in stackoverflow about the difference in DISTDIR and PREFIX of make.

As cmake hides the actual compiler calls, here is a way how to see what make is doing.
<pre>mingw32-make -j 2 VERBOSE=1</pre>

Compiling Inkscape on Windows 64-bit

2016-04-18T12:02:28Z

TheAdib: /* Compiling Inkscape using CMake */

'''For 32 bit: see [[Compiling Inkscape on Windows]]'''

----

Compiling Inkscape on Windows 64-bit works similar to [[Compiling Inkscape on Windows|compiling Inkscape on Windows 32-bit]] where you can find additional information.

This page only describes the basic steps that are required while highlighting the differences compared to a 32-bit build.

== Requirements ==
=== MinGW-w64 ===

Get [http://mingw-w64.org/ MinGW-w64] which contains the necessary GNU developer tools to build Inkscape on Windows.

You have to download a version that is configured for building native win64 applications with ''win32 threading model'' and ''SEH exception handling'', to ensure compatibility with the inkscape-devlibs64.

A matching build based on GCC 5.3 can be downloaded [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/ here]. The exact version used for building the inkscape-devlibs64 is [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z/download MinGW-w64 x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z].

=== CMake ===

CMake is a Cross-Platform buildsystem generator similar to autotools. It generates '''makefiles''' to be processed by '''make'''.
Get CMake from the [https://cmake.org/ official website cmake.org]. As of writing [https://cmake.org/files/v3.5/cmake-3.5.2-win32-x86.msi version 3.5.2] is the most recent version.

=== Inkscape development libraries for Windows 64-bit ===

Get the [https://code.launchpad.net/inkscape-devlibs64 inkscape-devlibs64] which include pre-compiled binaries of all Inkscape dependencies.

To checkout via Bazaar use the command
<pre>bzr checkout --lightweight lp:inkscape-devlibs64 C:\devlibs64</pre>
The <code>--lightweight</code> switch ensures that you only have to download the latest version of all binaries, <code>C:\devlibs64</code> is the folder you want them to be downloaded to.

See also [[Inkscape Devlibs 64-bit]] ''(only relevant if you want to update the development libraries)''

=== Inkscape source code ===

Get the [https://launchpad.net/inkscape Inkscape source code] from launchpad

To checkout via Bazaar use the command
<pre>bzr checkout lp:inkscape C:\inkscape</pre>

See also additional information on [[Compiling_Inkscape_on_Windows#Obtaining_Inkscape_source_code|obtaining Inkscape source code]] and [[Working with Bazaar|working with Bazaar]].

== Building ==

=== Environment variables ===

Edit the file <code>mingwenv.bat</code> in the root directory of the Inkscape source to match you local paths. Most importantly the two lines
<pre>
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64
</pre>
should point to the folders containing MinGW-w64 and the inkscape-devlibs64.

Whenever you want to build Inkscape open a command prompt (<code>cmd.exe</code>), change into the root directory of the Inkscape source and execute <code>mingwenv.bat</code> to set environment variables.

=== Compiling build tool ===

Compile <code>btool</code> (the command line tool that handles the actual build) using
<pre>g++ buildtool.cpp -o btool -fopenmp</pre>

=== Compiling Inkscape ===

Use <code>btool</code> to compile Inkscape compile and create the distribution directory:
<pre>btool -file build-x64.xml -j 2</pre>
The file <code>build-x64.xml</code> contains the necessary instructions for creating a standard 64-bit build. 
If you want to make a GTK+ 3 build use <code>build-x64-gtk3.xml</code> instead (please note that GTK+ 3 builds are experimental and not ready for production yet).

The <code>-j</code> switch allows to instruct btool to use multiple parallel threads to speed up compilation (e.g. 2 in the example above).

=== Compiling Inkscape using CMake ===

Go to source code directory.

Create the output directory, where the intermediate output goes to.
<pre>
mkdir build
cd build
</pre>

Create the makefiles using CMake.
<pre>cmake .. -G "MinGW Makefiles"</pre>

Start the build proccess. The INkscape.exe will be in build/bin directory afterwards.
<pre>mingw32-make -j 2</pre>

Collect all the needed files and create a selfcontaing directory. ''This currently does not work as with btool.''
<pre>mingw32-make DISTDIR=mydir install</pre>
See [http://stackoverflow.com/questions/11307465/destdir-and-prefix-of-make this article] in stackoverflow about the difference in DISTDIR and PREFIX of make.

Compiling Inkscape on Windows 64-bit

2016-04-17T16:00:19Z

TheAdib: /* Compiling Inkscape using CMake */

Compiling Inkscape on Windows 64-bit

2016-04-17T15:42:27Z

TheAdib: /* Compiling Inkscape using CMake */

'''For 32 bit: see [[Compiling Inkscape on Windows]]'''

----

Compiling Inkscape on Windows 64-bit works similar to [[Compiling Inkscape on Windows|compiling Inkscape on Windows 32-bit]] where you can find additional information.

This page only describes the basic steps that are required while highlighting the differences compared to a 32-bit build.

== Requirements ==
=== MinGW-w64 ===

Get [http://mingw-w64.org/ MinGW-w64] which contains the necessary GNU developer tools to build Inkscape on Windows.

You have to download a version that is configured for building native win64 applications with ''win32 threading model'' and ''SEH exception handling'', to ensure compatibility with the inkscape-devlibs64.

A matching build based on GCC 5.3 can be downloaded [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/ here]. The exact version used for building the inkscape-devlibs64 is [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z/download MinGW-w64 x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z].

=== CMake ===

CMake is a Cross-Platform buildsystem generator similar to autotools. It generates '''makefiles''' to be processed by '''make'''.
Get CMake from the [https://cmake.org/ official website cmake.org]. As of writing [https://cmake.org/files/v3.5/cmake-3.5.2-win32-x86.msi version 3.5.2] is the most recent version.

=== Inkscape development libraries for Windows 64-bit ===

Get the [https://code.launchpad.net/inkscape-devlibs64 inkscape-devlibs64] which include pre-compiled binaries of all Inkscape dependencies.

To checkout via Bazaar use the command
<pre>bzr checkout --lightweight lp:inkscape-devlibs64 C:\devlibs64</pre>
The <code>--lightweight</code> switch ensures that you only have to download the latest version of all binaries, <code>C:\devlibs64</code> is the folder you want them to be downloaded to.

See also [[Inkscape Devlibs 64-bit]] ''(only relevant if you want to update the development libraries)''

=== Inkscape source code ===

Get the [https://launchpad.net/inkscape Inkscape source code] from launchpad

To checkout via Bazaar use the command
<pre>bzr checkout lp:inkscape C:\inkscape</pre>

See also additional information on [[Compiling_Inkscape_on_Windows#Obtaining_Inkscape_source_code|obtaining Inkscape source code]] and [[Working with Bazaar|working with Bazaar]].

== Building ==

=== Environment variables ===

Edit the file <code>mingwenv.bat</code> in the root directory of the Inkscape source to match you local paths. Most importantly the two lines
<pre>
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64
</pre>
should point to the folders containing MinGW-w64 and the inkscape-devlibs64.

Whenever you want to build Inkscape open a command prompt (<code>cmd.exe</code>), change into the root directory of the Inkscape source and execute <code>mingwenv.bat</code> to set environment variables.

=== Compiling build tool ===

Compile <code>btool</code> (the command line tool that handles the actual build) using
<pre>g++ buildtool.cpp -o btool -fopenmp</pre>

=== Compiling Inkscape ===

Use <code>btool</code> to compile Inkscape compile and create the distribution directory:
<pre>btool -file build-x64.xml -j 2</pre>
The file <code>build-x64.xml</code> contains the necessary instructions for creating a standard 64-bit build. 
If you want to make a GTK+ 3 build use <code>build-x64-gtk3.xml</code> instead (please note that GTK+ 3 builds are experimental and not ready for production yet).

The <code>-j</code> switch allows to instruct btool to use multiple parallel threads to speed up compilation (e.g. 2 in the example above).

=== Compiling Inkscape using CMake ===

Go to source code directory.

Create the output directory, where the intermediate output goes to.
<pre>
mkdir build
cd build
</pre>

Create the makefiles using CMake.
<pre>cmake .. -G "MinGW Makefiles</pre>

Start the build proccess.
<pre>mingw32-make -j</pre>

Compiling Inkscape on Windows 64-bit

2016-04-17T15:32:59Z

TheAdib: /* Compiling Inkscape using CMake */

'''For 32 bit: see [[Compiling Inkscape on Windows]]'''

----

Compiling Inkscape on Windows 64-bit works similar to [[Compiling Inkscape on Windows|compiling Inkscape on Windows 32-bit]] where you can find additional information.

This page only describes the basic steps that are required while highlighting the differences compared to a 32-bit build.

== Requirements ==
=== MinGW-w64 ===

Get [http://mingw-w64.org/ MinGW-w64] which contains the necessary GNU developer tools to build Inkscape on Windows.

You have to download a version that is configured for building native win64 applications with ''win32 threading model'' and ''SEH exception handling'', to ensure compatibility with the inkscape-devlibs64.

A matching build based on GCC 5.3 can be downloaded [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/ here]. The exact version used for building the inkscape-devlibs64 is [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z/download MinGW-w64 x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z].

=== CMake ===

CMake is a Cross-Platform buildsystem generator similar to autotools. It generates '''makefiles''' to be processed by '''make'''.
Get CMake from the [https://cmake.org/ official website cmake.org]. As of writing [https://cmake.org/files/v3.5/cmake-3.5.2-win32-x86.msi version 3.5.2] is the most recent version.

=== Inkscape development libraries for Windows 64-bit ===

Get the [https://code.launchpad.net/inkscape-devlibs64 inkscape-devlibs64] which include pre-compiled binaries of all Inkscape dependencies.

To checkout via Bazaar use the command
<pre>bzr checkout --lightweight lp:inkscape-devlibs64 C:\devlibs64</pre>
The <code>--lightweight</code> switch ensures that you only have to download the latest version of all binaries, <code>C:\devlibs64</code> is the folder you want them to be downloaded to.

See also [[Inkscape Devlibs 64-bit]] ''(only relevant if you want to update the development libraries)''

=== Inkscape source code ===

Get the [https://launchpad.net/inkscape Inkscape source code] from launchpad

To checkout via Bazaar use the command
<pre>bzr checkout lp:inkscape C:\inkscape</pre>

See also additional information on [[Compiling_Inkscape_on_Windows#Obtaining_Inkscape_source_code|obtaining Inkscape source code]] and [[Working with Bazaar|working with Bazaar]].

== Building ==

=== Environment variables ===

Edit the file <code>mingwenv.bat</code> in the root directory of the Inkscape source to match you local paths. Most importantly the two lines
<pre>
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64
</pre>
should point to the folders containing MinGW-w64 and the inkscape-devlibs64.

Whenever you want to build Inkscape open a command prompt (<code>cmd.exe</code>), change into the root directory of the Inkscape source and execute <code>mingwenv.bat</code> to set environment variables.

=== Compiling build tool ===

Compile <code>btool</code> (the command line tool that handles the actual build) using
<pre>g++ buildtool.cpp -o btool -fopenmp</pre>

=== Compiling Inkscape ===

Use <code>btool</code> to compile Inkscape compile and create the distribution directory:
<pre>btool -file build-x64.xml -j 2</pre>
The file <code>build-x64.xml</code> contains the necessary instructions for creating a standard 64-bit build. 
If you want to make a GTK+ 3 build use <code>build-x64-gtk3.xml</code> instead (please note that GTK+ 3 builds are experimental and not ready for production yet).

The <code>-j</code> switch allows to instruct btool to use multiple parallel threads to speed up compilation (e.g. 2 in the example above).

=== Compiling Inkscape using CMake ===

Go to source code directory.

Create the output directory, where the intermediate output goes to.
<pre>
mkdir build
cd build
</pre>

Create the makefiles using CMake.
<pre>cmake .. -G "MinGW Makefiles</pre>

Start the build proccess.
<pre>mingw32-make</pre>

Compiling Inkscape on Windows 64-bit

2016-04-17T15:32:14Z

TheAdib: add cmake instructions

'''For 32 bit: see [[Compiling Inkscape on Windows]]'''

----

Compiling Inkscape on Windows 64-bit works similar to [[Compiling Inkscape on Windows|compiling Inkscape on Windows 32-bit]] where you can find additional information.

This page only describes the basic steps that are required while highlighting the differences compared to a 32-bit build.

== Requirements ==
=== MinGW-w64 ===

Get [http://mingw-w64.org/ MinGW-w64] which contains the necessary GNU developer tools to build Inkscape on Windows.

You have to download a version that is configured for building native win64 applications with ''win32 threading model'' and ''SEH exception handling'', to ensure compatibility with the inkscape-devlibs64.

A matching build based on GCC 5.3 can be downloaded [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/ here]. The exact version used for building the inkscape-devlibs64 is [https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/5.3.0/threads-win32/seh/x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z/download MinGW-w64 x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z].

=== CMake ===

CMake is a Cross-Platform buildsystem generator similar to autotools. It generates '''makefiles''' to be processed by '''make'''.
Get CMake from the [https://cmake.org/ official website cmake.org]. As of writing [https://cmake.org/files/v3.5/cmake-3.5.2-win32-x86.msi version 3.5.2] is the most recent version.

=== Inkscape development libraries for Windows 64-bit ===

Get the [https://code.launchpad.net/inkscape-devlibs64 inkscape-devlibs64] which include pre-compiled binaries of all Inkscape dependencies.

To checkout via Bazaar use the command
<pre>bzr checkout --lightweight lp:inkscape-devlibs64 C:\devlibs64</pre>
The <code>--lightweight</code> switch ensures that you only have to download the latest version of all binaries, <code>C:\devlibs64</code> is the folder you want them to be downloaded to.

See also [[Inkscape Devlibs 64-bit]] ''(only relevant if you want to update the development libraries)''

=== Inkscape source code ===

Get the [https://launchpad.net/inkscape Inkscape source code] from launchpad

To checkout via Bazaar use the command
<pre>bzr checkout lp:inkscape C:\inkscape</pre>

See also additional information on [[Compiling_Inkscape_on_Windows#Obtaining_Inkscape_source_code|obtaining Inkscape source code]] and [[Working with Bazaar|working with Bazaar]].

== Building ==

=== Environment variables ===

Edit the file <code>mingwenv.bat</code> in the root directory of the Inkscape source to match you local paths. Most importantly the two lines
<pre>
IF "%DEVLIBS_PATH%"=="" set DEVLIBS_PATH=c:\devlibs64
IF "%MINGW_PATH%"=="" set MINGW_PATH=C:\mingw64
</pre>
should point to the folders containing MinGW-w64 and the inkscape-devlibs64.

Whenever you want to build Inkscape open a command prompt (<code>cmd.exe</code>), change into the root directory of the Inkscape source and execute <code>mingwenv.bat</code> to set environment variables.

=== Compiling build tool ===

Compile <code>btool</code> (the command line tool that handles the actual build) using
<pre>g++ buildtool.cpp -o btool -fopenmp</pre>

=== Compiling Inkscape ===

Use <code>btool</code> to compile Inkscape compile and create the distribution directory:
<pre>btool -file build-x64.xml -j 2</pre>
The file <code>build-x64.xml</code> contains the necessary instructions for creating a standard 64-bit build. 
If you want to make a GTK+ 3 build use <code>build-x64-gtk3.xml</code> instead (please note that GTK+ 3 builds are experimental and not ready for production yet).

The <code>-j</code> switch allows to instruct btool to use multiple parallel threads to speed up compilation (e.g. 2 in the example above).

=== Compiling Inkscape using CMake ===

Go to source code directory.

Create the output directory, where the intermediate output goes to.
<pre>mkdir build</pre>
<pre>cd build</pre>

Create the makefiles using CMake.
<pre>cmake .. -G "MinGW Makefiles</pre>

Start the build proccess.
<pre>mingw32-make</pre>

Compiling Inkscape on Windows 64-bit

2016-04-17T15:27:22Z

TheAdib: add cmake instructions

Compiling Inkscape on Windows 32-bit

2016-01-24T13:06:10Z

TheAdib:

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

----

Inkscape was originally written for Linux, but it has been ported to other platforms, including Windows. Since Windows is not POSIX compliant and doesn't have several features useful to developers (like package management), compiling Inkscape on Windows is more tedious than on Linux, but perfectly possible. To make it easier, we have compiled a package that contains all the libraries you need to build Inkscape. This reduces the effort of compiling Inkscape to: download and install 3 programs, download library package, download sourcecode, and you are ready to go.

==Setting up the build environment==

To develop Inkscape, you will need the following things:

* [http://wiki.bazaar.canonical.com/WindowsDownloads Bazaar]
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY] programs: puttygen.exe and pageant.exe
* TDM's GCC (MingW): Please use exactly the [http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/Previous/1.1006.0/tdm-gcc-4.6.1.exe/download version 4.6.1 32bit bundle installer] and follow the instructions below. In the setup, '''Uncheck''' the [''Check for updated files on the TDM-GCC server''] when installing, or it will install a newer version. Newer versions (tdm-gcc-4.7+) introduce important changes in gcc and don't work with the current Inkscape devlibs (see [http://old.nabble.com/Compiling-on-Windows-7-x64-td34601489.html developpers' list discussion]).
* Launchpad account

In order to build the installer (not needed for most developers):
* [http://wixtoolset.org Windows Installer XML Toolset] for rencent msi builds
* [http://sourceforge.net/projects/nsis/files/NSIS%202/2.46/nsis-2.46-setup.exe/download NSIS 2.46]

===Install the compiler===
Run the TDM-MinGW installer:
# Install in a path that doesn't contain spaces. The path 'C:\mingw' is ideal beacuse it is currently set in the <tt>mingwenv.bat</tt> file (along with the location of devlibs).
#* TDM-MinGW's default install option may be to a different location. You will have to edit the <tt>mingwenv.bat</tt> file to point there.
#* If you install it into another path, set the environment variable MINGW_PATH to the TDM-MinGW installation directory, e.g. the one containing <tt>README-tdm-gcc.txt</tt> (right click My Computer -> Properties -> Advanced -> Environment Variables).
# Be sure to enable the "GCC -> openmp support" checkbox from the components list

===Create your Launchpad account===
You can skip this step (or do it later) if you just want to download the sources, but not submit your changes.

If you do not have an SSH public/private key pair to identify yourself:
*run the program puttygen.exe to generate an SSH key
*save both its parts.
Log into your Launchpad account, go to your profile page and add the public part of the generated key to the list of SSH keys. Run the program pageant.exe (you can add it to Autorun). A tray icon should appear. Right click it, select "Add Key" and pick the private key file you have just generated from the dialog. Note that you need to repeat this after every login whenever you want to access Launchpad.

Now set up Bazaar. First tell it who you are, then associate with your Launchpad account. You need to use the account name (e.g. johnq), not the display name.(John Q. Public).

C:\> bzr whoami "''Your Name'' <''your_real_email@example.com''>"
C:\> bzr launchpad-login ''your_launchpad_account''

===Install the developer libraries===
Check out Inkscape Devlibs into C:\devlibs. If you check them out elsewhere, set the environment variable DEVLIBS_PATH to the path where they are. Devlibs are a bundle of all the libraries needed to compile Inkscape. If you experience any problems, make sure you have an up to date copy of those libraries and an up to date checkout of Inkscape source. To reduce the size of the download, pass the <tt>--lightweight</tt> parameter.

C:\> bzr checkout --lightweight lp:inkscape-devlibs devlibs

To update devlibs:

C:\devlibs> bzr update

All Inkscape developers can commit to the devlibs trunk. Advanced information about Devlibs, mainy useful when you want to update them to newly released versions of upstream libraries, is available here: [[Inkscape Devlibs]].
You can see some infomation from [https://launchpad.net/inkscape-devlibs launchpad:inkscape-devlibs] and [http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/files trunk/files].

== Obtaining Inkscape source code ==

You can obtain released Inkscape source from a tarball. Since version 0.47 they are hosted on [https://launchpad.net/inkscape Inkscape's Launchpad page]. There are ready-made installers provided, so there's usually little reason to compile the stable version yourself.

To obtain cutting edge code, check out Inkscape source from the Bazaar repository. You can also use the TortoiseBZR shell extensions to do this. The recommended way is to first create a shared repository, then check out the Inkscape branch into that shared repository. Using this setup, branching will be a lot faster.

C:\src\inkscape> bzr init-repo --rich-root .
C:\src\inkscape> bzr upgrade
C:\src\inkscape> bzr checkout lp:inkscape trunk

If you don't want to create any branches, you can skip the shared repository step.

C:\src> bzr checkout lp:inkscape

'''IMPORTANT:''' make sure that the path to your Inkscape source checkout does not contain spaces. Unix tools do not like them and you will end up with a lot of error messages about missing files.

== Set Environmental Variables ==

First set up the environmental variables. You need to run mingwenv once per console session like this:
C:\src\inkscape\trunk> mingwenv
Or you can set the paths in the Windows system settings. Go to (Win 7):

Start->Control Panel ->System and Security->System->Advanced system settings->Advanced->Environment variables->System variables->New.
Add these variable names and values: 
DEVLIBS_PATH c:\devlibs 
MINGW_PATH c:\mingw 
MINGW_BIN c:\mingw\bin 
PKG_CONFIG_PATH c:\devlibs \lib\pkgconfig 
CMAKE_PREFIX_PATH c:\devlibs 
GTKMM_BASEPATH c:\devlibs 

Also, edit the PATH variable, and add these if not already present: 
c:\mingw\bin;c:\devlibs\python;c:\devlibs\bin

After the Environment Variables are set in the Windows system settings, a restart is required.

== Compile the Build Tool ==

Now compile the build tool. (Try the following command one by one. if that command fails)

C:\src\inkscape\trunk> g++ buildtool.cpp -o btool
C:\src\inkscape\trunk> g++ buildtool.cpp -o btool -fopenmp
C:\src\inkscape\trunk> g++ -DNEED_GETTIMEOFDAY buildtool.cpp -o btool -fopenmp

== Building Inkscape ==

Finally initiate the compilation. Get a coffee or take your dog out for a walk, because it will take a rather long time. If you have a multicore processor, add "-j 8" to use (for example) 8 parallel compilation threads.

C:\src\inkscape\trunk> btool -j 8

Once everything is done, there should be an <tt>inkscape</tt> directory that contains the Inkscape executable and libraries needed to run it.

== Rebuilding ==

If you have only changed a few files and want to rebuild, delete the <tt>inkscape</tt> directory and run <tt>btool</tt> again.

To rebuild from scratch, execute the following sequence of commands:
C:\src\inkscape\trunk> btool clean
C:\src\inkscape\trunk> btool

== Dealing With Build Errors ==
Feel free to add any questions or answers you have in here;

'''Q''' - My firewall software (Comodo's Defense+ component or similar) stopped the process continuing to the next step in the build, because I wasn't there to permit an action and it timed out. What can I do?

'''A1''' - The best thing is to disable stuff like Defense+ (put it in learning mode works) because it will stop any process that is not approved, and building makes new files which can't be approved before they're built. Disabling Comodo's Defense+ does not disable your firewall, either inbound or outbound, but just the part that scans every application for suspicious operations. Other firewalls etc may vary.

'''A2''' - If that doesn't suit, often you can simply run btool again and wait for Defense+ (or similar) to ask for approval for the process, and it will then continue as normal with the build. But remember that approving all the processes involved in the build process once doesn't mean they will all slip through next time.

'''A3''' - This is the more complex way to continue, but may help if you have problems with A2. If you know the stage the process was meant to be up to (look at the output in the command windows and compare to the stages in the ''build.xml'' file), you can start again from there.

You may see something like this in the command window;
=============================
## Target : link : link objects and library to create executable
---- task : rc
============ cmd ============
windres -o build/inkres.o --include-dir=src src/inkscape.rc
=============================
---- task : link
This will likely be followed by an error message. This means you were at the ''link'' stage

Now simply type;
...>btool ''stage''
Or in this case
...>btool link
And the build will continue from there.

After this, you will probably have to step through the remaining stages manually, one by one. The stages can include (see build.xml, where each stage is labelled 'target name="''target''"') ''init'', ''touchabout'', ''compile'', ''java'', ''lib'', ''i18n'', ''link'', ''linkinkview'', ''dist'', ''dist-all'', ''clean''.

'''Q''' - How do I rebuild just one ''file.o'' file? For instance if one particular file has gone wrong, or I want to try patching just one part of the code.

'''A''' - To find the right command for building any particular file in Inkscape, just look in the compile.lst after you have used btool once. Search for the name of the particular file (eg: print.cpp) and you will find the command used to compile it. You'll need to paste this into a text file, remove any carriage reurns and then paste that onto the command line.

'''Q''' - After I patched a file, I left a backup of the old file in the same directory called Copy of{filename}.cpp. The compiler complains about this file when building and stops.

'''A''' - Do not leave anything with a suffix .cpp in the source directories, apart from the original (or patched) source files. The build tool will try to compile everything ending in .cpp and will complain. If you backup an old file in the same directory before patching, call it {filename}.cpp.old or similar.

'''Q''' - I think I followed the instruction above. What could have caused the compiling error like this for src/extension/internal/pdfinput/pdf-parser.cpp?

src/extension/internal/pdfinput/pdf-parser.cpp:2248: error: no matching function for call to 'GfxFont::getNextChar(char*&, int&, CharCode*, Unicode [8], int, int*, double*, double*, double*, double*)'

Same error for line 2297 as well.

=== For more information ===
There is some old information on building Inkscape with either Mingw on Windows, or a cross-compiler on Linux, at http://inkscape.modevia.com/win32_inkscape_org/win32buildnotes.html
and old files mey be
http://inkscape.modevia.com/win32libs/
== Creating an installer ==

To create the '''inkscape-$RELEASE-win32.exe''' setup package you need the '''NSIS''' installer on your PC. Get that from http://nsis.sf.net .
You have successfully built Inkscape and everything is in the ...\inkscape\ directory.
Open the ...\packaging\win32\inkscape.nsi using the NSIS program and compile the package. Sooo easy :-)

The new wix installer in the packaging\wix directory creates msi packages. You need the '''windows installer XML''' package; get it from here http://wixtoolset.org/. Follow the instructions in the README file in the packaging\wix directory. The installer scripts parse version information from the inkscape.rc file. The generated packed is named as:

'''inkscape-$RELEASE.msi'''

== Note about Unicode ==

The GTK stack depends on functions only present in NT-based Windows (2000 and later). Therefore, Inkscape code can assume that Unicode functions from the Windows API (like GetCommandLineW) are always present. Note however that you should use the GLib/GTK functions rather the Windows API whenever possible.

=See also=
*[[Compiling Inkscape]]
*[[Using Visual Studio]]

[[Category:Developer Documentation]]

File:Corel pdf 06.png

2015-02-17T23:19:58Z

TheAdib:

File:Corel pdf 05.png

2015-02-17T23:19:31Z

TheAdib:

File:Corel pdf 04.png

2015-02-17T23:18:59Z

TheAdib:

File:Corel pdf 03.png

2015-02-17T23:18:32Z

TheAdib:

File:Corel pdf 02.png

2015-02-17T23:18:02Z

TheAdib:

File:Corel pdf 01.png

2015-02-17T23:17:30Z

TheAdib:

Export To Pdf dialogs

2015-02-17T23:17:17Z

TheAdib:

This page shows export to pdf dialogs from several applications

== Scribus ==
[[File:scribus_pdf_01.png]]
[[File:scribus_pdf_02.png]]
[[File:scribus_pdf_03.png]]
[[File:scribus_pdf_04.png]]
[[File:scribus_pdf_05.png]]
[[File:scribus_pdf_06.png]]
[[File:scribus_pdf_07.png]]
[[File:scribus_pdf_06_01.png]]
[[File:scribus_pdf_06_02.png]]
[[File:scribus_pdf_06_03.png]]

== C*Draw ==

[[File:corel_pdf_01.png]]
[[File:corel_pdf_02.png]]
[[File:corel_pdf_03.png]]
[[File:corel_pdf_04.png]]
[[File:corel_pdf_05.png]]
[[File:corel_pdf_06.png]]

File:Scribus pdf 06 03.png

2015-02-17T23:16:09Z

TheAdib:

Export To Pdf dialogs

2015-02-17T23:15:16Z

TheAdib:

File:Scribus pdf 06 02.png

2015-02-17T23:15:06Z

TheAdib:

File:Scribus pdf 06 01.png

2015-02-17T23:14:11Z

TheAdib:

File:Scribus pdf 07.png

2015-02-17T23:13:28Z

TheAdib:

File:Scribus pdf 06.png

2015-02-17T23:13:02Z

TheAdib:

File:Scribus pdf 05.png

2015-02-17T23:12:39Z

TheAdib: uploaded a new version of "File:Scribus pdf 05.png"

File:Scribus pdf 05.png

2015-02-17T23:11:47Z

TheAdib:

File:Scribus pdf 04.png

2015-02-17T23:11:08Z

TheAdib:

Export To Pdf dialogs

2015-02-17T23:10:39Z

TheAdib:

File:Scribus pdf 03.png

2015-02-17T23:10:14Z

TheAdib:

Export To Pdf dialogs

2015-02-17T23:08:56Z

TheAdib:

This page shows export to pdf dialogs from several applications

== Scribus ==
[[File:scribus_pdf_01]]
[[File:scribus_pdf_02]]

== C*Draw ==

File:Scribus pdf 02.png

2015-02-17T23:07:57Z

TheAdib:

File:Scribus pdf 01.png

2015-02-17T23:06:29Z

TheAdib:

Export To Pdf dialogs

2015-02-17T23:05:29Z

TheAdib: Created page with "This page shows export to pdf dialogs from several applications == Scribus == == C*Draw =="

This page shows export to pdf dialogs from several applications

== Scribus ==

== C*Draw ==

Required PDF Support

2015-02-17T23:02:39Z

TheAdib:

This page is part of the [[PrintingConsensusPoll]].

# What level of Support/features are required?
# What SVG features must be supported beyond the basics?
# Should the deliverable be a library, a stand alone tool, or ...?
# Other questions about requirements?

This page identifies exactly what sort of PDF support Inkscape needs. This information is essential to complete the plan for the [[PrintingConsensusPoll]].

* Arbitrary .pdf and .ps files can be opened or imported directly into an inkscape document in exactly the way that .svg files are imported.
** All shapes are editable
** All text is rendered in the same font as the original .pdf
** All text is appropriately sequential (multi-column pdfs are handled correctly)
** Arbitrary "page to import" is selectable for multi-page documents.
* Arbitrary .svg files can be "saved as" .pdf files
** What does the .pdf rendering model have that .svg does not?
** What does the .svg rendering model have that .pdf does not?
** Perhaps you would like to help [[EricWilhelm]] fill-out this table: [http://scratchcomputing.com/projects/uber-converter/chromista_features.html xar/svg/ps/pdf/crs features] (contact me to get the YAML source)
* Hyperlinks in the PDF file are preserved in the SVG.
* Exporting the SVG to .png produces a pixel accurate ...
* Metadata should be as much preserved as possible
* ... please refactor and refine ...

== What Users Need from Inkscape PDF/PS Support ==

* SVG canvas size needs to be compatible with PDF canvas
* Color SVG's get turned black and white on export; needs to preserve colors
* Better gradient supports. Xara Xtreme does a nice trick with gradients by creating colored steps aligned to the shape/direction of the gradient.
* Better AI support. The Adobe Illustrator file format is a PDF-based format (after version 7), or postscript (before version 7). If Inkscape gains good PDF/PS support, it should also be able to load/save AI files.
* Support for alpha transparency everywhere (objects, gradient stops, etc.)
* Ability to tile one large image across multiple pages (cf. KDEPrint's poster utility [http://printing.kde.org/downloads/])
* /What else?/
* some [[Export To Pdf dialogs]] in this separate page

Required PDF Support

2015-02-17T23:02:18Z

TheAdib:

Required PDF Support

2015-02-17T23:01:23Z

TheAdib: /* What Users Need from Inkscape PDF/PS Support */

Roadmap

2014-11-23T19:45:30Z

TheAdib: /* Random Ideas / Requests / Needs */

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.91 ===

0.91 will be a longer cycle focused on refactoring and new features.

* (DONE) <del>Merge GSoC 2010 work</del>
* (DONE) <del>Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases</del>
* (DONE) <del>Port renderer to Cairo (Krzysztof - GSoC 2010)</del>
* (DONE) <del>Completely remove libnr</del>

=== Inkscape 0.92 ===

=== Inkscape 0.93 ===

=== Inkscape 0.94 ===

=== Inkscape 0.9x ===

=== Inkscape 1.0 ===

=== Inkscape 1.x ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

* Replace VCS.
* Replace Automake Build System.
* Greatly expand Unit test framework.
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Multi-page documents and parent/child document references
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
** Using the above mechanism, make flowed text SVG-compliant.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
* Make the Windows uninstaller work (reevaluate this, we have now msi installier for win32 and Win64)
* make msi Windows install multilingual
* Evaluate pdf exporter to join features from scribus Export
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* Hardware acceleration: make use of modern GPUs to speed up rendering.
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
* CSS support?
* Animation support.
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)

[[Category:Developer Documentation]]

Compiling Inkscape on Windows 32-bit

2012-12-26T00:53:27Z

TheAdib: /* Creating an installer */

Inkscape was originally written for Linux, but it has been ported to other platforms, including Windows. Since Windows is not POSIX compliant and doesn't have several features useful to developers (like package management), compiling Inkscape on Windows is more tedious than on Linux, but perfectly possible. To make it easier, we have compiled a package that contains all the libraries you need to build Inkscape. This reduces the effort of compiling Inkscape to: download and install 3 programs, download library package, download sourcecode, and you are ready to go.

==Setting up the build environment==

To develop Inkscape, you will need the following things:

* [http://wiki.bazaar.canonical.com/WindowsDownloads Bazaar]
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY] programs: puttygen.exe and pageant.exe
* [http://tdm-gcc.tdragon.net/download TDM's GCC (MingW)], the 32 bit bundle installer is the safe choice (it's called tdm-gcc-4.something and should be one of the very first options). Recent versions (tdm-gcc-4.7+) introduce important changes in gcc and don't work with the current Inkscape devlibs (see [http://old.nabble.com/Compiling-on-Windows-7-x64-td34601489.html developpers' list discussion]). Please use the [http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/Previous/1.1006.0/ 4.6.1 version].
* Launchpad account

In order to build the installer (not needed for most developers):
* [http://sourceforge.net/projects/nsis/files/NSIS%202/2.46/nsis-2.46-setup.exe/download NSIS 2.46]

===Install the compiler===
Run the TDM-MinGW installer:
# Install in a path that doesn't contain spaces. The path 'C:\mingw' is ideal beacuse it is currently set in the <tt>mingwenv.bat</tt> file (along with the location of devlibs).
#* TDM-MinGW's default install option may be to a different location. You will have to edit the <tt>mingwenv.bat</tt> file to point there.
#* If you install it into another path, set the environment variable MINGW_PATH to the TDM-MinGW installation directory, e.g. the one containing <tt>README-tdm-gcc.txt</tt> (right click My Computer -> Properties -> Advanced -> Environment Variables).
# Be sure to enable the "openmp support" checkbox from the components list or choose to install all packages (option "TDM-GCC recommended, All Packages" in the TDM-GCC (4.5.1) installer).
#* ''All packages'' option will install support for many other programming languages.

If you have an older version of TDM-GCC (older than 4.5.1?), copy the file "\lib\gcc\mingw32\bin\libgomp-1.dll" to "\bin\libgomp-1.dll" (paths relative to your installation directory).

===Create your Launchpad account===
If you do not have an SSH public/private key pair to identify yourself:
*run the program puttygen.exe to generate an SSH key
*save both its parts.
Log into your Launchpad account, go to your profile page and add the public part of the generated key to the list of SSH keys. Run the program pageant.exe (you can add it to Autorun). A tray icon should appear. Right click it, select "Add Key" and pick the private key file you have just generated from the dialog. Note that you need to repeat this after every login whenever you want to access Launchpad.

Now set up Bazaar. First tell it who you are, then associate with your Launchpad account. You need to use the account name (e.g. johnq), not the display name.(John Q. Public).

C:\> bzr whoami "''Your Name'' <''your_real_email@example.com''>"
C:\> bzr launchpad-login ''your_launchpad_account''

===Install the developer libraries===
Check out Inkscape Devlibs into C:\devlibs. If you check them out elsewhere, set the environment variable DEVLIBS_PATH to the path where they are. Devlibs are a bundle of all the libraries needed to compile Inkscape. If you experience any problems, make sure you have an up to date copy of those libraries and an up to date checkout of Inkscape source. To reduce the size of the download, pass the <tt>--lightweight</tt> parameter.

C:\> bzr checkout --lightweight lp:inkscape-devlibs devlibs

To update devlibs:

C:\devlibs> bzr update

All Inkscape developers can commit to the devlibs trunk. Advanced information about Devlibs, mainy useful when you want to update them to newly released versions of upstream libraries, is available here: [[Inkscape Devlibs]].
You can see some infomation from [https://launchpad.net/inkscape-devlibs launchpad:inkscape-devlibs] and [http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/files trunk/files].

== Obtaining Inkscape source code ==

You can obtain released Inkscape source from a tarball. Since version 0.47 they are hosted on [https://launchpad.net/inkscape Inkscape's Launchpad page]. There are ready-made installers provided, so there's usually little reason to compile the stable version yourself.

To obtain cutting edge code, check out Inkscape source from the Bazaar repository. You can also use the TortoiseBZR shell extensions to do this. The recommended way is to first create a shared repository, then check out the Inkscape branch into that shared repository. Using this setup, branching will be a lot faster.

C:\src\inkscape> bzr init-repo --rich-root .
C:\src\inkscape> bzr upgrade
C:\src\inkscape> bzr checkout lp:inkscape trunk

If you don't want to create any branches, you can skip the shared repository step.

C:\src> bzr checkout lp:inkscape

'''IMPORTANT:''' make sure that the path to your Inkscape source checkout does not contain spaces. Unix tools do not like them and you will end up with a lot of error messages about missing files.

== Building Inkscape ==

Open the command prompt, navigate to the directory with Inkscape sources. First set up some environmental variables. You only need to do this once per console session. This will define the location of your downloaded ''MinGW'' and ''devlibs'' so inkscape can find them.

C:\src\inkscape\trunk> mingwenv

Now compile the build tool.

C:\src\inkscape\trunk> g++ buildtool.cpp -o btool -fopenmp

If that command fails, then try the following command:

C:\src\inkscape\trunk> g++ -DNEED_GETTIMEOFDAY buildtool.cpp -o btool -fopenmp

Finally initiate the compilation. Get a coffee or take your dog out for a walk, because it will take a rather long time. If you have a multicore processor, add "-j 8" to use (for example) 8 parallel compilation threads.

C:\src\inkscape\trunk> btool -j 8

Once everything is done, there should be an <tt>inkscape</tt> directory that contains the Inkscape executable and libraries needed to run it.

== Rebuilding ==

If you have only changed a few files and want to rebuild, delete the <tt>inkscape</tt> directory and run <tt>btool</tt> again.

To rebuild from scratch, execute the following sequence of commands:
C:\src\inkscape\trunk> btool clean
C:\src\inkscape\trunk> btool

== Dealing With Build Errors ==
Feel free to add any questions or answers you have in here;

'''Q''' - My firewall software (Comodo's Defense+ component or similar) stopped the process continuing to the next step in the build, because I wasn't there to permit an action and it timed out. What can I do?

'''A1''' - The best thing is to disable stuff like Defense+ (put it in learning mode works) because it will stop any process that is not approved, and building makes new files which can't be approved before they're built. Disabling Comodo's Defense+ does not disable your firewall, either inbound or outbound, but just the part that scans every application for suspicious operations. Other firewalls etc may vary.

'''A2''' - If that doesn't suit, often you can simply run btool again and wait for Defense+ (or similar) to ask for approval for the process, and it will then continue as normal with the build. But remember that approving all the processes involved in the build process once doesn't mean they will all slip through next time.

'''A3''' - This is the more complex way to continue, but may help if you have problems with A2. If you know the stage the process was meant to be up to (look at the output in the command windows and compare to the stages in the ''build.xml'' file), you can start again from there.

You may see something like this in the command window;
=============================
## Target : link : link objects and library to create executable
---- task : rc
============ cmd ============
windres -o build/inkres.o --include-dir=src src/inkscape.rc
=============================
---- task : link
This will likely be followed by an error message. This means you were at the ''link'' stage

Now simply type;
...>btool ''stage''
Or in this case
...>btool link
And the build will continue from there.

After this, you will probably have to step through the remaining stages manually, one by one. The stages can include (see build.xml, where each stage is labelled 'target name="''target''"') ''init'', ''touchabout'', ''compile'', ''java'', ''lib'', ''i18n'', ''link'', ''linkinkview'', ''dist'', ''dist-all'', ''clean''.

'''Q''' - How do I rebuild just one ''file.o'' file? For instance if one particular file has gone wrong, or I want to try patching just one part of the code.

'''A''' - To find the right command for building any particular file in Inkscape, just look in the compile.lst after you have used btool once. Search for the name of the particular file (eg: print.cpp) and you will find the command used to compile it. You'll need to paste this into a text file, remove any carriage reurns and then paste that onto the command line.

'''Q''' - After I patched a file, I left a backup of the old file in the same directory called Copy of{filename}.cpp. The compiler complains about this file when building and stops.

'''A''' - Do not leave anything with a suffix .cpp in the source directories, apart from the original (or patched) source files. The build tool will try to compile everything ending in .cpp and will complain. If you backup an old file in the same directory before patching, call it {filename}.cpp.old or similar.

'''Q''' - I think I followed the instruction above. What could have caused the compiling error like this for src/extension/internal/pdfinput/pdf-parser.cpp?

src/extension/internal/pdfinput/pdf-parser.cpp:2248: error: no matching function for call to 'GfxFont::getNextChar(char*&, int&, CharCode*, Unicode [8], int, int*, double*, double*, double*, double*)'

Same error for line 2297 as well.

=== For more information ===
There is some old information on building Inkscape with either Mingw on Windows, or a cross-compiler on Linux, at http://inkscape.modevia.com/win32_inkscape_org/win32buildnotes.html
and old files mey be
http://inkscape.modevia.com/win32libs/
== Creating an installer ==

To create the '''inkscape-$RELEASE-win32.exe''' setup package you need the '''NSIS''' installer on your PC. Get that from http://nsis.sf.net .
You have successfully built Inkscape and everything is in the ...\inkscape\ directory.
Open the ...\packaging\win32\inkscape.nsi using the NSIS program and compile the package. Sooo easy :-)

The new wix installer in the packaging\wix directory creates msi packages. You need the '''windows installer XML''' package; get it from here http://wixtoolset.org/. Follow the instructions in the README file in the packaging\wix directory. The installer scripts parse version information from the inkscape.rc file. The generated packed is named as:

'''inkscape-$RELEASE.msi'''

== Note about Unicode ==

The GTK stack depends on functions only present in NT-based Windows (2000 and later). Therefore, Inkscape code can assume that Unicode functions from the Windows API (like GetCommandLineW) are always present. Note however that you should use the GLib/GTK functions rather the Windows API whenever possible.

=See also=
*[[Compiling Inkscape]]

[[Category:Developer Documentation]]

Creating Inkscape distributions

2012-12-06T23:03:51Z

TheAdib: /* Creating a Windows Distro */

{{Other languages|en=Creating Inkscape distributions}}

== Creating Dists of Inkscape ==

Those who wish to produce packaged releases of inkscape are welcome to do so.
If it is packages changes that you've made to the official release, please select a version name that distinguishes it from the official version, to avoid confusion. For example, “inkscape-0.35-johndoe.tar.gz”. Please consider distributing your changes as a patch rather than as a full distribution, as patches tend to be easier to maintain.

Inkscape's release process works like this:

# Chill - Wrap up development work
# Frost - Feature work should be complete. Bug Hunt
# Feature Freeze - Critical bug fixing
# Hard Freeze - Two freeze wardens are named. All development must be done as patches submitted to the freeze wardens for review and integration.
# Branch - The codebase is tagged and branched. Final release tarball is posted. The codebase is returned to regular open development.
# Packaging - Three days are allowed for creating release dists (rpm's, deb's, exe's, and autopackages).
# Release Announcement - A Release Announcement and a Press Release are written and circulated to relevant online news sites. Our Freshmeat record is updated.

=== Feature Freeze Mode ===

In the run-up to [[CreatingDists]], for a short time preceding the tagging of the release it's a good idea to hold off on adding new features or doing other major changes like architectural changes to the code that might decrease its stability. Whether a change is minor enough to be “ok” is left to the developer's judgement, and they're trusted to be conservative and careful.

The most useful activity to do during a feature freeze is to locate and/or fix bugs that produce crashes, and to do so with the smallest amount of change to the codebase possible. If a “proper” fix requires architectural changes or redesign of the code, consider writing that up as a post-release task.

-----

It might be useful to branch off a release branch a week before making the release. Hopefully most people using CVS would switch to this branch at this time. Then only bug fixes can go into that branch. --[[Ted]]

=== Branching the release candidate ===

Before release, a branch should have been be created for that release in the form RELEASE_<major>_<minor>_BRANCH. For example, 0.38 should have a branch called RELEASE_0_38_BRANCH.

Minor fixes and code review can then be performed on that branch before the final release; it also permits making future point releases easily (if necessary).

To create the release branch, do the following:

<pre>svn copy https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_38_BRANCH</pre>

To check out this branch:

<pre>svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_38_BRANCH inkscape-0.38-branch</pre>

Once the release is deemed ready a distribution tarball should be created as below.

=== Creating a distribution source tarball package ===

On the release branch (NOT ON HEAD):

* Set the version name via the file configure.ac in the AC_INIT() macro, packaging/win32/inkscape.nsi, src/inkscape_version.h.mingw, inkscape.rc, inkview.rc and build.xml
* Run `perl packaging/mkNEWS 046 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and lynx. Don't forget to replace 046 with the correct version number. The NEWS file may need some manual cleanup, so do a quick review of it.
* Run ./autogen.sh && ./configure (with any flags, e.g. CXXFLAGS=).
* Run “cd src && make helper/sp-marshal.h helper/sp-marshal.cpp inkscape_version.h && perl mkfiles.pl && perl mkdep.pl”, then do “cvs -q diff -du make.*|less” to check for anything strange (e.g. source files accidentally added or removed), and finally “cvs commit -m '' make.*”.
* Run "cd po && make update-po" to update the translation files. This especially must be done before declaring string freeze.
* Run "make dist"
* This should produce inkscape-VERSION.tar.gz
* Commit the changed configure.ac and other files to the branch
* Tag the release on launchpad

Release tags should be in the form RELEASE_<major>_<minor>_<point>. A non-point-release like 0.38 would get the tag RELEASE_0_38_0, 0.38.1 would get the tag RELEASE_0_38_1, and so on.

On HEAD:

* Change configure.ac and inkscape_version.h.mingw, inkscape.rc, inkview.rc to reflect the new future version

=== GPG signing Tarballs ===

Downstream packagers are asking for and may soon demand gpg signed tarballs. For Fedora, this is not a requirement, but does ease acceptance of packages. It also shows we are doing “The Right Thing”. md5sums are not foolproof.

* To create a gpg signed tarball:

<pre>$gpg -u packager@foo.net --armor --output tarball.sig --detach-sig tarball.tar.gz</pre>

* To verify :

<pre>$gpg --verify ./tarball.asc ./tarball.tar.gz</pre>

Of course, this step doesn't mean much in practice unless people have a trust path to your key. Packagers are encouraged to attend key signing parties and take other measures to establish important trust paths to their keys (particularly with downstream packagers).

:Where are the public keys matching these sig's posted?

=== Creating a Windows Distro ===
Inkscape/sodipodi has always been
buildable on Win32. The problem with the sodipodi and original inkscape build, though,
was that the Win32 builder had to download and configure
a lot of things to make it to work. Mingw, MSYS, automake,
autoconf, pkg-config, the codepages, etc. He would spend more
time on THAT than the actual code.

What a pain for the average developer/user who merely wants
to make Inkscape do what he wants it to do. Why waste
days and days getting it to compile, when the developer
would rather be working on the program itself?

So we spent several weeks collecting libraries, building others,
installing the codepages into the source (which we can delete soon
because of Pango) and creating a set of clean makefiles
that work on Win9x, NT, XP, and the cross-compiler.
It is a bit more work for people like me, but hopefully it
attains its goal of saving a lot of work for other people.

Also, remember that on Unix/Linux, $PREFIX is commonly
/usr/local or /usr or something like that. In windows, all of
a program's files are typically located in their own directory. So all
of the files are located relative to “.”. Actually, relative to
the .exe that is currently running.

.....anyway, just wanted to explain that there is a reason
for the Win32 build to be constructed in such a manner,
and that we haven't just been arbitrary.

The version numbers in the FILEVERSION and PRODUCTVERSION fields within inkscape.rc and inkview.rc need to be updated to reflect the current version number of the release.

Once the tree is built (“make -f Makefile.mingw” and “make -f Makefile.mingw dist-strip”) into the “inkscape” directory, the [http://nsis.sourceforge.net/ NSIS] installer script “inkscape.nsi” can be run to create the self-extracting win32 installer.

The Windows download package should be named according to the following scheme:

inkscape-$RELEASE-$PKG.$WINVER.exe

Where $WINVER is the required Windows version, e.g. “win32”. For example:

inkscape-0.37-1.win32.exe

The new wix installer in the packaging/wix directory creates msi packages. Follow the instructions in the README file. The installer scripts parse version information from the inkscape.rc file. The generated packed is named as:

inkscape-$RELEASE.msi

=== Creating a Debian .deb ===

The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.

=== Creating a distribution RPM ===

Method A:
# do as above for tarball, or download the release tarball
# login as root
# rpmbuild -tb inkscape-x.x.tar.gz
# Your RPMs will be in /usr/src/rpm[[/RPMS]] (/usr/src/redhat on RH systems)
# RPMs should be GPG signed

Method B:
# do as above for tarball, or download the release tarball
# mkdir ~/rpm
# Copy the tarball to ~/rpm/SOURCES/
# Copy the inkscape.spec from the tarball to ~/rpm/SPECS/inkscape.spec
# rpmbuild -ba ~/rpm/SPECS/inkscape.spec
# Your RPMs will be in ~/rpm/RPMS and ~/rpm/SRPMS
# RPMs should be GPG signed

The rpm should be named according to the following pattern:

inkscape-$RELEASE-$PKG.$DISTRO.$ARCH.rpm

Where:

$RELEASE: the Inkscape release number, such as “0.37”, “0.36.2”, etc.
The third number should be omitted if it is 0. (I.e., 0.37 instead of 0.37.0)

$PKG: A version number for your package. Use a value of 1 for your package, and increment it if you
need to update the released package for some reason.

$DISTRO: The name and an indicator of the version number for the distro. E.g.,
rh71, rh90, mdk91, suse90, fc1, etc. No need to be too exhaustive with the distro versions;
for a given brand of distro it's probably enough to have a reasonably “modern” release
and an older one for legacy support. For instance, rh71 and rh90.

$ARCH: The architecture that the package was built on. E.g., i686, i386, athlon, ppc, etc.
Don't bother with i586 - either i386 or i686 is preferred. The i386 packages will run on Cyrix
and K-6.

Examples:

inkscape-0.37-1.mdk80.i386.rpm
inkscape-0.37-1.mdk80.i686.rpm
inkscape-0.37-1.mdk91.i386.rpm
inkscape-0.37-1.mdk91.i686.rpm

inkscape-0.37-1.fc1.i386.rpm
inkscape-0.37-1.fc1.i686.rpm
inkscape-0.37-1.fc1.athlon.rpm
inkscape-0.37-1.fc1.ppc.rpm

For creating spec files, feel free to list yourself as the packager, but please use
inkscape-devel@lists.sourceforge.net as the contact email address, to ensure that
questions/complaints about the RPM go to the official support channel.

==== Patching RPMs ====

Occasionally, the RPM will not build without some modifications. If the problem is serious enough that it affects every packaging format, this could signal a need to do a point release, but usually you can just add a patch specifically for the RPM. This is what RPM is for, after all. :-)

Here's how to do it:

1. Create a copy of the source tree, with the modifications needed to correct the issue.
2. Generate a patch like this:

$ diff -uNr package-1.0/ package-1.0p/ > ../SOURCES/package-1.0-my.patch

3. Next add the patch to the RPM. In the specfile at %_topdir/SPECS/package.spec, add a line like this at the top of the file:

Patch0: package-1.0-my.patch

Then further down add a line after the %setup section, like this:

%prep
%setup ...
%patch0 -p1

It's a very good idea to split up changes into discrete patches, giving each a different number (they don't have to be consecutively numbered). Also, be sure to upload the patch(es) to the patch tracker so they'll get into the codebase for the next release.

Then rebuild the package like this:

rpmbuild -ba SPECS/package.spec

=== Signing your package ===

First, you need to have a public/private keypair. This can be generated with gpg using 'gpg --gen-key'.

To add a signature to an extisting package, use the command rpm --addsign /path/to/package.rpm To sign in the process of building a package, use rpmbuild -bb --sign

To check the signature on a package, use rpm --checksig.

=== Releasing Dists on the [[SourceForge]] File Release Tool ===

To release a file: (You need Release Tech permission for your Inkscape account)

* ftp upload.sf.net (anonymous/anonymous)
* cd incoming
* mput filename
* go to Admin -> File Releases
* scroll to the bottom and click [Add Release] to the inkscape item
* Enter 0.35 in the box & click “Create this Release”
* Fill in the form, checkbox the file you uploaded in (c)
* It won't give you a clear “success” message, but you can check it got in right by going to the Files list. You can then edit any of the info you entered, to make it more correct.

Also see [[CVSNamingConventions]] if you are making a release.

=== Announcing Releases ===

When you cut a release, send a copy of the release notes as an announcement to inkscape-announce@lists.sourceforge.net.
If you find other mailing lists or websites that should receive the announcements, add their email address to the inkscape-announce list. This is done by a list admin such as Bryce Harrington.

'''[[AnnouncingReleases]]''' - Keep an eye out for other places we could announce such as distros or graphics-related sites (not only Linux-centric!).

=== Updating Website Collateral ===

When a new release is cut, there are several pieces of info that need to be added to the website:

* Add a news item on front page
* Review/revise FAQ
* Review/revise Roadmap
* Add or revise Screenshots (if appropriate)
* doc directory: Add the manpage for the release, update doc/keys.html file, and change the corresponding version number(s) in doc/index.php.
** From the shell on inkscape.org, cd to /home/inkscape/inkscape_web and run the command “(cd ../inkscape; svn update; chmod g+w -R * 2>/dev/null); pod2html --cachedir=/tmp --infile=../inkscape/inkscape.pod --outfile=doc/inkscape-man.html”.

[[Category:Help Wanted]]

Creating Inkscape distributions

2012-12-06T22:58:11Z

TheAdib: /* Creating a distribution source tarball package */

{{Other languages|en=Creating Inkscape distributions}}

== Creating Dists of Inkscape ==

Those who wish to produce packaged releases of inkscape are welcome to do so.
If it is packages changes that you've made to the official release, please select a version name that distinguishes it from the official version, to avoid confusion. For example, “inkscape-0.35-johndoe.tar.gz”. Please consider distributing your changes as a patch rather than as a full distribution, as patches tend to be easier to maintain.

Inkscape's release process works like this:

# Chill - Wrap up development work
# Frost - Feature work should be complete. Bug Hunt
# Feature Freeze - Critical bug fixing
# Hard Freeze - Two freeze wardens are named. All development must be done as patches submitted to the freeze wardens for review and integration.
# Branch - The codebase is tagged and branched. Final release tarball is posted. The codebase is returned to regular open development.
# Packaging - Three days are allowed for creating release dists (rpm's, deb's, exe's, and autopackages).
# Release Announcement - A Release Announcement and a Press Release are written and circulated to relevant online news sites. Our Freshmeat record is updated.

=== Feature Freeze Mode ===

In the run-up to [[CreatingDists]], for a short time preceding the tagging of the release it's a good idea to hold off on adding new features or doing other major changes like architectural changes to the code that might decrease its stability. Whether a change is minor enough to be “ok” is left to the developer's judgement, and they're trusted to be conservative and careful.

The most useful activity to do during a feature freeze is to locate and/or fix bugs that produce crashes, and to do so with the smallest amount of change to the codebase possible. If a “proper” fix requires architectural changes or redesign of the code, consider writing that up as a post-release task.

-----

It might be useful to branch off a release branch a week before making the release. Hopefully most people using CVS would switch to this branch at this time. Then only bug fixes can go into that branch. --[[Ted]]

=== Branching the release candidate ===

Before release, a branch should have been be created for that release in the form RELEASE_<major>_<minor>_BRANCH. For example, 0.38 should have a branch called RELEASE_0_38_BRANCH.

Minor fixes and code review can then be performed on that branch before the final release; it also permits making future point releases easily (if necessary).

To create the release branch, do the following:

<pre>svn copy https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_38_BRANCH</pre>

To check out this branch:

<pre>svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_38_BRANCH inkscape-0.38-branch</pre>

Once the release is deemed ready a distribution tarball should be created as below.

=== Creating a distribution source tarball package ===

On the release branch (NOT ON HEAD):

* Set the version name via the file configure.ac in the AC_INIT() macro, packaging/win32/inkscape.nsi, src/inkscape_version.h.mingw, inkscape.rc, inkview.rc and build.xml
* Run `perl packaging/mkNEWS 046 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and lynx. Don't forget to replace 046 with the correct version number. The NEWS file may need some manual cleanup, so do a quick review of it.
* Run ./autogen.sh && ./configure (with any flags, e.g. CXXFLAGS=).
* Run “cd src && make helper/sp-marshal.h helper/sp-marshal.cpp inkscape_version.h && perl mkfiles.pl && perl mkdep.pl”, then do “cvs -q diff -du make.*|less” to check for anything strange (e.g. source files accidentally added or removed), and finally “cvs commit -m '' make.*”.
* Run "cd po && make update-po" to update the translation files. This especially must be done before declaring string freeze.
* Run "make dist"
* This should produce inkscape-VERSION.tar.gz
* Commit the changed configure.ac and other files to the branch
* Tag the release on launchpad

Release tags should be in the form RELEASE_<major>_<minor>_<point>. A non-point-release like 0.38 would get the tag RELEASE_0_38_0, 0.38.1 would get the tag RELEASE_0_38_1, and so on.

On HEAD:

* Change configure.ac and inkscape_version.h.mingw, inkscape.rc, inkview.rc to reflect the new future version

=== GPG signing Tarballs ===

Downstream packagers are asking for and may soon demand gpg signed tarballs. For Fedora, this is not a requirement, but does ease acceptance of packages. It also shows we are doing “The Right Thing”. md5sums are not foolproof.

* To create a gpg signed tarball:

<pre>$gpg -u packager@foo.net --armor --output tarball.sig --detach-sig tarball.tar.gz</pre>

* To verify :

<pre>$gpg --verify ./tarball.asc ./tarball.tar.gz</pre>

Of course, this step doesn't mean much in practice unless people have a trust path to your key. Packagers are encouraged to attend key signing parties and take other measures to establish important trust paths to their keys (particularly with downstream packagers).

:Where are the public keys matching these sig's posted?

=== Creating a Windows Distro ===
Inkscape/sodipodi has always been
buildable on Win32. The problem with the sodipodi and original inkscape build, though,
was that the Win32 builder had to download and configure
a lot of things to make it to work. Mingw, MSYS, automake,
autoconf, pkg-config, the codepages, etc. He would spend more
time on THAT than the actual code.

What a pain for the average developer/user who merely wants
to make Inkscape do what he wants it to do. Why waste
days and days getting it to compile, when the developer
would rather be working on the program itself?

So we spent several weeks collecting libraries, building others,
installing the codepages into the source (which we can delete soon
because of Pango) and creating a set of clean makefiles
that work on Win9x, NT, XP, and the cross-compiler.
It is a bit more work for people like me, but hopefully it
attains its goal of saving a lot of work for other people.

Also, remember that on Unix/Linux, $PREFIX is commonly
/usr/local or /usr or something like that. In windows, all of
a program's files are typically located in their own directory. So all
of the files are located relative to “.”. Actually, relative to
the .exe that is currently running.

.....anyway, just wanted to explain that there is a reason
for the Win32 build to be constructed in such a manner,
and that we haven't just been arbitrary.

The version numbers in the FILEVERSION and PRODUCTVERSION fields within inkscape.rc and inkview.rc need to be updated to reflect the current version number of the release.

Once the tree is built (“make -f Makefile.mingw” and “make -f Makefile.mingw dist-strip”) into the “inkscape” directory, the [http://nsis.sourceforge.net/ NSIS] installer script “inkscape.nsi” can be run to create the self-extracting win32 installer.

The Windows download package should be named according to the following scheme:

inkscape-$RELEASE-$PKG.$WINVER.exe

Where $WINVER is the required Windows version, e.g. “win32”. For example:

inkscape-0.37-1.win32.exe

=== Creating a Debian .deb ===

The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.

=== Creating a distribution RPM ===

Method A:
# do as above for tarball, or download the release tarball
# login as root
# rpmbuild -tb inkscape-x.x.tar.gz
# Your RPMs will be in /usr/src/rpm[[/RPMS]] (/usr/src/redhat on RH systems)
# RPMs should be GPG signed

Method B:
# do as above for tarball, or download the release tarball
# mkdir ~/rpm
# Copy the tarball to ~/rpm/SOURCES/
# Copy the inkscape.spec from the tarball to ~/rpm/SPECS/inkscape.spec
# rpmbuild -ba ~/rpm/SPECS/inkscape.spec
# Your RPMs will be in ~/rpm/RPMS and ~/rpm/SRPMS
# RPMs should be GPG signed

The rpm should be named according to the following pattern:

inkscape-$RELEASE-$PKG.$DISTRO.$ARCH.rpm

Where:

$RELEASE: the Inkscape release number, such as “0.37”, “0.36.2”, etc.
The third number should be omitted if it is 0. (I.e., 0.37 instead of 0.37.0)

$PKG: A version number for your package. Use a value of 1 for your package, and increment it if you
need to update the released package for some reason.

$DISTRO: The name and an indicator of the version number for the distro. E.g.,
rh71, rh90, mdk91, suse90, fc1, etc. No need to be too exhaustive with the distro versions;
for a given brand of distro it's probably enough to have a reasonably “modern” release
and an older one for legacy support. For instance, rh71 and rh90.

$ARCH: The architecture that the package was built on. E.g., i686, i386, athlon, ppc, etc.
Don't bother with i586 - either i386 or i686 is preferred. The i386 packages will run on Cyrix
and K-6.

Examples:

inkscape-0.37-1.mdk80.i386.rpm
inkscape-0.37-1.mdk80.i686.rpm
inkscape-0.37-1.mdk91.i386.rpm
inkscape-0.37-1.mdk91.i686.rpm

inkscape-0.37-1.fc1.i386.rpm
inkscape-0.37-1.fc1.i686.rpm
inkscape-0.37-1.fc1.athlon.rpm
inkscape-0.37-1.fc1.ppc.rpm

For creating spec files, feel free to list yourself as the packager, but please use
inkscape-devel@lists.sourceforge.net as the contact email address, to ensure that
questions/complaints about the RPM go to the official support channel.

==== Patching RPMs ====

Occasionally, the RPM will not build without some modifications. If the problem is serious enough that it affects every packaging format, this could signal a need to do a point release, but usually you can just add a patch specifically for the RPM. This is what RPM is for, after all. :-)

Here's how to do it:

1. Create a copy of the source tree, with the modifications needed to correct the issue.
2. Generate a patch like this:

$ diff -uNr package-1.0/ package-1.0p/ > ../SOURCES/package-1.0-my.patch

3. Next add the patch to the RPM. In the specfile at %_topdir/SPECS/package.spec, add a line like this at the top of the file:

Patch0: package-1.0-my.patch

Then further down add a line after the %setup section, like this:

%prep
%setup ...
%patch0 -p1

It's a very good idea to split up changes into discrete patches, giving each a different number (they don't have to be consecutively numbered). Also, be sure to upload the patch(es) to the patch tracker so they'll get into the codebase for the next release.

Then rebuild the package like this:

rpmbuild -ba SPECS/package.spec

=== Signing your package ===

First, you need to have a public/private keypair. This can be generated with gpg using 'gpg --gen-key'.

To add a signature to an extisting package, use the command rpm --addsign /path/to/package.rpm To sign in the process of building a package, use rpmbuild -bb --sign

To check the signature on a package, use rpm --checksig.

=== Releasing Dists on the [[SourceForge]] File Release Tool ===

To release a file: (You need Release Tech permission for your Inkscape account)

* ftp upload.sf.net (anonymous/anonymous)
* cd incoming
* mput filename
* go to Admin -> File Releases
* scroll to the bottom and click [Add Release] to the inkscape item
* Enter 0.35 in the box & click “Create this Release”
* Fill in the form, checkbox the file you uploaded in (c)
* It won't give you a clear “success” message, but you can check it got in right by going to the Files list. You can then edit any of the info you entered, to make it more correct.

Also see [[CVSNamingConventions]] if you are making a release.

=== Announcing Releases ===

When you cut a release, send a copy of the release notes as an announcement to inkscape-announce@lists.sourceforge.net.
If you find other mailing lists or websites that should receive the announcements, add their email address to the inkscape-announce list. This is done by a list admin such as Bryce Harrington.

'''[[AnnouncingReleases]]''' - Keep an eye out for other places we could announce such as distros or graphics-related sites (not only Linux-centric!).

=== Updating Website Collateral ===

When a new release is cut, there are several pieces of info that need to be added to the website:

* Add a news item on front page
* Review/revise FAQ
* Review/revise Roadmap
* Add or revise Screenshots (if appropriate)
* doc directory: Add the manpage for the release, update doc/keys.html file, and change the corresponding version number(s) in doc/index.php.
** From the shell on inkscape.org, cd to /home/inkscape/inkscape_web and run the command “(cd ../inkscape; svn update; chmod g+w -R * 2>/dev/null); pod2html --cachedir=/tmp --infile=../inkscape/inkscape.pod --outfile=doc/inkscape-man.html”.

[[Category:Help Wanted]]

Contact information archive

2012-12-06T22:49:49Z

TheAdib: /* Usernames on the various servers as previously volunteered */

== Usernames on the various servers as previously volunteered ==
This information was previously displayed on the [[Contact information|Contact Information]] page.
 
{| class="wikitable" border="1"
|-
!Person
!Jabber
!Launchpad
!Wiki
!Sourceforge
!Email
!IRC
!AIM
!ICQ
!Nickname(s)

|-
!Bryce Harrington
|bryce at gristle dot org
|[https://launchpad.net/~bryceharrington ~bryceharrington]
|[[User:BryceHarrington]]
|bryce: [http://bryce.users.sourceforge.net/ Developer] [https://sourceforge.net/users/bryce Activity]
|style="color:white"|bryce at osdl dot org
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Mental Guy
|mental at gristle dot org
|[https://launchpad.net/~mental ~mental]
|[[User:MenTaLguY]]
|mental: [http://mental.users.sourceforge.net/ Developer] [https://sourceforge.net/users/mental Activity]
|mental at rydia dot net
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Ted Gould
|ted at gristle dot org
|[https://launchpad.net/~ted ~ted]
|[[User:TedGould]]
|gouldtj: [http://gouldtj.users.sourceforge.net/ Developer] [https://sourceforge.net/users/gouldtj Activity]
|ted at gould dot cx
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Bulia Byak
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~buliabyak ~buliabyak] [https://launchpad.net/~buliabyak-users ~buliabyak-users]
|[[User:BuliaByak]]
|buliabyak: [http://buliabyak.users.sourceforge.net/ Developer] [https://sourceforge.net/users/buliabyak Activity]
|buliabyak at users dot sourceforge dot net
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Jon Phillips
|rejon at jabber dot org
|[https://launchpad.net/~rejon ~rejon]
|[[User:Jon Phillips]]
|kidproto: [http://kidproto.users.sourceforge.net/ Developer] [https://sourceforge.net/users/kidproto Activity]
|jon at rejon dot org
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|kidproto rejon

|-
!Aaron C Spike
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~acspike ~acspike]
|[[User:acspike]]
|acspike: [http://acspike.users.sourceforge.net/ Developer] [https://sourceforge.net/users/acspike Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Bob Jamison
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~ishmalius ~ishmalius]
|[[User:ishmalius]]
|ishmal: [http://ishmal.users.sourceforge.net/ Developer] [https://sourceforge.net/users/ishmal Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Arpad Biro
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~biro-arpad ~biro-arpad]
|[[User:biro-arpad]]
|a_b: [http://a_b.users.sourceforge.net/ Developer] [https://sourceforge.net/users/a_b Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Josh Andler
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~scislac ~scislac]
|[[User:scislac]]
|scislac: [http://scislac.users.sourceforge.net/ Developer] [https://sourceforge.net/users/scislac Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Cedric Gemy
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~pygmee ~pygmee]
|[[User:pygmee]]
|pygmee: [http://pygmee.users.sourceforge.net/ Developer] [https://sourceforge.net/users/pygmee Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Jon Cruz
|joncruz at gristle dot org
|[https://launchpad.net/~jon-joncruz ~jon-joncruz]
|[[User:JonCruz]]
|joncruz: [http://joncruz.users.sourceforge.net/ Developer] [https://sourceforge.net/users/joncruz Activity]
|jon at jon cruz dot org
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Nathan Hurst
|njh at jabber dot org
|[https://launchpad.net/~njh-njhurst ~njh-njhurst]
|[[User:NathanHurst]] [[NathanHurst]]
|njh: [http://njh.users.sourceforge.net/ Developer] [https://sourceforge.net/users/njh Activity]
|mail dot csse da monash doto edu dot au at njh
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Tom von Schwerdtner
|tvon at jabber dot org
|[https://launchpad.net/~tvon ~tvon]
|[[User:TomvonSchwerdtner]]
|tvon: [http://tvon.users.sourceforge.net/ Developer] [https://sourceforge.net/users/tvon Activity]
|tvon at etria dot com
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Tom Ingham
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~thomas.ingham ~thomas.ingham]
|[[User:TomIngham]]
|tingham: [http://tingham.users.sourceforge.net/ Developer] [https://sourceforge.net/users/tingham Activity]
|tingham at coalmarch dot com
|style="color:white"|IRC at domain dot tld
|tingham at mac dot com
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Robert Crosbie
|swingincelt at jabber dot com
|[https://launchpad.net/~swingincelt ~swingincelt]
|style="color:white"|[[User:swingincelt]]
|swingincelt: [http://swingincelt.users.sourceforge.net/ Developer] [https://sourceforge.net/users/swingincelt Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Johan Ceuppens
|jceuppen at gristle dot org
|style="color:white"|[https://launchpad.net/~Launchpad ~Launchpad]
|[[User:JohanCeuppens]]
|jceuppen: [http://jceuppen.users.sourceforge.net/ Developer] [https://sourceforge.net/users/jceuppen Activity]
|jceuppen at sourceforge dot net
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Myrkraverk (pkt == dot)
|myrkraverk at gristle pkt org
|[https://launchpad.net/~myrkraverk ~myrkraverk]
|[[User:Myrkraverk]]
|myrkraverk: [http://myrkraverk.users.sourceforge.net/ Developer] [https://sourceforge.net/users/myrkraverk Activity]
|myrkraverk at users pkt sourceforge pkt net
|myrkraverk at freenode pkt net
|myrkraverk at netscape pkt net
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!John Cliff (Simarilius)
|simarilius at gristle dot org
|style="color:white"|[https://launchpad.net/~johncliff ~johncliff]
|[[User:Simarilius]] [[SimTODO|Simarilius' To Do list]]
|simarilius: [http://johncliff.users.sourceforge.net/ Developer] [https://sourceforge.net/users/johncliff Activity]
|simarilius at yahoo dot com
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Carl Hetherington
|cth103 at myjabber dot net
|[https://launchpad.net/~cth-carlh ~cth-carlh]
|[[User:CarlHetherington]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|inkscape at carlh dot net
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Derek Moore
|jizzbug at gristle dot org
|style="color:white"|[https://launchpad.net/~Launchpad ~Launchpad]
|[[User:DerekMoore]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|derekm at hackunix dot org
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|1290241
|style="color:white"|nicknames

|-
!von Halenbach
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~lustik ~lustik]
|[[User:vonHalenbach]]
|vonHalenbach: [http://vonHalenbach.users.sourceforge.net/ Developer] [https://sourceforge.net/users/vonHalenbach Activity]
|vonHalenbach at users dot sourceforge dot net
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Chris Campbell
|caliga ät gristle (.) org
|[https://launchpad.net/~caliga ~caliga]
|[[User:Caliga]]
|caliga: [http://caliga.users.sourceforge.net/ Developer] [https://sourceforge.net/users/caliga Activity]
|inkscape at stiefelweb semicolon de
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|143406052
|style="color:white"|nicknames

|-
!Fzap
|fzap (at) jabber (dot) i-pobox (dot) net
|[https://launchpad.net/~pflaumenmus92 ~pflaumenmus92]
|[[User:Fzap]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|inkscape (dot) 100 (dot) schimano (at) spamgourmet (dot) com
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!theAdib
|theAdib at jabber dot org
|[https://launchpad.net/~theadib ~theadib]
|[[User:Adib]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|theAdib at gmail dot com
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Colin Marquardt
|cmarqu splat jabber bot org
|[https://launchpad.net/~ubuntu-marquardt-home ~ubuntu-marquardt-home]
|[[User:Colin_Marquardt]]
|cmarqu: [http://cmarqu.users.sourceforge.net/ Developer] [https://sourceforge.net/users/cmarqu Activity]
|inkscape bat marquardt-home spot de
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Illith
|ill66 ätt jabber punkkt ccc punkkt de
|style="color:white"|[https://launchpad.net/~Launchpad ~Launchpad]
|[[User:ILL.ONE]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|ILLITH ätt gmx punkkt de
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Matiphas
|style="color:white"|Jabber at gristle dot org
|[https://launchpad.net/~matiphas-users ~matiphas-users]
|[[User:Matiphas]]
|Matiphas: [http://Matiphas.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Matiphas Activity]
|matiphas chez free point fr
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|-
!Josef Vybíral
|cornelius at njs dot netlab dot cz
|[https://launchpad.net/~cornelius-cz ~cornelius-cz]
|[[User:cornelius]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|josef.vybiral at gmail dot com
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|cornelius

|-
!Person Template
|style="color:white"|Jabber at gristle dot org
|style="color:white"|[https://launchpad.net/~Launchpad ~Launchpad]
|style="color:white"|[[User:Wiki]]
|style="color:white"|Sourceforge: [http://Sourceforge.users.sourceforge.net/ Developer] [https://sourceforge.net/users/Sourceforge Activity]
|style="color:white"|email at domain dot tld
|style="color:white"|IRC at domain dot tld
|style="color:white"|AIM at domain dot tld
|style="color:white"|1234567
|style="color:white"|nicknames

|}
[[Category:Wiki Attic]]

Compiling Inkscape on Windows 32-bit

2009-11-22T11:44:00Z

TheAdib: howto include inkview into the win32 build

See the [http://sourceforge.net/tracker/index.php?func=detail&aid=847856&group_id=93438&atid=604308 Win32 Build ticket] for some info.

=== Inkscape under Windows ===

Inkscape was originally written for Linux, but has been ported to other platforms, including Windows, through the work of a number of dedicated developers.

You can get pre-built binaries of the Windows releases (both stable and development) from the [http://www.inkscape.org/download/?lang=en Inkscape download page]

=== Building Your Own Binary ===
As well as getting a pre-built binary, you can also build your own. You may do this for fun, to learn about programming, or to help test or improve Inkscape.

Several steps are required to set things up before you can build your own binary, as follows;

1. You should install the TortoiseSVN program to help manage source files and patching (if you know how to do this without Tortoise, feel free)

2. You need to download the Inkscape source code

3. You will need to download and install the MinGW compiler and development libraries (devlibs) used by Inkscape

4. You will possibly want to patch the source code if testing bug fixes

5. You are then able to build the Inkscape Binary

6. You may have to deal with some errors, but hopefully not...

7. If you're keen, you can also generate an installation package for Windows

==== Install The TortoiseSVN Program ====
The best way to get the source is straight from the SVN repository using the TortoiseSVN program. Follow these steps;

* Get TortoiseSVN from http://tortoisesvn.net/downloads
* Install Tortoise SVN.

==== Download the Inkscape Source Code ====
'''''Setting up a local source repository:'''''
* Once Tortoise is installed, make a working folder wherever you want. It can be on a different partition if you wish - it doesn't matter.
* Inside the working folder, right click and select ''TortoiseSVN'' -> ''Create repository here''. This will make a bunch of folders inside your working folder.
* Now make another folder in the working folder called 0.46branch or whatever else you'd like to call it. This will hold the source files.

'''''Getting the source:'''''
* Enter the folder you created for the source files. Right click and select ''SVN Checkout''.
* Enter the URL for the source code you want;
** For the 0.46 release branch, use https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_46_BRANCH/ (This branch of the source is frozen for the 0.46 release. New features are not allowed in order to focus on bug fixing. This is what you need to test for bugs in the 0.46 release.)
*** Someone has reported that to get this to work with the libraries above, they had to edit build-dw2.xml and build.xml and replace the instances (1 per file) of libpoppler-2.dll with libpoppler-3.dll. It compiles without the changes, but won't run. (Compiling/Running on Vista). This may have been corrected by now, so don't do this unless you have problems...
** For the 0.47 (or later) development branch (trunk), use https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk/ (This branch of the source is for ongoing development and includes new and experimental features not in the 0.46 release branch. It is slowly diverging from the 0.46 release branch, thus becoming progressively less useful for testing bugs in the 0.46 release.)
* TortoiseSVN will now download the source files, which are just over 30Mb.
* To keep the source files up to date in future, simply right click on your working folder and select ''SVN update''.

'''''Notes:'''''
* You can also get a zipped up version of the trunk (0.47 dev) from Ishmal's site - http://inkscape.modevia.com/svn-snap/

==== Download The MinGW Compiler & Dev Libraries ====

Thanks to Ishmal, it is extremely easy to set up your system to compile Inkscape. He has made a complete set of compiler and library files available from his website - http://inkscape.modevia.com/win32libs/.

Before you download, check for the latest versions. As of '''Feb 26 2009''' those are:
* The mingw compiler version 4.2.1 http://inkscape.modevia.com/win32libs/mingw-4.2.1-071022-dw2.7z
* The latest library SVN snapshot is http://inkscape.modevia.com/win32libs/devlibs-svn-0811161728.7z - this is currently just less than 120Mb
(you can optionally get the files completely using svn, located at https://svn.modevia.com/inkscape/devlibs - although this will be a significantly bigger download as the files are not compressed)

The configuration files expect the compiler and the development library files (devlibs) in specific directories:
* Unzip the compiler (mingw-{version}.7z) to C:\MINGW (referenced by mingwenv.bat)
* Unzip the other libraries (devlibs-{version}.7z) to C:\DEVLIBS (must be this directory unless you want to edit the file build.xml used by buildtool)
* Once you have unzipped devlibs to C:\DEVLIBS make sure it is up to date with the latest svn version by running svn update. If you have TortoiseSVN installed this can be done by right-clicking on the devlibs folder and clicking ''SVN update''.

==== Patch The Source Code ====

'''''Using TortoiseSVN:'''''

Tortoise makes patching quite easy. Follow these steps;

1. Find your patch. Windows Patches to the main SVN are now being kept in a folder under your main working directory called ''packaging\win32\patches''. If you download or make a subsequent patch, put it in this directory to keep things orderly. It should be called {patchname}.patch or {patchname}.diff

2. Right click on the patch, and select ''TortoiseSVN'' -> ''Apply Patch...''. Because the Windows patches are kept a little tucked away, Tortoise will probably give a message; '''The path {working directory}\packaging\win32\patches seems not to match the paths in the patchfile. But Tortoise found the path {working directory} matches it better. Do you want to use the suggested path instead?''' Click ''Yes'' to proceed.

3. Now comes the actual patching process. See the Tortoise website for an explanation of how to use the merge tool - http://tortoisesvn.net/docs/release/TortoiseMerge_en/tmerge-dug.html#tmerge-dug-open-view (see also the following pages)

4. Once patched, you will now notice that the patched file has a red exclamation rather than a green tick, as do its parent folders. This signifies that it has been altered from the SVN version, and helps you find altered files really quickly.

5. If you want to go back to the SVN version you originally ''checked out'', simply right click on an individual file or a whole folder and select ''TortoiseSVN'' -> ''Revert''. This will bring up a list of files that can be reverted. If you only selected one file, only that will be available to revert. If you selected a folder, all the modified files in that folder will be available to revert. Tick only those you wish to revert to the SVN version last checked out.

'''''Notes:'''''
* When applying several patches at once, you will possibly find that some patches update the same code modules. This is normal, and Tortoise can help you compare files and resolve conflicts. See the [http://tortoisesvn.net/docs/release/TortoiseMerge_en/tmerge-dug.html#tmerge-dug-open-view link mentioned above] to learn more.
* Sometimes conflicts are not able to be resolved using Tortoise, and you will need to edit the files by hand. Don't worry, you can always ''revert'' the files if you make a mistake. A good text editor to help is Notepad 2 - http://www.flos-freeware.ch/
* If you edit the source files yourself, Tortoise will register that the files are changed with an exclamation mark. To create your own patch from a changed file, right click on the ''src'' directory folder that contains your changed file, then select ''Tortoise SVN -> Create Patch''. Now tick only the file/s you edited and save the patch file. This can be posted to a bug report as a test, and possibly committed to SVN if your patch works.

'''''Using the GNU patch program:'''''

For those who love the command line, you can patch the hard way using the GNU patch program.

* Download the program from here - http://gnuwin32.sourceforge.net/packages/patch.htm
* Put the patch program wherever you like, as it works independently from the compiler.
* If the patch file refers to the location in its header, put it in the /src directory and then patch, otherwise put it in the same directory as the file to be patched
* In a command window, type something like the following;
...>patch --binary {''modulename''}.cpp {''modulename''}.cpp.patch
* You should now have a patched code module to copy back to the same spot in the source tree.
* The ''--binary'' switch is only necessary if the files contain the wrong sort of line endings. The [http://gnuwin32.sourceforge.net/packages/patch.htm GnuWin32 Patch page] notes the following; ''"On MS-Windows, the patch file must be a text file, i.e. CR-LF must be used as line endings. A file with LF may give the error: "Assertion failed, hunk, file patch.c, line 343," unless the option '--binary' is given."''

==== Build The Inkscape Binary ====

Before you begin, it might be an idea to temporarily lower the level of any over zealous security software, screen savers or other background programs that chew a lot of processor power when the computer is not attended. These programs can interfere with the build process, and cause you to have to start again.

'''''Doing A New Build'''''

You will need to open a command window (DOS prompt) to build the binary. Go to the Start Menu, select Run, and then type command (or cmd). Now you need to step into the Inkscape source directory:
...\> cd ...\inkscape

Firstly run the batch file that sets up the MinGW environment variables
...\> mingwenv.bat
You can usually just type mingwenv (enter) and Windows will execute the batch file.

Now, build the build tool:
...\> g++ buildtool.cpp -o btool
or, if you get errors about gettimeofday:
...\> g++ -DNEED_GETTIMEOFDAY buildtool.cpp -o btool

Now you can start the build process by simply running btool.
...\> btool

Grab a coffee and find something else to do. On an AMD-64 3000+ 1Gb it takes about 70 minutes, but your mileage may vary. The build process can normally continue in the background while you're doing other stuff on your PC.

'''''Please note:''''' that the standard btool only builds Inkscape. In order to have Inkview included you must pass an additional parameter to btool:
...\>btool dist-all

If everything went well, you should now have you fresh Inkscape in the ...\Inkscape directory.

'''''Re-building after modifying source modules'''''

If you've already built the source once and done a few changes to source code files, you can do a quick rebuild using many of the files already compiled in the ''build'' directory. Only those that need to be rebuilt will be, and the ''btool'' program automatically figures that out. It will then 'link' the relevant files together and copy them into the ''inkscape'' directory.

To do a quick rebuild, simply go to the directory that contains the source and do the following;

* Delete or rename the ''inkscape'' directory, which contains the previous fully built and linked version of Inkscape
* Now open a command window and run the following;
...> mingwenv
...> btool dist-all
* Ishmal's build tool should now rebuild the individual files that have changed, along with any extra 'dependencies' these might require. If you've only applied one new patch, it can be done in less than 5 minutes!

'''''Note:''''' It is best not to do a quick rebuild if you have changed the version of libraries in C:\DEVLIBS. This can cause problems, as the files in the ''build'' directory incorporate functions from these libraries, which can change significantly between library versions. You will need to rebuild from scratch (see below).

'''''Rebuilding From Scratch'''''

To rebuild from scratch, you need to clean out any build files. First of all, if you want to keep the previously built version, rename the ''inkscape'' directory. Now open a command window and run the following;
...> mingwenv
...> btool clean
...> btool dist-all

==== Dealing With Build Errors ====
Feel free to add any questions or answers you have in here;

'''Q''' - My firewall software (Comodo's Defense+ component or similar) stopped the process continuing to the next step in the build, because I wasn't there to permit an action and it timed out. What can I do?

'''A1''' - The best thing is to disable stuff like Defense+ (put it in learning mode works) because it will stop any process that is not approved, and building makes new files which can't be approved before they're built. Disabling Comodo's Defense+ does not disable your firewall, either inbound or outbound, but just the part that scans every application for suspicious operations. Other firewalls etc may vary.

'''A2''' - If that doesn't suit, often you can simply run btool again and wait for Defense+ (or similar) to ask for approval for the process, and it will then continue as normal with the build. But remember that approving all the processes involved in the build process once doesn't mean they will all slip through next time.

'''A3''' - This is the more complex way to continue, but may help if you have problems with A2. If you know the stage the process was meant to be up to (look at the output in the command windows and compare to the stages in the ''build.xml'' file), you can start again from there.

You may see something like this in the command window;
=============================
## Target : link : link objects and library to create executable
---- task : rc
============ cmd ============
windres -o build/inkres.o --include-dir=src src/inkscape.rc
=============================
---- task : link
This will likely be followed by an error message. This means you were at the ''link'' stage

Now simply type;
...>btool ''stage''
Or in this case
...>btool link
And the build will continue from there.

After this, you will probably have to step through the remaining stages manually, one by one. The stages can include (see build.xml, where each stage is labelled 'target name="''target''"') ''init'', ''touchabout'', ''compile'', ''java'', ''lib'', ''i18n'', ''link'', ''linkinkview'', ''dist'', ''dist-all'', ''clean''.

'''Q''' - How do I rebuild just one ''file.o'' file? For instance if one particular file has gone wrong, or I want to try patching just one part of the code.

'''A''' - To find the right command for building any particular file in Inkscape, just look in the compile.lst after you have used btool once. Search for the name of the particular file (eg: print.cpp) and you will find the command used to compile it. You'll need to paste this into a text file, remove any carriage reurns and then paste that onto the command line.

'''Q''' - After I patched a file, I left a backup of the old file in the same directory called Copy of{filename}.cpp. The compiler complains about this file when building and stops.

'''A''' - Do not leave anything with a suffix .cpp in the source directories, apart from the original (or patched) source files. The build tool will try to compile everything ending in .cpp and will complain. If you backup an old file in the same directory before patching, call it {filename}.cpp.old or similar.

'''Q''' - I think I followed the instruction above. What could have caused the compiling error like this for src/extension/internal/pdfinput/pdf-parser.cpp?

src/extension/internal/pdfinput/pdf-parser.cpp:2248: error: no matching function for call to 'GfxFont::getNextChar(char*&, int&, CharCode*, Unicode [8], int, int*, double*, double*, double*, double*)'

Same error for line 2297 as well.

==== For more information ====
There is some old information on building Inkscape with either Mingw on Windows, or a cross-compiler on Linux, at http://inkscape.modevia.com/win32_inkscape_org/win32buildnotes.html

=== Create An Installation Package For Win32 ===

To create the setup package you need the NSIS installer on your PC. Get that from http://nsis.sf.net .
You have successfully built Inkscape and everything is in the ...\Inkscape\Inkscape\ directory.
Open the ...\Inkscape\packaging\win32\inkscape.nsi using the NSIS program and compile the package. Sooo easy :-)

==== A Note from Jon about UNICODE on Win32 ====

Actually, Microsoft themselves never use _UNICODE, nor it's 'evil' friends TCHAR and _T.
If it is used, it results in a binary that can not be run on Windows 95/98[[/ME]]. It is more of a "Windows NT only" define.

Microsoft applications like MS Office have been pure 16-bit Unicode internally for years now. Also remember that BSTRs in Win32 are required to have 16-bit Unicode data. So for any COM access on a Win32 box running Win9x[[/ME]] 'multibyte' or '8-bit' COM calls convert all ANSI data to Unicode once you pass things in. To avoid this, Microsoft just keeps data 16-bit Unicode and then translates to local ANSI codepage only when data needs to be passed directly to a Win32 call.

To help developers, Microsoft finally made public their API they had been using. It's [http://www.microsoft.com/globaldev/handson/dev/mslu_announce.mspx "The Microsoft Layer for Unicode"].

Although that simplifies things, it's not required. I've done Win32 programs that are 16-bit Unicode and run on Windows 95/98[[/ME]] with no problems years before they released that.

Soo.... _UNICODE can't be used as it makes your binary unusable on Win9x[[/ME]]. Then it turns out that TCHAR and _T can't be used either. (Oh, and MS can't really use them, since Office does run on Win9x[[/ME]]). So just explicitly use some 16-bit datatype for chars. Microsoft is misleading in their documentation when they state that wchar_t is 16-bit. Most other platforms (including Mac OS, Linux, Solaris, BSD, etc) follow the language standard's recommendation and make it 32-bit. So it is best to avoid wchar_t for any real cross-platform code.

So, some general guidelines are:
* Never define _UNICODE
* Don't use _T
* Don't use TCHAR
* Don't use wchar_t
* Use some explicit 16-bit type for characters/strings
** [http://www.icu-project.org/ International Components for Unicode (ICU)] does this

So then it's a simple matter of converting data from the standard UTF-8 GTK+ data to UTF-16 data before passing to Win32-land.

The result? A single binary that executes properly on both [[Win9X/ME]] and [[WinNT/2K/XP]], including full and proper font and filename support.

And, as I've mentioned before, I've actually achieved this for a few different shipping products and projects.

-- [[JonCruz|Jon C]]

=== SVN and Windows ===

If you want to access Inkscapes' subversion repository on SourceForge from Windows, I'd heartily recommend [[TortoiseSVN]].
It has the SSH stuff built into it so you don't have to mess about with putty, and
it integrates right into Explorer, so SVN becomes just an extension of the right-click file commands.
get it from http://tortoisesvn.net/

John

PerformanceMeasures

2009-09-30T10:40:44Z

TheAdib:

[[Category:Developer Documentation]]

== Performance Measures ==

=== build times ===

==== build times for Inkscape-0.47pre3.tar.gz ====
* my machine: Laptop DELL latitude D520 - E5500 Dualcore@1.6GHz 3329 bogomips 2GBRAM
** Linux Ubuntu9.04: "time make -j2" '''real 22m38 user36m21 sys 2m57'''
** Windows XP: "g++ buildtool.cpp -O2 -g0 -mtune=prescott" -o btool" "btool clean" "btool" '''46m57'''

PerformanceMeasures

2009-09-30T10:39:27Z

TheAdib:

[[Category:Developer]]

== Performance Measures ==

=== build times ===

==== build times for Inkscape-0.47pre3.tar.gz ====
* my machine: Laptop DELL latitude D520 - E5500 Dualcore@1.6GHz 3329 bogomips 2GBRAM
** Linux Ubuntu9.04: "time make -j2" '''real 22m38 user36m21 sys 2m57'''
** Windows XP: "g++ buildtool.cpp -O2 -g0 -mtune=prescott" -o btool" "btool clean" "btool" '''46m57'''

PerformanceMeasures

2009-09-30T10:37:44Z

TheAdib:

== Performance Measures ==

=== build times ===

==== build times for Inkscape-0.47pre3.tar.gz ====
* my machine: Laptop DELL latitude D520 - E5500 Dualcore@1.6GHz 3329 bogomips 2GBRAM
** Linux Ubuntu9.04: "time make -j2" '''real 22m38 user36m21 sys 2m57'''
** Windows XP: "g++ buildtool.cpp -O2 -g0 -mtune=prescott" -o btool" "btool clean" "btool" '''46m57'''

PerformanceMeasures

2009-09-30T10:20:18Z

TheAdib:

== Performance Measures ==

=== build times ===

==== build times for Inkscape-0.47pre3.tar.gz ====
* my machine: Laptop DELL latitude D520 - E5500 Dualcore@1.6GHz 3329 bogomips 2GBRAM
** Linux Ubuntu9.04: "time make -j2" '''real 22m38 user36m21 sys 2m57'''
** Windows: "g++ buildtool.cpp -O2 -g0 -mtune=prescott" -o btool" "btool clean" "btool" '''46m57'''

PerformanceMeasures

2009-09-30T09:29:51Z

TheAdib:

PerformanceMeasures

2009-09-30T09:29:09Z

TheAdib:

PerformanceMeasures

2009-09-30T09:25:00Z

TheAdib: