Difference between revisions of "CompilingUbuntu"

From Inkscape Wiki
Jump to navigation Jump to search
(remove all redundant content that is already covered in https://inkscape.org/develop/getting-started/)
 
(56 intermediate revisions by 17 users not shown)
Line 1: Line 1:
== Dapper and Edgy ==
== Consider using pre-built packages ==
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:
This is a short how to build the latest development version. '''If you don't want to change the source code, you can avoid this effort and use pre-built packages''', either the well-tested stable version, or the newest developer's version intended for testing. See [[Installing_Inkscape#Ubuntu_or_Debian_Linux]].


Note: the libgc-6.7 that is available in Edgy removes the need for the following:
== Compiling unstable developement version ==


<pre>
Please refer to https://inkscape.org/en/develop/getting-started/
  sudo apt-get build-dep inkscape
  sudo apt-get install liblcms-dev build-essential
  echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list
  sudo apt-get update
  sudo apt-get source libgc-dev
  sudo apt-get install fakeroot debhelper
  cd libgc*
  sudo fakeroot dpkg-buildpackage -uc -us
  sudo dpkg -i ../libgc*.deb
</pre>
 
If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:


<pre>
  apt-get source inkscape
  cd inkscape*
  fakeroot dpkg-buildpackage -uc -us
  sudo dpkg -i ../inkscape*.deb
</pre>


To build the SVN snapshots:
=== Installing ===


<pre>
If you used some CMAKE_INSTALL_PREFIX other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location.
  # Untar and navigate to the inkscape source folder
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".
  ./configure
  make
  sudo make install
</pre>


Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do
<pre>
<pre>
   sudo checkinstall
   sudo checkinstall
</pre>
</pre>
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.
If you get the "command not found" message, do
<pre>
  sudo apt-get install checkinstall
</pre>
'''Notes:'''
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.
libcms-dev was required for ./configure to work
This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.
The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:
  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
Inkscape requires libgc-6.7.
Breezy uses 6.4, Dapper uses 6.6, Edgy uses 6.7
Hoary uses version 6.3, which is provided in the Repos.  (Is there somewhere to get a .deb for 6.4?)
To overwrite libgc-6.3 with libgc-6.4:
  Download gc6.4
  ./configure --prefix=/usr
  make
  sudo make install


== Old libgc 6.5 debs for Breezy ==
Happy inkscapeing.


http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb


[[Category:Developer Documentation]]
[[Category:Developer Documentation]]

Latest revision as of 20:06, 16 February 2020

Consider using pre-built packages

This is a short how to build the latest development version. If you don't want to change the source code, you can avoid this effort and use pre-built packages, either the well-tested stable version, or the newest developer's version intended for testing. See Installing_Inkscape#Ubuntu_or_Debian_Linux.

Compiling unstable developement version

Please refer to https://inkscape.org/en/develop/getting-started/


Installing

If you used some CMAKE_INSTALL_PREFIX other than /usr, then you may install using usual 'make install' or 'sudo make install', depending on the location. 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". 

   sudo checkinstall

Happy inkscapeing.

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