Difference between revisions of "Compiling Inkscape"

From Inkscape Wiki
Jump to navigation Jump to search
m
 
m (link fix)
(6 intermediate revisions by the same user not shown)
Line 40: Line 40:
 
  checking for gtk+-2.0 >= 2.0.0  libxml-2.0 >= 2-2.4.24  sigc++-1.2  gtkmm-2.0... Package gtkmm-2.0 was not found in the  pkg-config search path.
 
  checking for gtk+-2.0 >= 2.0.0  libxml-2.0 >= 2-2.4.24  sigc++-1.2  gtkmm-2.0... Package gtkmm-2.0 was not found in the  pkg-config search path.
 
  Perhaps you should add the directory containing `gtkmm-2.0.pc'
 
  Perhaps you should add the directory containing `gtkmm-2.0.pc'
  to the PKG_CONFIG_PATH environment variable
+
  to the [[PKG_CONFIG_PATH]] environment variable
 
  No package 'gtkmm-2.0' found
 
  No package 'gtkmm-2.0' found
  
A solution is to set the PKG_CONFIG_PATH variable as so:
+
A solution is to set the [[PKG_CONFIG_PATH]] variable as so:
  
 
for bash:
 
for bash:
     export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
+
     export [[PKG_CONFIG_PATH]]=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
 
for csh:
 
for csh:
     setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig
+
     setenv [[PKG_CONFIG_PATH]] /usr/local/lib/pkgconfig:/usr/lib/pkgconfig
  
 
A good place to put this line is in your .bashrc or .cshrc file
 
A good place to put this line is in your .bashrc or .cshrc file
Line 77: Line 77:
 
* As the 'root' user,  install it with:
 
* As the 'root' user,  install it with:
  
     $ make install
+
     # make install
  
 
== Boehm-GC ==
 
== Boehm-GC ==
  
Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.4.tar.gz
+
Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.6.tar.gz
  
  
[Note that for old 0.40CVS development versions we used the C++ version of gc, so you need to compile it with the --enable-cplusplus; we didn't include that version in any of the official releases though.]
+
*  Download this file:
 +
**  http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.6.tar.gz
 +
*  Unpack it
 +
**  tar zxf gc6.6.tar.gz
 +
*  Configure and build it
 +
**  cd gc6.6
 +
**  ./configure --disable-shared --enable-static
 +
**  make
 +
*  Install it
 +
**  su    (or however else you become root)
 +
**  make install
  
Also, if searching for a package for GC, the name of it is sometimes:
+
 
 +
Binaries:  If searching for a package for GC, the name of it is sometimes:
  
 
* gc
 
* gc
Line 92: Line 103:
 
* libgc-devel
 
* libgc-devel
 
* boehm-gc  (on Gentoo)
 
* boehm-gc  (on Gentoo)
 +
* debian/ubuntu:  sudo apt-get install libgc-dev
  
  
 
== libSigc++ ==
 
== libSigc++ ==
  
Source: http://sourceforge.net/project/showfiles.php?group_id=1970&package_id=76644
+
Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.0/
  
With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
+
With this file, and for [[GlibMM]] and [[GtkMM]] below, it is usually desirable for us developers to
 
build this C++ library statically.  This removes a dependency that might be difficult for an
 
build this C++ library statically.  This removes a dependency that might be difficult for an
 
end-user during installation.  Configure it with:
 
end-user during installation.  Configure it with:
Line 105: Line 117:
  
  
== GlibMM ==
+
== [[GlibMM]] ==
  
Source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.4/
+
Source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.8/
  
== GtkMM ==
+
== [[GtkMM]] ==
  
Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.4/
+
Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.8/
  
  
Line 148: Line 160:
 
Turning off just optimization (which can produce strange results in debuggers):
 
Turning off just optimization (which can produce strange results in debuggers):
  
export CC=g++
 
 
  export CXXFLAGS='-g -O0 -Wall'
 
  export CXXFLAGS='-g -O0 -Wall'
 
  export CFLAGS='-g -O0 -Wall'
 
  export CFLAGS='-g -O0 -Wall'
 
  ./configure
 
  ./configure

Revision as of 02:32, 22 January 2006

Hopefully, Inkscape will compile right out of the box. If it doesn't, well that's what this page is for.

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

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

Notes

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

You may want to also add plugins durring or after compiling.

OS & Distribution Specific


Package Config (pkg-config)

If you must compile and install any of these from source, you may find an error like this when trying to compile them or Inkscape itself:

checking for gtk+-2.0 >= 2.0.0  libxml-2.0 >= 2-2.4.24  sigc++-1.2  gtkmm-2.0... Package gtkmm-2.0 was not found in the  pkg-config search path.
Perhaps you should add the directory containing `gtkmm-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkmm-2.0' found

A solution is to set the PKG_CONFIG_PATH variable as so:

for bash:

    export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig

for csh:

    setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig

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


Getting and Installing Source packages

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download source packages and build and install them yourself. Actually this is not that hard, and is similar to doing a Gentoo 'emerge.'

  • Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with
   $ tar zxf somepackage-1.0.tar.gz
   or
   $ tar jxf somepackage-1.0.tar.bz2
  • Then 'cd' into the new directory.
  • Configure it with the command:
   $ ./configure
  • Build it with:
   $ make
  • As the 'root' user, install it with:
   # make install

Boehm-GC

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.6.tar.gz



Binaries: If searching for a package for GC, the name of it is sometimes:

  • gc
  • libgc
  • libgc-devel
  • boehm-gc (on Gentoo)
  • debian/ubuntu: sudo apt-get install libgc-dev


libSigc++

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.0/

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to build this C++ library statically. This removes a dependency that might be difficult for an end-user during installation. Configure it with:

   ./configure --enable-static --disable-shared


GlibMM

Source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.8/

GtkMM

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.8/




Developer Compilation

Plain vanilla compilation is done as documented in INSTALL; ./autogen.sh (optionally); ./configure; make; su && make test; make install (optional). See INSTALL for more on that.

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

  1. Turn off optimization
  2. Use ccache for faster compilation
  3. Set up a separate build directory (nice for testing both gcc and g++, or cross compiling)
  4. Use the -j N flag to optimize for the number of processors in your machine, with N = 1 + no. proc's

Example: Setting up both gcc and g++ build environments (in separate tree), and using ccache for faster compilations on a dual-processor machine, with no optimization, assuming /bin/bash:

mkdir build-gcc build-g++
cvs checkout inkscape
cd inkscape
libtoolize --copy --force
./autogen.sh
cd ../build-gcc
CFLAGS='-g -O0 -Wall' CC='ccache gcc' ../inkscape/configure
cd ../build-g++
CXXFLAGS='-g -O0 -Wall' CXX='ccache g++' ../inkscape/configure
cd ../build-gcc && make -j 3
cd ../build-g++ && make -j 3


Turning off just optimization (which can produce strange results in debuggers):

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