https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&user=Mahfiaz&feedformat=atomInkscape Wiki - User contributions [en]2024-03-29T09:40:05ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=47494CompilingUbuntu2009-02-23T17:21:41Z<p>Mahfiaz: /* Hardy and Intrepid */</p>
<hr />
<div>== Hardy, Intrepid and Jaunty ==<br />
=== Consider using stable (recommended for production) ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages (recommended) ===<br />
For Ubuntu there are nightly builds available. <br />
<br />
Get your appropriate repository lines from launchpad (read about [https://help.ubuntu.com/community/Repositories/Ubuntu adding repositories]):<br />
<br />
https://launchpad.net/~inkscape-nightly/+archive/ppa<br />
<br />
<br />
Run following command to update the repository information and install inkscape:<br />
<pre> sudo apt-get update<br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev libaspell-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have pdf support you need to install poppler:<br />
<br />
<pre><br />
sudo apt-get install libpoppler-dev libpoppler-glib-dev<br />
</pre><br />
<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
If you used some --prefix=/... other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.<br />
If the the location prefix was /usr, then "sudo make install" is not recommended, as debian package manager would know nothing about new package. The better alternative is using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=47484CompilingUbuntu2009-02-23T17:20:27Z<p>Mahfiaz: /* Using prebuilt packages */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages (recommended) ===<br />
For Ubuntu there are nightly builds available. <br />
<br />
Get your appropriate repository lines from launchpad (read about [https://help.ubuntu.com/community/Repositories/Ubuntu adding repositories]):<br />
<br />
https://launchpad.net/~inkscape-nightly/+archive/ppa<br />
<br />
<br />
Run following command to update the repository information and install inkscape:<br />
<pre> sudo apt-get update<br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev libaspell-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have pdf support you need to install poppler:<br />
<br />
<pre><br />
sudo apt-get install libpoppler-dev libpoppler-glib-dev<br />
</pre><br />
<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
If you used some --prefix=/... other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.<br />
If the the location prefix was /usr, then "sudo make install" is not recommended, as debian package manager would know nothing about new package. The better alternative is using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=41694CompilingUbuntu2009-01-05T22:41:53Z<p>Mahfiaz: /* Using prebuilt packages */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following line to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/towolf/ubuntu intrepid main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have pdf support you need to install poppler:<br />
<br />
<pre><br />
sudo apt-get install libpoppler-dev libpoppler-glib-dev<br />
</pre><br />
<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
If you used some --prefix=/... other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.<br />
If the the location prefix was /usr, then "sudo make install" is not recommended, as debian package manager would know nothing about new package. The better alternative is using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Installing_Inkscape&diff=40574Installing Inkscape2008-12-15T22:58:55Z<p>Mahfiaz: /* Unstable development version */ added titles</p>
<hr />
<div>== Installing on a Mac ==<br />
<br />
There are two steps needed to install on a Mac.<br />
<br />
<br />
'''1. Getting The Right Inkscape Installer:'''<br />
<br />
You need to download the right installation file from [http://www.inkscape.org/download/ here]. Note that this page has a separate version for Panther (10.3.9 only), and Tiger (10.4.x) and above. The Panther version is PPC only, while the Tiger version is ''Universal Binary'', meaning it installs on either older PPC or newer Intel Macs. The Tiger version will also work on Leopard (10.5.x)<br />
<br />
Once you have the Inkscape installation package, double click on it and it will open a windows with an Inkscape icon on one side, and a shortcut to the Applications folder on the other side. You need to drag the Inkscape icon across and drop in on the Applications folder. This will copy the file to the Application folder.<br />
<br />
To make a shortcut on your Dock, open the Applications folder, and drag the Inkscape icon to the place you want it on the dock.<br />
<br />
<br />
<br />
'''2. Getting The Right X11 Installer:'''<br />
<br />
To run Inkscape, you will also need to install X11. This is an environment that provides Unix like X-Window support for applications, including Inkscape (For more about X11 see [http://en.wikipedia.org/wiki/X11 here]). A native Mac OSX version that doesn't need X11 will be available sometime in the future (see [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here] or [http://jo.irisson.free.fr/?p=34 here] or [http://jo.irisson.free.fr/?p=62 here] for a sneak peek). But for now you need to do one of the following, depending on your OSX version.<br />
<br />
<br />
'''''For Panther (10.3.x):'''''<br />
<br />
You can download a suitable version of X11 from [http://www.apple.com/downloads/macosx/apple/macosx_updates/x11formacosx.html Apple] or mirrored [http://inkscape.modevia.com/macosx-snap/X11User_Panther.dmg here].<br />
<br />
<br />
'''''For Tiger (10.4.x):'''''<br />
<br />
You can install X11 from your original Install Disc 1. Scroll down the Finder window which opens when the DVD is inserted; double clic "Optional Installs"; go through the license agreement and destination selection; on the "Custom install" page select Applications -> X11 and deselect everything else; hit Install. To see what this looks like, go [http://overstimulate.com/articles/2005/11/04/installing-x11-on-os-x-10-4-tiger here]).<br />
<br />
Alternately, you can download a version for PPC [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_PPC.dmg here], or Intel [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_Intel.dmg here]. These files are able to be freely re-distributed because X11 is open source.<br />
<br />
<br />
'''Notes:'''<br />
*Once installed, you should also update your X11 to version 1.1.2 [http://www.apple.com/support/downloads/x11update2006113.html here]. This requires the earlier version, so you cannot just install the update.<br />
*A heavily improved version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] is expected to be available for Tiger some time in 2008. This will bring X11 on Tiger (10.4.x) into line with Leopard (10.5.x). See [http://trac.macosforge.org/projects/xquartz/roadmap here] for a roadmap of that project.<br />
<br />
<br />
'''''For Leopard (10.5.x):'''''<br />
<br />
Leopard officially ships with a version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] pre-installed, however the preinstalled version has some problems. Starting from January 2008, the XQuartz community released several updates to the XQuartz package in Mac OS X 10.5.x on [http://trac.macosforge.org/projects/xquartz Mac OS Forge]. These releases significantly improve X11 on the version of XQuartz found in the original Leopard release.<br />
<br />
On February 11 2008, Apple released an official XQuartz update in the [http://www.apple.com/support/downloads/macosx1052comboupdate.html Mac OS X 10.5.2 update]. This update addresses [http://docs.info.apple.com/article.html?artnum=307430 two security issues], although it is still somewhat behind the current XQuartz releases, upon which the official update is based. The [http://trac.macosforge.org/projects/xquartz XQuartz site] notes that "''10.5.2's version of X11 is somewhere between the 2.1.1 and 2.1.2 packages released through this site''". It also warns that "''Installing versions prior to X11 2.1.2 onto OS-X 10.5.2 may work but is not supported.''"<br />
<br />
XQuartz 2.2.1 was released on May 1 2008. This version requires OS X 10.5.0, however if you install the 10.5.2 update (or other updates) after XQuartz, you will probably need to reinstall XQuartz.<br />
<br />
For optimal performance and security, it is always best to install the latest Mac OS X updates, and then install the latest XQuartz over the top. This is what XQuartz is designed to do.<br />
<br />
'''Notes:'''<br />
*Because of changes to launchd, you will need to logout and re-login after installing XQuartz.<br />
*For the keen, pre-release candidates and recent deprecated versions of XQuartz are available [http://xquartz.macosforge.org/downloads/ here]. Information on a given release or release candidate is normally available at http://trac.macosforge.org/projects/xquartz/wiki/X112.2.x (change x to suit)<br />
*The XQuartz release roadmap is available [http://trac.macosforge.org/projects/xquartz/roadmap here].<br />
*For more technical information about X11 on Mac, a good place to go is http://homepage.mac.com/sao1/X11/index.html<br />
<br />
'''Problems After Installation'''<br />
<br />
''''' On Leopard (10.5) with XQuartz 2.2.1:'''''<br />
<br />
Some users report problems loading Inkscape 0.46-2 with XQuartz 2.2.1. - [https://bugs.launchpad.net/inkscape/+bug/226355 see here]. This problem occurs because XQuartz 2.2.1 has changed fontconfig.<br />
<br />
There are two possible fixes;<br />
<br />
1. Michael Whybrow, the packager of Inkscape for Mac suggests this;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type the following<br />
mkdir ~/.fontconfig<br />
b. Rerun Inkscape.app<br />
<br />
<br />
2. Another solution originally posted [https://answers.launchpad.net/inkscape/+question/28776 here] suggests editing an Inkscape configuration file;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type<br />
nano /Applications/Inkscape.app/Contents/Resources/script<br />
b. Press CTRL+V (scrolls down a page)<br />
<br />
c. Change the code (use the arrows keys to get to the right part) from:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig || exit 12<br />
"""<br />
<br />
to:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig<br />
"""<br />
d. Save changes by pressing CTRL+O and then ENTER to confirm<br />
<br />
e. Run Inkscape and wait for first-time caching<br />
<br />
Also it seems that having the "''authentificate connexion''" option checked in Preferences -> Securtity tab does interfere with Inkscape launch. Uncheck it if Inkscape doesn't launch.<br />
<br />
'''''I've installed X11 on OS X but Inkscape keeps asking for it'''''<br />
<br />
On Panther (10.3), you may need to uninstall/reinstall or upgrade X11. Use [http://www.osxgnu.org/software/pkgdetail.html?project_id=244 OSXPM] to uninstall X11 - Install OSXPM and select the Uninstall tab, scroll down to X11User, select it and hit Uninstall. Then you can install X11 properly.<br />
<br />
<br />
<br />
== Installing on Unix like systems ==<br />
<br />
=== Using Precompiled Packages (For Normal Users) ===<br />
<br />
==== Ubuntu Linux ====<br />
Probably the easiest way to install on Ubuntu is to use the apt command. <br />
<br />
Open a terminal and type;<br />
sudo apt-get update (enter)<br />
sudo apt-get install inkscape (enter)<br />
<br />
==== Ubuntu Linux Development Versions ====<br />
<br />
A few people have made builds of the development version of Inkscape 0.46 as it approaches release.<br />
<br />
<br />
Bryce Harrington has made available some i386 builds of the early January 2008 version for ''Gutsy'' (7.10) and ''Hardy'' (8.04 - currently in development). See the relevant post on the [http://www.nabble.com/Inkscape-0.46%7Esvn-Ubuntu-.deb-snapshot-td14645864.html Inksape-user email list]. This seems to be a one-off snapshot.<br />
<br />
<br />
NJH is offering nightly i386 and AMD64 builds for Gutsy and Edgy, along with supporting libraries like libcairo and libpixman. You can go to <br />
[http://ubuntu.cafuego.net/ http://ubuntu.cafuego.net] and select the link for the particular version of Ubuntu you're using. On the next page, select Inkscape, or Cairo etc, then follow the instructions on the following page.<br />
<br />
<br />
'''Note:''' Development versions offer some nice new features, but can be somewhat unstable, so save often. Inexperienced users will also quite possibly have problems installing them.<br />
<br />
==== Slackware Linux ====<br />
Pbhj says:<br />
<br />
I used the [http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=99112&release_id=426990 precompiled rpm] provided by Inkscape for the 0.44 release as my gcc wouldn't compile it. All you need to then do is run rpm2tgz at the command line on the package, eg " rpm2tgz inkscape-0.44-0.i686.rpm" and then install with "installpkg inkscape-0.44-0.i686.tgz".<br />
<br />
--[[User:Pbhj|Pbhj]] 13:29, 1 July 2006 (PDT)<br />
<br />
=== Compiling Your Own (For The Techies) ===<br />
<br />
<br />
NOTE: this isn't finished. I currently have two screwed up systems from fooling with bleeding edge GTK+ stuff, I don't know how that happened. !! :) I'll get to the end over the next few days tho. Setting up a more stable home network atm.<br />
-- <br />
Tsingi<br />
<br />
<br />
This was written building an InkScape snapshot on a new RedHat Linux installation. If you find that it doesn't answer your needs exactly, please update this file when you solve your particular problem.<br />
<br />
<br />
'''Installing libraries'''<br />
<br />
If you are running a debian based system, and have something like synaptic that lists recent enough versions of the libraries below, use that. If you want the latest libs, which you may need, especially if you are installing a snapshot or building from svn, you will want to download sources. Generally you will get a ''foo.tar.bz2'' or ''foo.tar.gz'' or ''foo.tgz'' file that you will need to unpack and build.<br />
<br />
''bz2'' files are the smallest. Uncompress them first by typing ''bunzip2 foo.tar.gz'' then unpack the remaining tar file by typing ''tar -xvf foo.tar''<br />
<br />
''foo.tar.gz'' files and ''foo.tgz'' files can be extracted in one operation by typing ''tar -xvzf foo.tar.gz'' <br />
<br />
Change to the directory that you just created ''foo''. type ''./configure'' then ''make'' then, as root, ''make install''<br />
<br />
Sometimes that is all you will need to do.<br />
<br />
Sometimes you will run into dependancy errors because you need a library you haven't installed yet. If you try installing inkscape without some of these dependancies, you will get a list of what you need. hopefully the instructions below will help you solve these dependancies.<br />
<br />
<br />
'''Running ldconfig'''<br />
<br />
after installing libs, (as root) you need to run ''ldconfig'' so that the linker can find the libraries that you have just installed. If you aren't logged in as root (i.e. if you became root by typing su) you may not have the /sbin/ directory in your path. so if ''ldconfig'' isn't working for you try typing ''/sbin/ldconfig''<br />
<br />
<br />
'''pkg-config'''<br />
<br />
''pkg-config'' is a utility that lists dependancies for libraries that sets up flags and paths for compiling. When it's working right it's wonderful. Getting it to work right is a pain in the ass if you don't know how. It's amazing how silent an IRC channel will get when you mention it.<br />
<br />
''pkg-config'' references pc files that applications install to give information about them. These are called metadata files, metadata means data about data. For a list of libraries that pkg-config sees, type ''pkg-config --list-all'' Having done that and looking at a list of pc files on my system (using ''find /usr -name "*.pc" > find.pc'', then browsing find.pc) I see that I also have a directory called ''/usr/lib64/pkgconfig/'' I might as well get that in there while I'm at it since none of those libs show up in a listing either and that's where most of them are.<br />
<br />
Depending on what shell you use, there are different ways of doing this. I'm adding a couple lines to my /etc/profile file:<br />
<br />
''PKG_CONFIG_PATH=/usr/lib/pkgconfig/:/usr/share/pkgconfig/:/usr/lib64/pkgconfig/:/usr/local/lib/pkgconfig/''<br />
<br />
''export PKG_CONFIG_PATH''<br />
<br />
Note that I have a new 64 bit system, which is why I'm going through all this. You probably won't have a ''/usr/lib64/pkgconfig/'' unless you do too, so don't just copy what I did. Also note that on a Windows system PATH type environment variables use semi-colons ";" for delimiters as opposed to colons ":"<br />
<br />
Using bash, to immediately source the file in the shell you are using, type ''. /etc/profile'. This won't test to see if the path gets put into your environment when open a shell though, so maybe a better thing to do is close your terminals and open new ones to see that it is actually set automagically.<br />
<br />
Ahh, I can now configure glibmm. The hair on the back of my neck is laying flat again, I think I'll have a coffee. :)<br />
<br />
<br />
<br />
'''libgc'''<br />
<br />
download and install the latest version of libgc[[http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/]]<br />
<br />
libgc installs in /usr/local/lib by default. If you have installed it and it is still not linking, you may not have that in your library path. There is a LD_LIBRARY_PATH environment variable, or alternatively you can make sure that /usr/local/lib is listed in the file /etc/ls.so.conf<br />
<br />
<br />
<br />
'''libsig++'''<br />
<br />
download and install libsig++ [http://libsigc.sourceforge.net/stable.shtml]<br />
<br />
this should be fairly straightforward.<br />
<br />
<br />
<br />
'''glibmm''' <br />
<br />
This is where, if you haven't wrestled with pkg-config on your system you start scratching your head. Because when you run configure on glibmm you may an error like this <br />
<br />
''checking for GLIBMM... configure: error: Package requirements (sigc++-2.0 >= 2.0.0 glib-2.0 >= 2.8.0 gobject-2.0 >= 2.8.0 gmodule-2.0 >= 2.8.0) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you<br />
installed software in a non-standard prefix.''<br />
<br />
''Alternatively you may set the GLIBMM_CFLAGS and GLIBMM_LIBS environment variables to avoid the need to call pkg-config. See the pkg-config man page for<br />
more details.''<br />
<br />
It seems that most packages install in a non standard prefix, in direct defiance of everything we have been led to believe regarding the concept of standard, so you may have to deal with this. See the note on ''pkg-config'' above.<br />
<br />
<br />
<br />
''gtkmm'' [http://www.gtkmm.org/]<br />
<br />
----<br />
(Ben) Tsingi, you are writing in the 'User Documentation' section. Most of this material is only appropriate for Developers and some would be better on the Mailing List. You will probably find that when you have finished, this page will be edited and pruned back. FWIW, I was expecting to find information about 'apt-get' (Debian) 'emerge' (Gentoo) and AutoPackage (the others).<br />
<br />
[[Category:User Documentation]]<br />
<br />
<br />
== Installing on a Windows system ==<br />
=== Stable version ===<br />
You can find the installer from [http://www.inkscape.org/download/ download page]. Installing should be easy next-next-finish.<br />
=== Unstable development version===<br />
First be warned. Unstable and development means you likely will encounter crashes, usability problems, sometimes lost data. Ctrl+S will become your friend. If you cannot take the risk, please use the stable version instead.<br />
<br />
You are still reading so you are the brave one and want the bleeding edge.<br />
==== 1. Download the latest build ====<br />
On [http://www.inkscape.org/download/ download page] there is a section named "Development versions". Find Mirrored win32 Builds link. This points you to inkscape.modevia.com server. There is information about builds and naming conventions on top of page. Down the page there are links to files. Get the .7z file with latest date on it.<br />
===== Exremely small build =====<br />
If the build is significantly smaller than previous ones, the build most likely is broken and you should get the latest one which is of normal size (currently over 40MB and growing).<br />
==== 2. Extract the .7z archive ====<br />
Extract the archive using [http://www.7-zip.org/ 7zip unpacker]. You will get a directory which contains several files including inkscape.exe<br />
==== 3. Run inkscape ====<br />
Run the inkscape.exe file by double clicking it. That's it. <br />
You can also drag files to inkscape.exe to have these opened.<br />
<br />
Don't forget reporting bugs, encouraging developers or fixing bugs yourself.<br />
<br />
==== Multiple versions for testing ====<br />
For testing purposes it is good to see where some problem first appeared. For this reason you could hold as many parallel versions of inkscape as your disk allows.</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Installing_Inkscape&diff=40564Installing Inkscape2008-12-15T22:37:18Z<p>Mahfiaz: readding Windows section</p>
<hr />
<div>== Installing on a Mac ==<br />
<br />
There are two steps needed to install on a Mac.<br />
<br />
<br />
'''1. Getting The Right Inkscape Installer:'''<br />
<br />
You need to download the right installation file from [http://www.inkscape.org/download/ here]. Note that this page has a separate version for Panther (10.3.9 only), and Tiger (10.4.x) and above. The Panther version is PPC only, while the Tiger version is ''Universal Binary'', meaning it installs on either older PPC or newer Intel Macs. The Tiger version will also work on Leopard (10.5.x)<br />
<br />
Once you have the Inkscape installation package, double click on it and it will open a windows with an Inkscape icon on one side, and a shortcut to the Applications folder on the other side. You need to drag the Inkscape icon across and drop in on the Applications folder. This will copy the file to the Application folder.<br />
<br />
To make a shortcut on your Dock, open the Applications folder, and drag the Inkscape icon to the place you want it on the dock.<br />
<br />
<br />
<br />
'''2. Getting The Right X11 Installer:'''<br />
<br />
To run Inkscape, you will also need to install X11. This is an environment that provides Unix like X-Window support for applications, including Inkscape (For more about X11 see [http://en.wikipedia.org/wiki/X11 here]). A native Mac OSX version that doesn't need X11 will be available sometime in the future (see [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here] or [http://jo.irisson.free.fr/?p=34 here] or [http://jo.irisson.free.fr/?p=62 here] for a sneak peek). But for now you need to do one of the following, depending on your OSX version.<br />
<br />
<br />
'''''For Panther (10.3.x):'''''<br />
<br />
You can download a suitable version of X11 from [http://www.apple.com/downloads/macosx/apple/macosx_updates/x11formacosx.html Apple] or mirrored [http://inkscape.modevia.com/macosx-snap/X11User_Panther.dmg here].<br />
<br />
<br />
'''''For Tiger (10.4.x):'''''<br />
<br />
You can install X11 from your original Install Disc 1. Scroll down the Finder window which opens when the DVD is inserted; double clic "Optional Installs"; go through the license agreement and destination selection; on the "Custom install" page select Applications -> X11 and deselect everything else; hit Install. To see what this looks like, go [http://overstimulate.com/articles/2005/11/04/installing-x11-on-os-x-10-4-tiger here]).<br />
<br />
Alternately, you can download a version for PPC [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_PPC.dmg here], or Intel [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_Intel.dmg here]. These files are able to be freely re-distributed because X11 is open source.<br />
<br />
<br />
'''Notes:'''<br />
*Once installed, you should also update your X11 to version 1.1.2 [http://www.apple.com/support/downloads/x11update2006113.html here]. This requires the earlier version, so you cannot just install the update.<br />
*A heavily improved version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] is expected to be available for Tiger some time in 2008. This will bring X11 on Tiger (10.4.x) into line with Leopard (10.5.x). See [http://trac.macosforge.org/projects/xquartz/roadmap here] for a roadmap of that project.<br />
<br />
<br />
'''''For Leopard (10.5.x):'''''<br />
<br />
Leopard officially ships with a version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] pre-installed, however the preinstalled version has some problems. Starting from January 2008, the XQuartz community released several updates to the XQuartz package in Mac OS X 10.5.x on [http://trac.macosforge.org/projects/xquartz Mac OS Forge]. These releases significantly improve X11 on the version of XQuartz found in the original Leopard release.<br />
<br />
On February 11 2008, Apple released an official XQuartz update in the [http://www.apple.com/support/downloads/macosx1052comboupdate.html Mac OS X 10.5.2 update]. This update addresses [http://docs.info.apple.com/article.html?artnum=307430 two security issues], although it is still somewhat behind the current XQuartz releases, upon which the official update is based. The [http://trac.macosforge.org/projects/xquartz XQuartz site] notes that "''10.5.2's version of X11 is somewhere between the 2.1.1 and 2.1.2 packages released through this site''". It also warns that "''Installing versions prior to X11 2.1.2 onto OS-X 10.5.2 may work but is not supported.''"<br />
<br />
XQuartz 2.2.1 was released on May 1 2008. This version requires OS X 10.5.0, however if you install the 10.5.2 update (or other updates) after XQuartz, you will probably need to reinstall XQuartz.<br />
<br />
For optimal performance and security, it is always best to install the latest Mac OS X updates, and then install the latest XQuartz over the top. This is what XQuartz is designed to do.<br />
<br />
'''Notes:'''<br />
*Because of changes to launchd, you will need to logout and re-login after installing XQuartz.<br />
*For the keen, pre-release candidates and recent deprecated versions of XQuartz are available [http://xquartz.macosforge.org/downloads/ here]. Information on a given release or release candidate is normally available at http://trac.macosforge.org/projects/xquartz/wiki/X112.2.x (change x to suit)<br />
*The XQuartz release roadmap is available [http://trac.macosforge.org/projects/xquartz/roadmap here].<br />
*For more technical information about X11 on Mac, a good place to go is http://homepage.mac.com/sao1/X11/index.html<br />
<br />
'''Problems After Installation'''<br />
<br />
''''' On Leopard (10.5) with XQuartz 2.2.1:'''''<br />
<br />
Some users report problems loading Inkscape 0.46-2 with XQuartz 2.2.1. - [https://bugs.launchpad.net/inkscape/+bug/226355 see here]. This problem occurs because XQuartz 2.2.1 has changed fontconfig.<br />
<br />
There are two possible fixes;<br />
<br />
1. Michael Whybrow, the packager of Inkscape for Mac suggests this;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type the following<br />
mkdir ~/.fontconfig<br />
b. Rerun Inkscape.app<br />
<br />
<br />
2. Another solution originally posted [https://answers.launchpad.net/inkscape/+question/28776 here] suggests editing an Inkscape configuration file;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type<br />
nano /Applications/Inkscape.app/Contents/Resources/script<br />
b. Press CTRL+V (scrolls down a page)<br />
<br />
c. Change the code (use the arrows keys to get to the right part) from:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig || exit 12<br />
"""<br />
<br />
to:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig<br />
"""<br />
d. Save changes by pressing CTRL+O and then ENTER to confirm<br />
<br />
e. Run Inkscape and wait for first-time caching<br />
<br />
Also it seems that having the "''authentificate connexion''" option checked in Preferences -> Securtity tab does interfere with Inkscape launch. Uncheck it if Inkscape doesn't launch.<br />
<br />
'''''I've installed X11 on OS X but Inkscape keeps asking for it'''''<br />
<br />
On Panther (10.3), you may need to uninstall/reinstall or upgrade X11. Use [http://www.osxgnu.org/software/pkgdetail.html?project_id=244 OSXPM] to uninstall X11 - Install OSXPM and select the Uninstall tab, scroll down to X11User, select it and hit Uninstall. Then you can install X11 properly.<br />
<br />
<br />
<br />
== Installing on Unix like systems ==<br />
<br />
=== Using Precompiled Packages (For Normal Users) ===<br />
<br />
==== Ubuntu Linux ====<br />
Probably the easiest way to install on Ubuntu is to use the apt command. <br />
<br />
Open a terminal and type;<br />
sudo apt-get update (enter)<br />
sudo apt-get install inkscape (enter)<br />
<br />
==== Ubuntu Linux Development Versions ====<br />
<br />
A few people have made builds of the development version of Inkscape 0.46 as it approaches release.<br />
<br />
<br />
Bryce Harrington has made available some i386 builds of the early January 2008 version for ''Gutsy'' (7.10) and ''Hardy'' (8.04 - currently in development). See the relevant post on the [http://www.nabble.com/Inkscape-0.46%7Esvn-Ubuntu-.deb-snapshot-td14645864.html Inksape-user email list]. This seems to be a one-off snapshot.<br />
<br />
<br />
NJH is offering nightly i386 and AMD64 builds for Gutsy and Edgy, along with supporting libraries like libcairo and libpixman. You can go to <br />
[http://ubuntu.cafuego.net/ http://ubuntu.cafuego.net] and select the link for the particular version of Ubuntu you're using. On the next page, select Inkscape, or Cairo etc, then follow the instructions on the following page.<br />
<br />
<br />
'''Note:''' Development versions offer some nice new features, but can be somewhat unstable, so save often. Inexperienced users will also quite possibly have problems installing them.<br />
<br />
==== Slackware Linux ====<br />
Pbhj says:<br />
<br />
I used the [http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=99112&release_id=426990 precompiled rpm] provided by Inkscape for the 0.44 release as my gcc wouldn't compile it. All you need to then do is run rpm2tgz at the command line on the package, eg " rpm2tgz inkscape-0.44-0.i686.rpm" and then install with "installpkg inkscape-0.44-0.i686.tgz".<br />
<br />
--[[User:Pbhj|Pbhj]] 13:29, 1 July 2006 (PDT)<br />
<br />
=== Compiling Your Own (For The Techies) ===<br />
<br />
<br />
NOTE: this isn't finished. I currently have two screwed up systems from fooling with bleeding edge GTK+ stuff, I don't know how that happened. !! :) I'll get to the end over the next few days tho. Setting up a more stable home network atm.<br />
-- <br />
Tsingi<br />
<br />
<br />
This was written building an InkScape snapshot on a new RedHat Linux installation. If you find that it doesn't answer your needs exactly, please update this file when you solve your particular problem.<br />
<br />
<br />
'''Installing libraries'''<br />
<br />
If you are running a debian based system, and have something like synaptic that lists recent enough versions of the libraries below, use that. If you want the latest libs, which you may need, especially if you are installing a snapshot or building from svn, you will want to download sources. Generally you will get a ''foo.tar.bz2'' or ''foo.tar.gz'' or ''foo.tgz'' file that you will need to unpack and build.<br />
<br />
''bz2'' files are the smallest. Uncompress them first by typing ''bunzip2 foo.tar.gz'' then unpack the remaining tar file by typing ''tar -xvf foo.tar''<br />
<br />
''foo.tar.gz'' files and ''foo.tgz'' files can be extracted in one operation by typing ''tar -xvzf foo.tar.gz'' <br />
<br />
Change to the directory that you just created ''foo''. type ''./configure'' then ''make'' then, as root, ''make install''<br />
<br />
Sometimes that is all you will need to do.<br />
<br />
Sometimes you will run into dependancy errors because you need a library you haven't installed yet. If you try installing inkscape without some of these dependancies, you will get a list of what you need. hopefully the instructions below will help you solve these dependancies.<br />
<br />
<br />
'''Running ldconfig'''<br />
<br />
after installing libs, (as root) you need to run ''ldconfig'' so that the linker can find the libraries that you have just installed. If you aren't logged in as root (i.e. if you became root by typing su) you may not have the /sbin/ directory in your path. so if ''ldconfig'' isn't working for you try typing ''/sbin/ldconfig''<br />
<br />
<br />
'''pkg-config'''<br />
<br />
''pkg-config'' is a utility that lists dependancies for libraries that sets up flags and paths for compiling. When it's working right it's wonderful. Getting it to work right is a pain in the ass if you don't know how. It's amazing how silent an IRC channel will get when you mention it.<br />
<br />
''pkg-config'' references pc files that applications install to give information about them. These are called metadata files, metadata means data about data. For a list of libraries that pkg-config sees, type ''pkg-config --list-all'' Having done that and looking at a list of pc files on my system (using ''find /usr -name "*.pc" > find.pc'', then browsing find.pc) I see that I also have a directory called ''/usr/lib64/pkgconfig/'' I might as well get that in there while I'm at it since none of those libs show up in a listing either and that's where most of them are.<br />
<br />
Depending on what shell you use, there are different ways of doing this. I'm adding a couple lines to my /etc/profile file:<br />
<br />
''PKG_CONFIG_PATH=/usr/lib/pkgconfig/:/usr/share/pkgconfig/:/usr/lib64/pkgconfig/:/usr/local/lib/pkgconfig/''<br />
<br />
''export PKG_CONFIG_PATH''<br />
<br />
Note that I have a new 64 bit system, which is why I'm going through all this. You probably won't have a ''/usr/lib64/pkgconfig/'' unless you do too, so don't just copy what I did. Also note that on a Windows system PATH type environment variables use semi-colons ";" for delimiters as opposed to colons ":"<br />
<br />
Using bash, to immediately source the file in the shell you are using, type ''. /etc/profile'. This won't test to see if the path gets put into your environment when open a shell though, so maybe a better thing to do is close your terminals and open new ones to see that it is actually set automagically.<br />
<br />
Ahh, I can now configure glibmm. The hair on the back of my neck is laying flat again, I think I'll have a coffee. :)<br />
<br />
<br />
<br />
'''libgc'''<br />
<br />
download and install the latest version of libgc[[http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/]]<br />
<br />
libgc installs in /usr/local/lib by default. If you have installed it and it is still not linking, you may not have that in your library path. There is a LD_LIBRARY_PATH environment variable, or alternatively you can make sure that /usr/local/lib is listed in the file /etc/ls.so.conf<br />
<br />
<br />
<br />
'''libsig++'''<br />
<br />
download and install libsig++ [http://libsigc.sourceforge.net/stable.shtml]<br />
<br />
this should be fairly straightforward.<br />
<br />
<br />
<br />
'''glibmm''' <br />
<br />
This is where, if you haven't wrestled with pkg-config on your system you start scratching your head. Because when you run configure on glibmm you may an error like this <br />
<br />
''checking for GLIBMM... configure: error: Package requirements (sigc++-2.0 >= 2.0.0 glib-2.0 >= 2.8.0 gobject-2.0 >= 2.8.0 gmodule-2.0 >= 2.8.0) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you<br />
installed software in a non-standard prefix.''<br />
<br />
''Alternatively you may set the GLIBMM_CFLAGS and GLIBMM_LIBS environment variables to avoid the need to call pkg-config. See the pkg-config man page for<br />
more details.''<br />
<br />
It seems that most packages install in a non standard prefix, in direct defiance of everything we have been led to believe regarding the concept of standard, so you may have to deal with this. See the note on ''pkg-config'' above.<br />
<br />
<br />
<br />
''gtkmm'' [http://www.gtkmm.org/]<br />
<br />
----<br />
(Ben) Tsingi, you are writing in the 'User Documentation' section. Most of this material is only appropriate for Developers and some would be better on the Mailing List. You will probably find that when you have finished, this page will be edited and pruned back. FWIW, I was expecting to find information about 'apt-get' (Debian) 'emerge' (Gentoo) and AutoPackage (the others).<br />
<br />
[[Category:User Documentation]]<br />
<br />
<br />
== Installing on a Windows system ==<br />
=== Stable version ===<br />
You can find the installer from [http://www.inkscape.org/download/ download page]. Installing should be easy next-next-finish.<br />
=== Unstable development version===<br />
First be warned. Unstable and development means you likely will encounter crashes, usability problems, sometimes lost data. Ctrl+S will become your friend. If you cannot take the risk, please use the stable version instead.<br />
<br />
You are still reading so you are the brave one and want the bleeding edge.<br />
On [http://www.inkscape.org/download/ download page] there is a section named "Development versions". Find Mirrored win32 Builds link. This points you to inkscape.modevia.com server. There is information about builds and naming conventions. Get the .7z file with latest date on it. This can be extracted using [http://www.7-zip.org/ 7zip unpacker]. You will get directory which contains several files including inkscape.exe, run this by double clicking it. That's it. Don't forget reporting bugs, encouraging developers or fixing bugs yourself.<br />
==== Exremely small build ====<br />
If the build is significantly smaller than previous ones, the build most likely is broken and you should get the latest one which is of normal size (currently over 40MB and growing).<br />
==== Multiple versions ====<br />
For testing purposes it is good to see where some problem first appeared. For this reason you could hold as many parallel versions of inkscape as your disk allows.</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Installing_Inkscape&diff=40554Installing Inkscape2008-12-15T22:36:50Z<p>Mahfiaz: replacing</p>
<hr />
<div>== Installing on a Mac ==<br />
<br />
There are two steps needed to install on a Mac.<br />
<br />
<br />
'''1. Getting The Right Inkscape Installer:'''<br />
<br />
You need to download the right installation file from [http://www.inkscape.org/download/ here]. Note that this page has a separate version for Panther (10.3.9 only), and Tiger (10.4.x) and above. The Panther version is PPC only, while the Tiger version is ''Universal Binary'', meaning it installs on either older PPC or newer Intel Macs. The Tiger version will also work on Leopard (10.5.x)<br />
<br />
Once you have the Inkscape installation package, double click on it and it will open a windows with an Inkscape icon on one side, and a shortcut to the Applications folder on the other side. You need to drag the Inkscape icon across and drop in on the Applications folder. This will copy the file to the Application folder.<br />
<br />
To make a shortcut on your Dock, open the Applications folder, and drag the Inkscape icon to the place you want it on the dock.<br />
<br />
<br />
<br />
'''2. Getting The Right X11 Installer:'''<br />
<br />
To run Inkscape, you will also need to install X11. This is an environment that provides Unix like X-Window support for applications, including Inkscape (For more about X11 see [http://en.wikipedia.org/wiki/X11 here]). A native Mac OSX version that doesn't need X11 will be available sometime in the future (see [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here] or [http://jo.irisson.free.fr/?p=34 here] or [http://jo.irisson.free.fr/?p=62 here] for a sneak peek). But for now you need to do one of the following, depending on your OSX version.<br />
<br />
<br />
'''''For Panther (10.3.x):'''''<br />
<br />
You can download a suitable version of X11 from [http://www.apple.com/downloads/macosx/apple/macosx_updates/x11formacosx.html Apple] or mirrored [http://inkscape.modevia.com/macosx-snap/X11User_Panther.dmg here].<br />
<br />
<br />
'''''For Tiger (10.4.x):'''''<br />
<br />
You can install X11 from your original Install Disc 1. Scroll down the Finder window which opens when the DVD is inserted; double clic "Optional Installs"; go through the license agreement and destination selection; on the "Custom install" page select Applications -> X11 and deselect everything else; hit Install. To see what this looks like, go [http://overstimulate.com/articles/2005/11/04/installing-x11-on-os-x-10-4-tiger here]).<br />
<br />
Alternately, you can download a version for PPC [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_PPC.dmg here], or Intel [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_Intel.dmg here]. These files are able to be freely re-distributed because X11 is open source.<br />
<br />
<br />
'''Notes:'''<br />
*Once installed, you should also update your X11 to version 1.1.2 [http://www.apple.com/support/downloads/x11update2006113.html here]. This requires the earlier version, so you cannot just install the update.<br />
*A heavily improved version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] is expected to be available for Tiger some time in 2008. This will bring X11 on Tiger (10.4.x) into line with Leopard (10.5.x). See [http://trac.macosforge.org/projects/xquartz/roadmap here] for a roadmap of that project.<br />
<br />
<br />
'''''For Leopard (10.5.x):'''''<br />
<br />
Leopard officially ships with a version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] pre-installed, however the preinstalled version has some problems. Starting from January 2008, the XQuartz community released several updates to the XQuartz package in Mac OS X 10.5.x on [http://trac.macosforge.org/projects/xquartz Mac OS Forge]. These releases significantly improve X11 on the version of XQuartz found in the original Leopard release.<br />
<br />
On February 11 2008, Apple released an official XQuartz update in the [http://www.apple.com/support/downloads/macosx1052comboupdate.html Mac OS X 10.5.2 update]. This update addresses [http://docs.info.apple.com/article.html?artnum=307430 two security issues], although it is still somewhat behind the current XQuartz releases, upon which the official update is based. The [http://trac.macosforge.org/projects/xquartz XQuartz site] notes that "''10.5.2's version of X11 is somewhere between the 2.1.1 and 2.1.2 packages released through this site''". It also warns that "''Installing versions prior to X11 2.1.2 onto OS-X 10.5.2 may work but is not supported.''"<br />
<br />
XQuartz 2.2.1 was released on May 1 2008. This version requires OS X 10.5.0, however if you install the 10.5.2 update (or other updates) after XQuartz, you will probably need to reinstall XQuartz.<br />
<br />
For optimal performance and security, it is always best to install the latest Mac OS X updates, and then install the latest XQuartz over the top. This is what XQuartz is designed to do.<br />
<br />
'''Notes:'''<br />
*Because of changes to launchd, you will need to logout and re-login after installing XQuartz.<br />
*For the keen, pre-release candidates and recent deprecated versions of XQuartz are available [http://xquartz.macosforge.org/downloads/ here]. Information on a given release or release candidate is normally available at http://trac.macosforge.org/projects/xquartz/wiki/X112.2.x (change x to suit)<br />
*The XQuartz release roadmap is available [http://trac.macosforge.org/projects/xquartz/roadmap here].<br />
*For more technical information about X11 on Mac, a good place to go is http://homepage.mac.com/sao1/X11/index.html<br />
<br />
'''Problems After Installation'''<br />
<br />
''''' On Leopard (10.5) with XQuartz 2.2.1:'''''<br />
<br />
Some users report problems loading Inkscape 0.46-2 with XQuartz 2.2.1. - [https://bugs.launchpad.net/inkscape/+bug/226355 see here]. This problem occurs because XQuartz 2.2.1 has changed fontconfig.<br />
<br />
There are two possible fixes;<br />
<br />
1. Michael Whybrow, the packager of Inkscape for Mac suggests this;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type the following<br />
mkdir ~/.fontconfig<br />
b. Rerun Inkscape.app<br />
<br />
<br />
2. Another solution originally posted [https://answers.launchpad.net/inkscape/+question/28776 here] suggests editing an Inkscape configuration file;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type<br />
nano /Applications/Inkscape.app/Contents/Resources/script<br />
b. Press CTRL+V (scrolls down a page)<br />
<br />
c. Change the code (use the arrows keys to get to the right part) from:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig || exit 12<br />
"""<br />
<br />
to:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig<br />
"""<br />
d. Save changes by pressing CTRL+O and then ENTER to confirm<br />
<br />
e. Run Inkscape and wait for first-time caching<br />
<br />
Also it seems that having the "''authentificate connexion''" option checked in Preferences -> Securtity tab does interfere with Inkscape launch. Uncheck it if Inkscape doesn't launch.<br />
<br />
'''''I've installed X11 on OS X but Inkscape keeps asking for it'''''<br />
<br />
On Panther (10.3), you may need to uninstall/reinstall or upgrade X11. Use [http://www.osxgnu.org/software/pkgdetail.html?project_id=244 OSXPM] to uninstall X11 - Install OSXPM and select the Uninstall tab, scroll down to X11User, select it and hit Uninstall. Then you can install X11 properly.<br />
<br />
<br />
<br />
== Installing on Unix like systems ==<br />
<br />
=== Using Precompiled Packages (For Normal Users) ===<br />
<br />
==== Ubuntu Linux ====<br />
Probably the easiest way to install on Ubuntu is to use the apt command. <br />
<br />
Open a terminal and type;<br />
sudo apt-get update (enter)<br />
sudo apt-get install inkscape (enter)<br />
<br />
==== Ubuntu Linux Development Versions ====<br />
<br />
A few people have made builds of the development version of Inkscape 0.46 as it approaches release.<br />
<br />
<br />
Bryce Harrington has made available some i386 builds of the early January 2008 version for ''Gutsy'' (7.10) and ''Hardy'' (8.04 - currently in development). See the relevant post on the [http://www.nabble.com/Inkscape-0.46%7Esvn-Ubuntu-.deb-snapshot-td14645864.html Inksape-user email list]. This seems to be a one-off snapshot.<br />
<br />
<br />
NJH is offering nightly i386 and AMD64 builds for Gutsy and Edgy, along with supporting libraries like libcairo and libpixman. You can go to <br />
[http://ubuntu.cafuego.net/ http://ubuntu.cafuego.net] and select the link for the particular version of Ubuntu you're using. On the next page, select Inkscape, or Cairo etc, then follow the instructions on the following page.<br />
<br />
<br />
'''Note:''' Development versions offer some nice new features, but can be somewhat unstable, so save often. Inexperienced users will also quite possibly have problems installing them.<br />
<br />
==== Slackware Linux ====<br />
Pbhj says:<br />
<br />
I used the [http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=99112&release_id=426990 precompiled rpm] provided by Inkscape for the 0.44 release as my gcc wouldn't compile it. All you need to then do is run rpm2tgz at the command line on the package, eg " rpm2tgz inkscape-0.44-0.i686.rpm" and then install with "installpkg inkscape-0.44-0.i686.tgz".<br />
<br />
--[[User:Pbhj|Pbhj]] 13:29, 1 July 2006 (PDT)<br />
<br />
=== Compiling Your Own (For The Techies) ===<br />
<br />
<br />
NOTE: this isn't finished. I currently have two screwed up systems from fooling with bleeding edge GTK+ stuff, I don't know how that happened. !! :) I'll get to the end over the next few days tho. Setting up a more stable home network atm.<br />
-- <br />
Tsingi<br />
<br />
<br />
This was written building an InkScape snapshot on a new RedHat Linux installation. If you find that it doesn't answer your needs exactly, please update this file when you solve your particular problem.<br />
<br />
<br />
'''Installing libraries'''<br />
<br />
If you are running a debian based system, and have something like synaptic that lists recent enough versions of the libraries below, use that. If you want the latest libs, which you may need, especially if you are installing a snapshot or building from svn, you will want to download sources. Generally you will get a ''foo.tar.bz2'' or ''foo.tar.gz'' or ''foo.tgz'' file that you will need to unpack and build.<br />
<br />
''bz2'' files are the smallest. Uncompress them first by typing ''bunzip2 foo.tar.gz'' then unpack the remaining tar file by typing ''tar -xvf foo.tar''<br />
<br />
''foo.tar.gz'' files and ''foo.tgz'' files can be extracted in one operation by typing ''tar -xvzf foo.tar.gz'' <br />
<br />
Change to the directory that you just created ''foo''. type ''./configure'' then ''make'' then, as root, ''make install''<br />
<br />
Sometimes that is all you will need to do.<br />
<br />
Sometimes you will run into dependancy errors because you need a library you haven't installed yet. If you try installing inkscape without some of these dependancies, you will get a list of what you need. hopefully the instructions below will help you solve these dependancies.<br />
<br />
<br />
'''Running ldconfig'''<br />
<br />
after installing libs, (as root) you need to run ''ldconfig'' so that the linker can find the libraries that you have just installed. If you aren't logged in as root (i.e. if you became root by typing su) you may not have the /sbin/ directory in your path. so if ''ldconfig'' isn't working for you try typing ''/sbin/ldconfig''<br />
<br />
<br />
'''pkg-config'''<br />
<br />
''pkg-config'' is a utility that lists dependancies for libraries that sets up flags and paths for compiling. When it's working right it's wonderful. Getting it to work right is a pain in the ass if you don't know how. It's amazing how silent an IRC channel will get when you mention it.<br />
<br />
''pkg-config'' references pc files that applications install to give information about them. These are called metadata files, metadata means data about data. For a list of libraries that pkg-config sees, type ''pkg-config --list-all'' Having done that and looking at a list of pc files on my system (using ''find /usr -name "*.pc" > find.pc'', then browsing find.pc) I see that I also have a directory called ''/usr/lib64/pkgconfig/'' I might as well get that in there while I'm at it since none of those libs show up in a listing either and that's where most of them are.<br />
<br />
Depending on what shell you use, there are different ways of doing this. I'm adding a couple lines to my /etc/profile file:<br />
<br />
''PKG_CONFIG_PATH=/usr/lib/pkgconfig/:/usr/share/pkgconfig/:/usr/lib64/pkgconfig/:/usr/local/lib/pkgconfig/''<br />
<br />
''export PKG_CONFIG_PATH''<br />
<br />
Note that I have a new 64 bit system, which is why I'm going through all this. You probably won't have a ''/usr/lib64/pkgconfig/'' unless you do too, so don't just copy what I did. Also note that on a Windows system PATH type environment variables use semi-colons ";" for delimiters as opposed to colons ":"<br />
<br />
Using bash, to immediately source the file in the shell you are using, type ''. /etc/profile'. This won't test to see if the path gets put into your environment when open a shell though, so maybe a better thing to do is close your terminals and open new ones to see that it is actually set automagically.<br />
<br />
Ahh, I can now configure glibmm. The hair on the back of my neck is laying flat again, I think I'll have a coffee. :)<br />
<br />
<br />
<br />
'''libgc'''<br />
<br />
download and install the latest version of libgc[[http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/]]<br />
<br />
libgc installs in /usr/local/lib by default. If you have installed it and it is still not linking, you may not have that in your library path. There is a LD_LIBRARY_PATH environment variable, or alternatively you can make sure that /usr/local/lib is listed in the file /etc/ls.so.conf<br />
<br />
<br />
<br />
'''libsig++'''<br />
<br />
download and install libsig++ [http://libsigc.sourceforge.net/stable.shtml]<br />
<br />
this should be fairly straightforward.<br />
<br />
<br />
<br />
'''glibmm''' <br />
<br />
This is where, if you haven't wrestled with pkg-config on your system you start scratching your head. Because when you run configure on glibmm you may an error like this <br />
<br />
''checking for GLIBMM... configure: error: Package requirements (sigc++-2.0 >= 2.0.0 glib-2.0 >= 2.8.0 gobject-2.0 >= 2.8.0 gmodule-2.0 >= 2.8.0) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you<br />
installed software in a non-standard prefix.''<br />
<br />
''Alternatively you may set the GLIBMM_CFLAGS and GLIBMM_LIBS environment variables to avoid the need to call pkg-config. See the pkg-config man page for<br />
more details.''<br />
<br />
It seems that most packages install in a non standard prefix, in direct defiance of everything we have been led to believe regarding the concept of standard, so you may have to deal with this. See the note on ''pkg-config'' above.<br />
<br />
<br />
<br />
''gtkmm'' [http://www.gtkmm.org/]<br />
<br />
----<br />
(Ben) Tsingi, you are writing in the 'User Documentation' section. Most of this material is only appropriate for Developers and some would be better on the Mailing List. You will probably find that when you have finished, this page will be edited and pruned back. FWIW, I was expecting to find information about 'apt-get' (Debian) 'emerge' (Gentoo) and AutoPackage (the others).<br />
<br />
[[Category:User Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Installing_Inkscape&diff=40544Installing Inkscape2008-12-15T22:36:09Z<p>Mahfiaz: Adding windows section</p>
<hr />
<div>== Installing on a Mac ==<br />
<br />
There are two steps needed to install on a Mac.<br />
<br />
<br />
'''1. Getting The Right Inkscape Installer:'''<br />
<br />
You need to download the right installation file from [http://www.inkscape.org/download/ here]. Note that this page has a separate version for Panther (10.3.9 only), and Tiger (10.4.x) and above. The Panther version is PPC only, while the Tiger version is ''Universal Binary'', meaning it installs on either older PPC or newer Intel Macs. The Tiger version will also work on Leopard (10.5.x)<br />
<br />
Once you have the Inkscape installation package, double click on it and it will open a windows with an Inkscape icon on one side, and a shortcut to the Applications folder on the other side. You need to drag the Inkscape icon across and drop in on the Applications folder. This will copy the file to the Application folder.<br />
<br />
To make a shortcut on your Dock, open the Applications folder, and drag the Inkscape icon to the place you want it on the dock.<br />
<br />
<br />
<br />
'''2. Getting The Right X11 Installer:'''<br />
<br />
To run Inkscape, you will also need to install X11. This is an environment that provides Unix like X-Window support for applications, including Inkscape (For more about X11 see [http://en.wikipedia.org/wiki/X11 here]). A native Mac OSX version that doesn't need X11 will be available sometime in the future (see [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here] or [http://jo.irisson.free.fr/?p=34 here] or [http://jo.irisson.free.fr/?p=62 here] for a sneak peek). But for now you need to do one of the following, depending on your OSX version.<br />
<br />
<br />
'''''For Panther (10.3.x):'''''<br />
<br />
You can download a suitable version of X11 from [http://www.apple.com/downloads/macosx/apple/macosx_updates/x11formacosx.html Apple] or mirrored [http://inkscape.modevia.com/macosx-snap/X11User_Panther.dmg here].<br />
<br />
<br />
'''''For Tiger (10.4.x):'''''<br />
<br />
You can install X11 from your original Install Disc 1. Scroll down the Finder window which opens when the DVD is inserted; double clic "Optional Installs"; go through the license agreement and destination selection; on the "Custom install" page select Applications -> X11 and deselect everything else; hit Install. To see what this looks like, go [http://overstimulate.com/articles/2005/11/04/installing-x11-on-os-x-10-4-tiger here]).<br />
<br />
Alternately, you can download a version for PPC [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_PPC.dmg here], or Intel [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_Intel.dmg here]. These files are able to be freely re-distributed because X11 is open source.<br />
<br />
<br />
'''Notes:'''<br />
*Once installed, you should also update your X11 to version 1.1.2 [http://www.apple.com/support/downloads/x11update2006113.html here]. This requires the earlier version, so you cannot just install the update.<br />
*A heavily improved version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] is expected to be available for Tiger some time in 2008. This will bring X11 on Tiger (10.4.x) into line with Leopard (10.5.x). See [http://trac.macosforge.org/projects/xquartz/roadmap here] for a roadmap of that project.<br />
<br />
<br />
'''''For Leopard (10.5.x):'''''<br />
<br />
Leopard officially ships with a version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] pre-installed, however the preinstalled version has some problems. Starting from January 2008, the XQuartz community released several updates to the XQuartz package in Mac OS X 10.5.x on [http://trac.macosforge.org/projects/xquartz Mac OS Forge]. These releases significantly improve X11 on the version of XQuartz found in the original Leopard release.<br />
<br />
On February 11 2008, Apple released an official XQuartz update in the [http://www.apple.com/support/downloads/macosx1052comboupdate.html Mac OS X 10.5.2 update]. This update addresses [http://docs.info.apple.com/article.html?artnum=307430 two security issues], although it is still somewhat behind the current XQuartz releases, upon which the official update is based. The [http://trac.macosforge.org/projects/xquartz XQuartz site] notes that "''10.5.2's version of X11 is somewhere between the 2.1.1 and 2.1.2 packages released through this site''". It also warns that "''Installing versions prior to X11 2.1.2 onto OS-X 10.5.2 may work but is not supported.''"<br />
<br />
XQuartz 2.2.1 was released on May 1 2008. This version requires OS X 10.5.0, however if you install the 10.5.2 update (or other updates) after XQuartz, you will probably need to reinstall XQuartz.<br />
<br />
For optimal performance and security, it is always best to install the latest Mac OS X updates, and then install the latest XQuartz over the top. This is what XQuartz is designed to do.<br />
<br />
'''Notes:'''<br />
*Because of changes to launchd, you will need to logout and re-login after installing XQuartz.<br />
*For the keen, pre-release candidates and recent deprecated versions of XQuartz are available [http://xquartz.macosforge.org/downloads/ here]. Information on a given release or release candidate is normally available at http://trac.macosforge.org/projects/xquartz/wiki/X112.2.x (change x to suit)<br />
*The XQuartz release roadmap is available [http://trac.macosforge.org/projects/xquartz/roadmap here].<br />
*For more technical information about X11 on Mac, a good place to go is http://homepage.mac.com/sao1/X11/index.html<br />
<br />
'''Problems After Installation'''<br />
<br />
''''' On Leopard (10.5) with XQuartz 2.2.1:'''''<br />
<br />
Some users report problems loading Inkscape 0.46-2 with XQuartz 2.2.1. - [https://bugs.launchpad.net/inkscape/+bug/226355 see here]. This problem occurs because XQuartz 2.2.1 has changed fontconfig.<br />
<br />
There are two possible fixes;<br />
<br />
1. Michael Whybrow, the packager of Inkscape for Mac suggests this;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type the following<br />
mkdir ~/.fontconfig<br />
b. Rerun Inkscape.app<br />
<br />
<br />
2. Another solution originally posted [https://answers.launchpad.net/inkscape/+question/28776 here] suggests editing an Inkscape configuration file;<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type<br />
nano /Applications/Inkscape.app/Contents/Resources/script<br />
b. Press CTRL+V (scrolls down a page)<br />
<br />
c. Change the code (use the arrows keys to get to the right part) from:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig || exit 12<br />
"""<br />
<br />
to:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig<br />
"""<br />
d. Save changes by pressing CTRL+O and then ENTER to confirm<br />
<br />
e. Run Inkscape and wait for first-time caching<br />
<br />
Also it seems that having the "''authentificate connexion''" option checked in Preferences -> Securtity tab does interfere with Inkscape launch. Uncheck it if Inkscape doesn't launch.<br />
<br />
'''''I've installed X11 on OS X but Inkscape keeps asking for it'''''<br />
<br />
On Panther (10.3), you may need to uninstall/reinstall or upgrade X11. Use [http://www.osxgnu.org/software/pkgdetail.html?project_id=244 OSXPM] to uninstall X11 - Install OSXPM and select the Uninstall tab, scroll down to X11User, select it and hit Uninstall. Then you can install X11 properly.<br />
<br />
== Installing on a Windows system ==<br />
=== Stable version ===<br />
You can find the installer from [http://www.inkscape.org/download/ download page]. Installing should be easy next-next-finish.<br />
=== Unstable development version===<br />
First be warned. Unstable and development means you likely will encounter crashes, usability problems, sometimes lost data. Ctrl+S will become your friend. If you cannot take the risk, please use the stable version instead.<br />
<br />
You are still reading so you are the brave one and want the bleeding edge.<br />
On [http://www.inkscape.org/download/ download page] there is a section named "Development versions". Find Mirrored win32 Builds link. This points you to inkscape.modevia.com server. There is information about builds and naming conventions. Get the .7z file with latest date on it. This can be extracted using [http://www.7-zip.org/ 7zip unpacker]. You will get directory which contains several files including inkscape.exe, run this by double clicking it. That's it. Don't forget reporting bugs, encouraging developers or fixing bugs yourself.<br />
==== Exremely small build ====<br />
If the build is significantly smaller than previous ones, the build most likely is broken and you should get the latest one which is of normal size (currently over 40MB and growing).<br />
==== Multiple versions ====<br />
For testing purposes it is good to see where some problem first appeared. For this reason you could hold as many parallel versions of inkscape as your disk allows.<br />
<br />
== Installing on Unix like systems ==<br />
<br />
=== Using Precompiled Packages (For Normal Users) ===<br />
<br />
==== Ubuntu Linux ====<br />
Probably the easiest way to install on Ubuntu is to use the apt command. <br />
<br />
Open a terminal and type;<br />
sudo apt-get update (enter)<br />
sudo apt-get install inkscape (enter)<br />
<br />
==== Ubuntu Linux Development Versions ====<br />
<br />
A few people have made builds of the development version of Inkscape 0.46 as it approaches release.<br />
<br />
<br />
Bryce Harrington has made available some i386 builds of the early January 2008 version for ''Gutsy'' (7.10) and ''Hardy'' (8.04 - currently in development). See the relevant post on the [http://www.nabble.com/Inkscape-0.46%7Esvn-Ubuntu-.deb-snapshot-td14645864.html Inksape-user email list]. This seems to be a one-off snapshot.<br />
<br />
<br />
NJH is offering nightly i386 and AMD64 builds for Gutsy and Edgy, along with supporting libraries like libcairo and libpixman. You can go to <br />
[http://ubuntu.cafuego.net/ http://ubuntu.cafuego.net] and select the link for the particular version of Ubuntu you're using. On the next page, select Inkscape, or Cairo etc, then follow the instructions on the following page.<br />
<br />
<br />
'''Note:''' Development versions offer some nice new features, but can be somewhat unstable, so save often. Inexperienced users will also quite possibly have problems installing them.<br />
<br />
==== Slackware Linux ====<br />
Pbhj says:<br />
<br />
I used the [http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=99112&release_id=426990 precompiled rpm] provided by Inkscape for the 0.44 release as my gcc wouldn't compile it. All you need to then do is run rpm2tgz at the command line on the package, eg " rpm2tgz inkscape-0.44-0.i686.rpm" and then install with "installpkg inkscape-0.44-0.i686.tgz".<br />
<br />
--[[User:Pbhj|Pbhj]] 13:29, 1 July 2006 (PDT)<br />
<br />
=== Compiling Your Own (For The Techies) ===<br />
<br />
<br />
NOTE: this isn't finished. I currently have two screwed up systems from fooling with bleeding edge GTK+ stuff, I don't know how that happened. !! :) I'll get to the end over the next few days tho. Setting up a more stable home network atm.<br />
-- <br />
Tsingi<br />
<br />
<br />
This was written building an InkScape snapshot on a new RedHat Linux installation. If you find that it doesn't answer your needs exactly, please update this file when you solve your particular problem.<br />
<br />
<br />
'''Installing libraries'''<br />
<br />
If you are running a debian based system, and have something like synaptic that lists recent enough versions of the libraries below, use that. If you want the latest libs, which you may need, especially if you are installing a snapshot or building from svn, you will want to download sources. Generally you will get a ''foo.tar.bz2'' or ''foo.tar.gz'' or ''foo.tgz'' file that you will need to unpack and build.<br />
<br />
''bz2'' files are the smallest. Uncompress them first by typing ''bunzip2 foo.tar.gz'' then unpack the remaining tar file by typing ''tar -xvf foo.tar''<br />
<br />
''foo.tar.gz'' files and ''foo.tgz'' files can be extracted in one operation by typing ''tar -xvzf foo.tar.gz'' <br />
<br />
Change to the directory that you just created ''foo''. type ''./configure'' then ''make'' then, as root, ''make install''<br />
<br />
Sometimes that is all you will need to do.<br />
<br />
Sometimes you will run into dependancy errors because you need a library you haven't installed yet. If you try installing inkscape without some of these dependancies, you will get a list of what you need. hopefully the instructions below will help you solve these dependancies.<br />
<br />
<br />
'''Running ldconfig'''<br />
<br />
after installing libs, (as root) you need to run ''ldconfig'' so that the linker can find the libraries that you have just installed. If you aren't logged in as root (i.e. if you became root by typing su) you may not have the /sbin/ directory in your path. so if ''ldconfig'' isn't working for you try typing ''/sbin/ldconfig''<br />
<br />
<br />
'''pkg-config'''<br />
<br />
''pkg-config'' is a utility that lists dependancies for libraries that sets up flags and paths for compiling. When it's working right it's wonderful. Getting it to work right is a pain in the ass if you don't know how. It's amazing how silent an IRC channel will get when you mention it.<br />
<br />
''pkg-config'' references pc files that applications install to give information about them. These are called metadata files, metadata means data about data. For a list of libraries that pkg-config sees, type ''pkg-config --list-all'' Having done that and looking at a list of pc files on my system (using ''find /usr -name "*.pc" > find.pc'', then browsing find.pc) I see that I also have a directory called ''/usr/lib64/pkgconfig/'' I might as well get that in there while I'm at it since none of those libs show up in a listing either and that's where most of them are.<br />
<br />
Depending on what shell you use, there are different ways of doing this. I'm adding a couple lines to my /etc/profile file:<br />
<br />
''PKG_CONFIG_PATH=/usr/lib/pkgconfig/:/usr/share/pkgconfig/:/usr/lib64/pkgconfig/:/usr/local/lib/pkgconfig/''<br />
<br />
''export PKG_CONFIG_PATH''<br />
<br />
Note that I have a new 64 bit system, which is why I'm going through all this. You probably won't have a ''/usr/lib64/pkgconfig/'' unless you do too, so don't just copy what I did. Also note that on a Windows system PATH type environment variables use semi-colons ";" for delimiters as opposed to colons ":"<br />
<br />
Using bash, to immediately source the file in the shell you are using, type ''. /etc/profile'. This won't test to see if the path gets put into your environment when open a shell though, so maybe a better thing to do is close your terminals and open new ones to see that it is actually set automagically.<br />
<br />
Ahh, I can now configure glibmm. The hair on the back of my neck is laying flat again, I think I'll have a coffee. :)<br />
<br />
<br />
<br />
'''libgc'''<br />
<br />
download and install the latest version of libgc[[http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/]]<br />
<br />
libgc installs in /usr/local/lib by default. If you have installed it and it is still not linking, you may not have that in your library path. There is a LD_LIBRARY_PATH environment variable, or alternatively you can make sure that /usr/local/lib is listed in the file /etc/ls.so.conf<br />
<br />
<br />
<br />
'''libsig++'''<br />
<br />
download and install libsig++ [http://libsigc.sourceforge.net/stable.shtml]<br />
<br />
this should be fairly straightforward.<br />
<br />
<br />
<br />
'''glibmm''' <br />
<br />
This is where, if you haven't wrestled with pkg-config on your system you start scratching your head. Because when you run configure on glibmm you may an error like this <br />
<br />
''checking for GLIBMM... configure: error: Package requirements (sigc++-2.0 >= 2.0.0 glib-2.0 >= 2.8.0 gobject-2.0 >= 2.8.0 gmodule-2.0 >= 2.8.0) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you<br />
installed software in a non-standard prefix.''<br />
<br />
''Alternatively you may set the GLIBMM_CFLAGS and GLIBMM_LIBS environment variables to avoid the need to call pkg-config. See the pkg-config man page for<br />
more details.''<br />
<br />
It seems that most packages install in a non standard prefix, in direct defiance of everything we have been led to believe regarding the concept of standard, so you may have to deal with this. See the note on ''pkg-config'' above.<br />
<br />
<br />
<br />
''gtkmm'' [http://www.gtkmm.org/]<br />
<br />
----<br />
(Ben) Tsingi, you are writing in the 'User Documentation' section. Most of this material is only appropriate for Developers and some would be better on the Mailing List. You will probably find that when you have finished, this page will be edited and pruned back. FWIW, I was expecting to find information about 'apt-get' (Debian) 'emerge' (Gentoo) and AutoPackage (the others).<br />
<br />
[[Category:User Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=40534CompilingUbuntu2008-12-15T16:22:28Z<p>Mahfiaz: /* Using prebuilt packages */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu hardy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu hardy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
If you used some --prefix=/... other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.<br />
If the the location prefix was /usr, then "sudo make install" is not recommended, as debian package manager would know nothing about new package. The better alternative is using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=40514CompilingUbuntu2008-12-15T16:18:20Z<p>Mahfiaz: /* Using prebuilt packages */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu intrepid main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu intrepid main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
If you used some --prefix=/... other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.<br />
If the the location prefix was /usr, then "sudo make install" is not recommended, as debian package manager would know nothing about new package. The better alternative is using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=36754CompilingUbuntu2008-10-11T09:32:55Z<p>Mahfiaz: /* Installing */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
If you used some --prefix=/... other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.<br />
If the the location prefix was /usr, then "sudo make install" is not recommended, as debian package manager would know nothing about new package. The better alternative is using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=36094CompilingUbuntu2008-09-22T18:58:40Z<p>Mahfiaz: /* Configuring and Compiling */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb clean build took 100 minutes.<br />
<br />
==== Installing ====<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=36084CompilingUbuntu2008-09-22T16:55:23Z<p>Mahfiaz: Revision to prefix hint</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Configuring and Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
''All bug reporting testers may find it useful to install to use --prefix=/home/''yourname''/opt/inkscape-revision-19900 or --prefix=/opt/inkscape-19900 or something similar, replacing the revision number with correct one (this is shown when svn fetching finishes, also can be found in file .svn/entries). This way you can have several versions of inkscape installed at once.''<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
==== Installing ====<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=36074CompilingUbuntu2008-09-22T16:44:28Z<p>Mahfiaz: Added updating section, some minor fixes</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository available with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
To install Inkscape, do the usual <br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the dependencies. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. This creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Enter the newly created inkscape directory.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to make it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make to compile.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
==== Installing ====<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
===== Fix no icons problem =====<br />
<br />
If you run this and you find that you have no tool icons it's because it's looking in the wrong place for them. To fix that you need to make a symbolic link to the correct location. Here is an example:<br />
<br />
<pre><br />
sudo ln -s /usr/share/inkscape /usr/local/share/inkscape<br />
</pre><br />
<br />
<br />
==== Update your version ====<br />
<br />
If you want to update your already built inkscape to the very latest version, you need to run following commands in inkscape source directory. Please correct the configure line and use the same installation method as on first install.<br />
<br />
<pre><br />
svn update<br />
./configure --prefix=/home/''yourname''/opt/local<br />
make<br />
make install<br />
</pre><br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=35604CompilingUbuntu2008-09-04T18:51:08Z<p>Mahfiaz: /* Hardy */</p>
<hr />
<div>== Hardy and Intrepid ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=33484CompilingUbuntu2008-08-04T17:16:00Z<p>Mahfiaz: /* Installing dependencies */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev libgsl0-dev<br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen.sh<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have it install to an alternate location so that you can keep the standard version installed and untouched<br />
<br />
<code><br />
./configure --prefix=/home/''yourname''/opt/local<br />
</code><br />
(replacing "yourname" with your actual directory user name, of course)<br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=25604CompilingUbuntu2008-03-20T07:45:58Z<p>Mahfiaz: /* Unstable developement version */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
=== Compiling unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=25594CompilingUbuntu2008-03-20T07:08:21Z<p>Mahfiaz: /* Hardy */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Using prebuilt packages ===<br />
For Ubuntu there is developers repository with prebuilt Inkscape which is updated occassionally.<br />
You should append the following lines to file /etc/apt/sources.list<br />
<pre><br />
deb http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
deb-src http://ppa.launchpad.net/inkscape.testers/ubuntu gutsy main<br />
</pre><br />
<br />
Run following commands to update the repository information and install all the latest programs available.<br />
<pre> sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=25584CompilingUbuntu2008-03-20T06:56:20Z<p>Mahfiaz: /* Dapper and Edgy */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
<pre><br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
</pre><br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=25574CompilingUbuntu2008-03-20T06:55:15Z<p>Mahfiaz: /* Dapper and Edgy */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev \<br />
libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=25564CompilingUbuntu2008-03-20T06:52:52Z<p>Mahfiaz: /* Hardy */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool \<br />
libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev \<br />
libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your current working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information about how to build the program. The README file says that if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
If the configure script ends with no error messages, you are the lucky one, all system requirements are met. Run make for compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager would know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=18664CompilingUbuntu2008-01-18T18:57:26Z<p>Mahfiaz: /* Compiling */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your currend working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information how to build the program. The README file says if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
or, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
And if configure ends with no error messages, you are the lucky one, all system requirements are met. Run make for the compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager will know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=18489CompilingUbuntu2008-01-12T18:38:55Z<p>Mahfiaz: /* Compiling */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your currend working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information how to build the program. The README file says if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
of, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
And if configure ends with no error messages, you are the lucky one, all system requirements are met. Run make for the compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed. On 1,4Ghz P3M with 512Mb it took 32 minutes.<br />
<br />
You can continue by installing using "make install" (not recommended, as debian package manager will know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=18484CompilingUbuntu2008-01-12T17:53:02Z<p>Mahfiaz: /* Compiling */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your currend working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information how to build the program. The README file says if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
of, if you want to have inkboard enabled,<br />
<br />
<pre><br />
./configure --enable-inkboard<br />
</pre><br />
<br />
And if configure ends with no error messages, you are the lucky one, all system requirements are met. Run make for the compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed.<br />
You can continue by installing using "make install" (not recommended, as debian package manager will know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=18479CompilingUbuntu2008-01-12T17:49:38Z<p>Mahfiaz: /* Installing dependencies */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape.<br />
<br />
===== Additional dependencies =====<br />
If you want to have optional features you may need to install some more packages:<br />
<br />
<pre><br />
sudo apt-get install libgnome-vfsmm-2.6-dev libssl-dev libmagick++9-dev libwpg-dev<br />
</pre><br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your currend working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information how to build the program. The README file says if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
And if configure ends with no error messages, you are the lucky one, all system requirements are met. Run make for the compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed.<br />
You can continue by installing using "make install" (not recommended, as debian package manager will know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=18469CompilingUbuntu2008-01-12T15:54:45Z<p>Mahfiaz: /* Hardy */</p>
<hr />
<div>== Hardy ==<br />
=== Consider using stable ===<br />
This is a short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to install the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
=== Unstable developement version ===<br />
==== Installing dependencies ====<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape. <br />
<br />
==== Getting source from SVN ====<br />
You have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your currend working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
==== Compiling ====<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information how to build the program. The README file says if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc.:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
And if configure ends with no error messages, you are the lucky one, all system requirements are met. Run make for the compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed.<br />
You can continue by installing using "make install" (not recommended, as debian package manager will know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=CompilingUbuntu&diff=18464CompilingUbuntu2008-01-12T15:29:16Z<p>Mahfiaz: /* Dapper and Edgy */</p>
<hr />
<div>== Hardy ==<br />
A short how to build the latest svn version. Please note that SVN version may be buggy and crash often. This is released for people who want to help testing or need the very latest features. If you are not of developer kind, you are suggested to fetch the stable version from the repositories using Synaptic or from command line:<br />
<br />
<pre><br />
sudo apt-get install inkscape<br />
</pre><br />
<br />
If you are sure you can face Inkscape being unstable, then please continue reading. First you should install all the requirements. This can be done by:<br />
<br />
<pre><br />
sudo apt-get install build-essential autoconf automake intltool libglib2.0-dev libpng12-dev libgc-dev libfreetype6-dev liblcms1-dev libgtkmm-2.4-dev libxslt1-dev libboost-dev libpopt-dev <br />
</pre><br />
<br />
Now you should have every dependency you need to build Inkscape. But first you have to fetch the source from subversion (SVN). If you have not subversion installed, install it:<br />
<br />
<pre><br />
sudo apt-get install subversion<br />
</pre><br />
<br />
After this you can fetch the latest source. It creates a new directory named inkscape into your currend working directory.<br />
<br />
<pre><br />
svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape<br />
</pre><br />
<br />
If you want to learn more about subversion, feel free to do so: http://inkscape.org/wiki/index.php/WorkingWithSVN<br />
<br />
Change your current directory to the inkscape.<br />
<br />
<pre><br />
cd inkscape<br />
</pre><br />
<br />
As you may have already noticed this folder contains some files with all CAPITAL letters like README, INSTALL, HACKING, COPYING and probably others. These contain the latest information how to build the program. The README file says if you have no configure script in the current directory you should run autogen script to create it:<br />
<br />
<pre><br />
./autogen<br />
</pre><br />
<br />
Now run configure script which detects your system variables, installed software etc:<br />
<br />
<pre><br />
./configure<br />
</pre><br />
<br />
And if configure ends with no error messages, you are the lucky one, all system requirements are met. Run make for the compiling.<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
This may take some time, probably hours, depending on your machine's speed.<br />
You can continue by installing using "make install" (not recommended, as debian package manager will know nothing about new package) or using checkinstall. If checkinstall is not installed, you can install it the usual way "sudo apt-get install checkinstall".<br />
<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
<br />
Happy inkscapeing.<br />
<br />
== Dapper and Edgy ==<br />
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper and Edgy:<br />
<br />
Note: the libgc-6.7 that is available in Edgy removes the need for the following:<br />
<br />
<pre><br />
sudo apt-get build-dep inkscape<br />
sudo apt-get install liblcms-dev build-essential<br />
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list<br />
sudo apt-get update<br />
sudo apt-get source libgc-dev<br />
sudo apt-get install fakeroot debhelper<br />
cd libgc*<br />
sudo fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../libgc*.deb<br />
</pre><br />
<br />
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:<br />
<br />
<pre><br />
apt-get source inkscape<br />
cd inkscape*<br />
fakeroot dpkg-buildpackage -uc -us<br />
sudo dpkg -i ../inkscape*.deb<br />
</pre><br />
<br />
To build the SVN snapshots:<br />
<br />
<pre><br />
# Untar and navigate to the inkscape source folder<br />
./configure<br />
make<br />
sudo make install<br />
</pre><br />
<br />
Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do<br />
<pre><br />
sudo checkinstall<br />
</pre><br />
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.<br />
If you get the "command not found" message, do<br />
<pre><br />
sudo apt-get install checkinstall<br />
</pre><br />
<br />
<br />
'''Notes:'''<br />
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same. <br />
<br />
<br />
libcms-dev was required for ./configure to work<br />
<br />
<br />
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.<br />
<br />
<br />
<br />
<br />
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:<br />
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev<br />
<br />
Inkscape requires libgc-6.7.<br />
<br />
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7<br />
<br />
Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)<br />
<br />
To overwrite libgc-6.3 with libgc-6.4:<br />
Download gc6.4<br />
./configure --prefix=/usr<br />
make<br />
sudo make install<br />
<br />
== Old libgc 6.5 debs for Breezy ==<br />
<br />
http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb<br />
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb<br />
<br />
[[Category:Developer Documentation]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Filter_effects_internals&diff=17374Filter effects internals2007-12-12T22:35:01Z<p>Mahfiaz: /* Writing out XML nodes */</p>
<hr />
<div>This page describes the internal workings of Inkscape Filter effects subsystem.<br />
<br />
== Overview ==<br />
<br />
From Filter effects viewpoint, Inkscape is essentially three-tiered system. The tiers are XML representation, SVG document and SVG renderer.<br />
<br />
XML representation level is merely an representation of XML tree of the document. It contains XML nodes, which have attributes, content, children etc. At this level these nodes and whatever content they have, don't have any special meaning. Inkscape XML representation layer could be used for any type of XML document, not just SVG.<br />
<br />
SVG document layer builds upon the XML layer. This layer gives meaning to XML node names, node attributes, node content etc. Mostly, nodes are handled by different classes depending on the name of the node. For example, nodes named feOffset are handled by SPFeOffset class, which resides in src/sp-feoffset.*<br />
<br />
Main tasks for SVG document layer are reading essential parameters from XML tree, parsing parameter values read from XML tree, writing out internal state to XML node and initializing SVG renderer classes.<br />
<br />
SVG renderer produces bitmap images from the SVG graphics. Again, there are own classes for most different node names. For example, feOffset node is handled by NR::FilterOffset class, which resides in src/display/nr-filter-offset.*<br />
<br />
Note that Inkscape uses two types of classes here: SVG document layer uses GTK style classes, which don't make use of C++ object oriented programming functionality, but are usable in plain C. SVG renderer in turn uses C++ classes.<br />
<br />
[[Image:Filters_overview.png|UML overview of filter effects system and related classes.]]<br />
<br />
== Coordinate systems ==<br />
<br />
This page talks a lot about coordinate systems and it some parts might be hard to follow, if you're not somewhat familiar with coordinate system transforms.<br />
<br />
In SVG transformations like moving, scaling, rotating and shearing objects are modelled as coordinate system transformations. Each object is defined in its own coordinate system, which is combination of its own transformation and all its ancestors transformations. This allows for relatively simple cumulative transforms, like when you rotate a group, it rotates as a whole.<br />
<br />
Let's try this out in Inkscape. Draw a rectangle, visibly wider than it's high. Rotate it 90 degrees anti-clockwise. Now, using the numerical inputs of the rectangle tool, change the width of the rectangle. You can notice, you're actually modifying the height of the rectangle. Why is this? Well, let's suppose that originally rectangle's width increased to right and height upwards. Now that you've rotated the rectangle by 90 degrees, you've actually rotated these base directions - or should we say vectors - by 90 degrees. For this rectangle, width now increases upwards and height to left.<br />
<br />
For a more through and detailed description, see [http://www.w3.org/TR/SVG11/coords.html Coordinate Systems, Transformations and Units chapter in SVG specifications]<br />
<br />
== Filters in document layer ==<br />
<br />
In document layer, the classes responsible for filter effects are SPFilter, SPFilterPrimitive and it's subclasses. Each of SPFilterPrimitive's subclasses handles one type of filter primitive. There is also related code in SPItem, SPStyle, NRArenaShape, NRArenaGroup and NRArenaImage.<br />
<br />
=== Reading parameters from XML tree ===<br />
<br />
The build method of a filter primitive class should read all possible parameters, that are special for that filter primitive. For example, sp_feOffset_build calls sp_object_read_attr for parameters dx and dy. Any parameters that are common for all filter primitives, should be read in build-method for SPFilterPrimitive, which is superclass for all filter primitive classes.<br />
<br />
Note that the build method doesn't need to make any attempt to handle any contents, the read attributes may have. It is handled by the set-method, which is described in next paragraph.<br />
<br />
=== Parsing parameters read from XML tree ===<br />
<br />
When the parameters in XML tree are modified or read by build method, the set method for corresponding document layer object gets called. This method receives the name and content of the parameter and should set object's internal state according to these values.<br />
<br />
=== Writing out XML nodes ===<br />
<br />
The write function in filter primitive class should write the relevant parts of object's internal state to given node. Note that many filter primitives don't do this, but instead just duplicate the contents of their XML node. For some examples how to do this right, see sp-shape.cpp or sp-filter.cpp.<br />
<br />
=== Initializing SVG renderer classes ===<br />
<br />
Each filter primitive class should have build_renderer method, which will add correct type of filter primitive to the filter renderer object and give correct settings for created filter primitive.<br />
<br />
=== SPItem ===<br />
<br />
Filter renderer uses item bounding box for its calculations, this information is set in sp_item_update in sp-item.cpp.<br />
<br />
Also in this file contains sp_item_write_transform, which handles transforming items. Some transformations, like scaling a rectangle, can be done by embedding transform into object's properteries (i.e. changing rectangle width and height) instead of writing out normal transformation. If an item has a filter set, this might give odd behaviour, so this method checks for set filters before embedding transforms.<br />
<br />
=== SPStyle ===<br />
<br />
Filter effect applied to an object can be considered as a part of object style and in Inkscape codebase it is a natural place to handle such object property.<br />
<br />
SPStyle can locate the filter referenced by an SVG item, and provides a pointer to corresponding SPFilter object.<br />
<br />
=== NRArenaShape, -Group and -Image ===<br />
<br />
While these are renderer level classes, they contain filtering code, that interfaces document level and renderer level.<br />
<br />
Here, in set_style method for each class, if the SVG item references some filter, the corresponding SPFilter is fetched from SPStyle and a NR::Filter object is constructed from it.<br />
<br />
Specifically, the set_style method calls sp_filter_build_renderer, which will initialize the filter renderer (NR::Filter object).<br />
<br />
== Filter effects renderer ==<br />
<br />
The filter effects renderer is somewhat more complicated than the document level. The main components are NR::Filter, NR::FilterSlot, NR::FilterUnits and filter primitive renderers, which are NR::FilterPrimitive subclasses.<br />
<br />
=== NR::Filter ===<br />
<br />
NR::Filter is the main interface to filter effects renderer internals for rest of Inkscape renderer and document level filter effect classes.<br />
<br />
=== NR::FilterSlot ===<br />
<br />
Temporary images used in rendering the filter effect are stored in 'image slots'. Slots are referenced to by integers. Positive numbers are free to be used for user-defined temporary images. Negative numbers in turn are reserved for special images like SourceGraphic. Each slot may contain one bitmap image.<br />
<br />
Slot numbers are created in document level, according to temporary image names given in SVG file. Each user-defined name receives own integer, unique inside that filter, and each SVG defined name is mapped to corresponding pre-defined negative number. See sp_filter_*_image_name in src/sp-filter.cpp and sp_filter_primitive_read in src/display/sp-filter-primitive.cpp for further info.<br />
<br />
Each input image name defined in SVG also has a symbolical name like NR::NR_FILTER_SOURCEGRAPHIC, so that developer doesn't need to remember, which negative integer corresponds to which input image. There's also a special value NR::NR_FILTER_SLOT_NOT_SET, which means that input image to be used is not defined in SVG file. If this is the case, the output from previous filter or SourceGraphic is used, per SVG specifications. See src/display/nr-filter-types.h for these names.<br />
<br />
All images stored in one FilterSlot object are in same coordinate system. This coordinate system might be different from the coordinate system of NR::Filter::render input image. If this is the case, FilterSlot::set transforms these input images to the internal coordinate system and FilterSlot::get_final transforms the output image from the internal coordinate system back to the coordinate system, the original input was in.<br />
<br />
=== NR::FilterUnits ===<br />
<br />
FilterUnits is a helper class to simplify using different coordinate systems and units in filter effect rendering. Essentially NR::Filter::render initializes a FilterUnits object with information about object's SVG bounding box, current object space to screen coordinates transformation matrix, desired filtering resolution and such. After this, different parts of filtering code like FilterSlot::set and filter primitive renderers can use information derived from information stored in FilterUnits.<br />
<br />
This is essential part in making rotating and shearing filtered SVG items work. Many of the filter primitives use lengths, which are defined along object's x- and y-axis. Take for example gaussian blur, for which one can define different blur radius along x- and y-axis. Now, when these items are rotated and/or sheared, object's axis may not point any more to same direction as the axis of the bitmap image being rendered. It wouldn't be feasible to implement the required functionality in all filter primitives, this applies to, so the input image is first transformed to such an coordinate system, where the object's axis are to same direction as image axis.<br />
<br />
FilterUnits has functions that provide FilterSlot with necessary transformation matrices to transform input image to a coordinate system, that all filters primitives know how to use and back to original coordinate system.<br />
<br />
A filter primitive can indicate, it needs input where the image axis point to same direction as object axis, by returning TRAIT_PARALLER from get_input_traits.<br />
<br />
[[Image:Filters_rendering_transformations.png|thumb|right|border|Operations applied on sheared item. Blue and red arrows represent axis of object's coordinate system]]<br />
<br />
=== Filter primitive renderers ===<br />
<br />
Filter primitive renderers are the workhorses of filter effects rendering. Each renderer can render one of the filter primitives specified in SVG.<br />
<br />
The basic workflow for rendering a filter primitive is<br />
* Fetch input images from FilterSlot received as parameter<br />
* Read pixel data from these images and write filter result to a new image<br />
* Save the result image to FilterSlot<br />
<br />
The filter primitive renderer can use FilterUnits object it has received as a parameter for various tasks related to lengths and coordinate systems. A couple examples:<br />
* FilterOffset uses primitive units to input image coordinates transformation matrix to find out, by how many pixels it must transform the image, when it knows the length in object's coordinate system.<br />
* FilterTurbulence uses the filter effects area transformed to input image coordinates to find out, to how big area it should render to.<br />
<br />
== NR::Filter initialization ==<br />
<br />
This is a brief explanation on how NR::Filter (filter effects renderer) objects are constructed.<br />
<br />
SPFilter has a single method sp_filter_build_renderer, which will initialize given renderer object (NR::Filter) to a correct state. Calling this method is all that needs to be done in those three nr-arena-* classes to set the correct filter renderer state. This method takes in the NR::Filter object instead of returning one, because this way that object can be reserved and freed on the same level in code. Also, this makes it easier to re-use the object instead of allocating new objects.<br />
<br />
The inside workings of sp_filter_build_renderer are as follows: each filter primitive (SPFilterPrimitive subclasses) has a build_renderer virtual function that will add the correct NR::FilterPrimitive object in the filter renderer. Before doing any filter specific initialization, this function should call sp_filter_primitive_renderer_common, which will do the part of initialization, which is common for all filter primitives.<br />
<br />
== Modification signals for filters ==<br />
<br />
This is explanation on how different parts of document tree are notified of changes to filter primitives. This is done so that the display can be updated as the filters are modified.<br />
<br />
As the underlying XML representation of the drawing is modified, the corresponding document level objects are notified of the change. Let's suppose, that the changed value was stdDeviation in feGaussianBlur. For the SPGaussianBlur object, this will show as call to sp_gaussianBlur_set method, with key=SP_ATTR_STDDEVIATION and 'value' containing the new value.<br />
<br />
After modifying its internal state according to new values, the _set method should pass the update notification onwards - this will allow objects using this filter to update their own state. As for now, this happens by calling ::requestModified(SP_OBJECT_MODIFIED_FLAG) on the filter primitive's parent (which should be SPFilter). This may not be the best way to do this, though.<br />
<br />
Filters are referenced from object style. When SPStyle object is built, it subscribes for update notifications from SPFilter it references (if any). Now when ::requestModified is called on SPFilter, these update notifications are also called (eventually, as requestModified only schedules modification event, instead of executing the event immediately).<br />
<br />
The SPStyle object in turn knows, which object it's part of - these objects are the actual drawable objects, to which the filters are applied to. SPStyle propagates the modification event to that object, which in turn applies the modifications to its internal state and schedules redraw for itself.</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Interface_translation&diff=17294Interface translation2007-12-11T15:58:02Z<p>Mahfiaz: /* Get the PO file for your language */</p>
<hr />
<div>Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
== Introduction to PO file format ==<br />
<br />
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.<br />
<br />
&#35;: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br />
&#35;: gedit/dialogs/program-location-dialog.glade2.h:2<br />
msgid "Set program location..."<br />
msgstr "Ställ in programplats..."<br />
<br />
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from. <br />
<br />
A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:<br />
<br />
* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.<br />
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.<br />
<br />
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.<br />
<br />
== Get the PO file for your language ==<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://inkscape.svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then you will have to get an empty template file to start a new translation. <br />
The most straightforward way to obtain the inkscape.pot template is to download it from here (updated weekly):<br />
<br />
http://inkscape.modevia.com/potfile/inkscape.pot<br />
<br />
Alternatively, you can checkout the full SVN project repository and generate the project template. Information on how to get the source tree can be found [http://inkscape.org/svn.php here]. Then, you have to follow some steps in order to generate the template:<br />
<br />
1. "./autogen.sh"<br />
2. "./configure"<br />
3. enter the "po" directory: "cd po"<br />
4. generate the current PO template: "intltool-update --pot"<br />
<br />
To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough), <br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. merge your existing translations into the new POT file (inkscape.pot):<br />
<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
Now that you have an empty PO template, you can start translating the messages.<br />
<br />
== Tools for translators ==<br />
<br />
You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.<br />
<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://www.poedit.net/)<br />
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.<br />
<br />
And last but not least, [http://www.gnu.org/software/gettext/manual/ gettext] utils, which are installed on every linux distribution. You can see a complete reference too from installed info pages by running the command:<br />
<br />
info gettext<br />
<br />
== A few important things to remember ==<br />
<br />
* Some strings that can be ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication. (Some info on how to disambiguate a string can be found [http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html#Q-:CAPS here].)<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Submit finished work ==<br />
<br />
Upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
(Don't forget to compress your file before uploading it, as Sourceforge tracker doesn't accept large files.)<br />
<br />
Additionally, you may send a message to Inskcape's translators mailing list.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
= Windows installer translation =<br />
<br />
Strings for Windows installer are saved in *.nsh files. Each translation has its own file located in ''packaging\win32\'' directory of subversion checkout. Get this file in similar way of getting *.po file.<br />
=== Translating ===<br />
# Get the file according to your language. If there is not such a file, copy ''english.nsh'' file and rename it to ''yourlanguage.nsh''.<br />
# Translate strings in the file<br />
# Change '''!insertmacro MUI_LANGUAGE "English"''' and each occurence of '''${LANG_ENGLISH}''' to values corresponding with your language. For example '''!insertmacro MUI_LANGUAGE "Czech"''' and '''${LANG_CZECH}'''.<br />
# Change header information in '''yourlanguage.nsh''' file, like "windows code page" and "Authors" to proper values.<br />
=== Testing the translation ===<br />
# This part is optional but recommended. For this part you need [http://nsis.sourceforge.net/Main_Page NSIS installer] and run <pre>make -f Makefile.mingw dist</pre> command after succesfull compilation of Inkscape. This command prepares binary of Inkscape for installator creation.<br />
# Add filename of your file to '''inkscape.nsi''' file, "STRING LOCALIZATION" section, "Language files" subsection.<br />
# Right click on the inkscape.nsi file and choose "Compile NSIS Script". The installer compilation will start.<br />
# When the installer is finished, run it to test translations of strings in Installer and Uninstaller parts.<br />
# If the translation is tested succesfully, submit it to the patch tracker at sourceforge.net and mark as "Translation". If you haven't tested your translation yet, submit it too but enter this information to the patch information. You will be contacted about its correctness.<br />
<br />
= Default template translation =<br />
<br />
* To translate default template, modify the default.svg file and save it as default.xx.svg where "xx" is ISO code of your language. The file can be found in ''/usr/share/inkscape/templates/'' directory on Linux, or ''C:\Program Files\Inkscape\share\templates\'' directory on MS Windows(tm). Also you can get it from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/share/templates/ SVN repository]. <br />
* You need to modify your PO translation as well to use your localized default template. Look up for a msgid "default.svg" on the PO file and translate it accordingly to the file name of the localized template.<br />
* To test it, save it to the proper location and restart Inkscape. Default document should be now based on your localized template. (This is valid if your system is properly set to your locales).<br />
* Upload default.xx.svg to the patch tracker.<br />
<br />
To translate default template can be used Inkscape as well as any UTF-8 encoding capable text editor.<br />
<br />
= Translation information =<br />
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Documentation_translation&diff=17289Documentation translation2007-12-11T15:55:50Z<p>Mahfiaz: /* Manual pages (man) */</p>
<hr />
<div>Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
== Tutorial Translation ==<br />
<br />
Inkscape's tutorial sources are in Docbook XML format, with illustrations in SVG. <br />
<br />
The ''translations'' of the tutorials however are in the well-know PO format. If you want to help, download them here:<br />
<br />
http://inkscape.svn.sourceforge.net/viewvc/inkscape/doc-docbook/trunk/<br />
<br />
* Each tutorial is in its own subdirectory. You need the <code><LANG>.po</code> file, for example <code>basic/fr.po</code>. Please coordinate with the previous translator listed in that file!<br />
* If there is none of these files, get the <code><tutorial>.pot</code> file, rename it to <code><LANG>.po</code> and start translating.<br />
<br />
Once you are satisfied with what you have done, submit it to the SourceForge patch tracker.<br />
<br />
Thanks!<br />
<br />
== Keyboard and mouse translation ==<br />
<br />
* TBD<br />
<br />
== User Manual ==<br />
* See also [[Embedded Help]]<br />
* First download the user manual xml document from [http://inkscape.svn.sourceforge.net/viewcvs.cgi/inkscape/user_manual/trunk/xml/ SVN]<br />
* edit the trunk/xml/inkscapeUTF.xml file. All languages are inside.<br />
* Just read the file, choose the language reference you want to use (en, fr...) and translate by duplicating the node and changing lang attribute to yours. <br />
* when finishing editing, if necessary edit the Makefile and add your language to the Makefile. In every case test your file with some tools (xmllint...) or just type again "make your_language" : syntax errors will be displayed : please correct them.<br />
* submit your work as a patch in the patch tracker and warn Cédric Gemy (cedric at le-radar.com) by email.<br />
<br />
== Manual pages (man)==<br />
<br />
* first download inkscape.pod from [http://inkscape.svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/inkscape.pod?view=log SVN]<br />
* rename it to inkscape.xx.pod, where xx is the code for your language<br />
* open inkscape.xx.pod in your favourite text editor (pay attention to encoding which must be UTF8), and directly translate in the file. <br />
* you can take a look at a first example of translation with inkscape.fr.pod<br />
* finally, submit your work in the patch tracker and drop a mail to the inkscape devel mailing list.<br />
<br />
== Translation information ==<br />
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
[[Category: Developer Discussion]]</div>Mahfiazhttps://wiki.inkscape.org/wiki/index.php?title=Documentation_translation&diff=17284Documentation translation2007-12-11T15:55:31Z<p>Mahfiaz: /* User Manual */</p>
<hr />
<div>Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
== Tutorial Translation ==<br />
<br />
Inkscape's tutorial sources are in Docbook XML format, with illustrations in SVG. <br />
<br />
The ''translations'' of the tutorials however are in the well-know PO format. If you want to help, download them here:<br />
<br />
http://inkscape.svn.sourceforge.net/viewvc/inkscape/doc-docbook/trunk/<br />
<br />
* Each tutorial is in its own subdirectory. You need the <code><LANG>.po</code> file, for example <code>basic/fr.po</code>. Please coordinate with the previous translator listed in that file!<br />
* If there is none of these files, get the <code><tutorial>.pot</code> file, rename it to <code><LANG>.po</code> and start translating.<br />
<br />
Once you are satisfied with what you have done, submit it to the SourceForge patch tracker.<br />
<br />
Thanks!<br />
<br />
== Keyboard and mouse translation ==<br />
<br />
* TBD<br />
<br />
== User Manual ==<br />
* See also [[Embedded Help]]<br />
* First download the user manual xml document from [http://inkscape.svn.sourceforge.net/viewcvs.cgi/inkscape/user_manual/trunk/xml/ SVN]<br />
* edit the trunk/xml/inkscapeUTF.xml file. All languages are inside.<br />
* Just read the file, choose the language reference you want to use (en, fr...) and translate by duplicating the node and changing lang attribute to yours. <br />
* when finishing editing, if necessary edit the Makefile and add your language to the Makefile. In every case test your file with some tools (xmllint...) or just type again "make your_language" : syntax errors will be displayed : please correct them.<br />
* submit your work as a patch in the patch tracker and warn Cédric Gemy (cedric at le-radar.com) by email.<br />
<br />
== Manual pages (man)==<br />
<br />
* first download inkscape.pod from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/inkscape.pod?view=log SVN]<br />
* rename it to inkscape.xx.pod, where xx is the code for your language<br />
* open inkscape.xx.pod in your favourite text editor (pay attention to encoding which must be UTF8), and directly translate in the file. <br />
* you can take a look at a first example of translation with inkscape.fr.pod<br />
* finally, submit your work in the patch tracker and drop a mail to the inkscape devel mailing list.<br />
<br />
== Translation information ==<br />
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
[[Category: Developer Discussion]]</div>Mahfiaz