Compiling and Installing
- Glib >= 2.30 - http://developer.gnome.org/glib/2.30/
- Gtk+3 >= 3.0 - http://developer.gnome.org/gtk3/3.0/
- VTE >= 2.91 - http://developer.gnome.org/vte/0.30/
- libConfuse - http://www.nongnu.org/confuse/
- libx11-dev - http://www.x.org/wiki/
On Ubuntu based system install dependencies with:
sudo apt-get install git dh-autoreconf autotools-dev debhelper libconfuse-dev libgtk-3-dev libvte-2.91-dev pkg-config
You possibly need other packages such as
autopoint, and X11 development libraries.
# This may be outdated (see Ubuntu example above, for a more thorough list) sudo yum install git automake libconfuse-devel vte3-devel gtk3-devel glib-devel gettext-devel
The dependencies section above is complete but the sample command may not be complete, depending on your system you may need to
install additional packages. Please carefully read the output of the
autogen.sh (see below) for more information of what
you need to install.
Generally if you have installed the development packages (e.g. *-dev or *-devel) of the dependencies above and the autotools suite then it should be possible to compile with:
mkdir build cd build ../autogen.sh --prefix=/usr make --silent
build/ and calling autogen.sh relative from there
makes sure that we perform an out-of-tree build and all generated files are
build/. This way build artifacts will not clutter the
If you get the following error message, then you are missing the autopoint binary which is part of the autotools suite. On Ubuntu the
dh-autoreconf package installs it along with automake, autoconf and autoreconf.
Can't exec "autopoint": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 345.
You do not need the
--silent option, but I prefer to use it to reduce the output a bit. If you experience any problem during build,
then drop the
After you have compiled the package run the following command to install tilda to the prefix that you have chosen before:
sudo make install
If you don't want to install to the
/usr prefix, choose some other prefix when you run the
/opt/tilda and add it to your path.
Packaging for Debian
This section explains how to package Tilda for Debian and Debian derived distributions.
Preparation before building the package
In order to build a package which can be uploaded to some Debian based distribution the following steps are necessary. Replace '#' with the number of the current minor release.
Check out the latest stable branch (e.g. tilda-1-2) and commit any changes or patches which you want to include, then commit these changes.
Change into the
po/folder and run
Update the changelog with a message such as: "Update the change log for 1.2.#"
Update the version number in configure.ac and make a commit with the version number: "1.2.#"
Create a tarball using git-archive:
git archive --prefix=tilda-1.2.#/ -o ../tilda_1.2.#.orig.tar.gz HEAD
Building a package
With the above
git archive command you get a tarball
from which a Debian package can be build. A Debian package
consists of a separate source and binary package. The following steps
document the basic commands that are required to build both the source package
and the binary package, to verify that both are correct and to
upload the source package to mentors.debian.org.
I am using pbuilder to build the source and binary packages.
Please refer to the man pages pbuilder(8) on howto
setup the base image. I also use pdebuild as a convenient script to
debuild inside the pbuilder environment (see pdebuild(1)).
cd ..; tar -xf tilda_1.2.#.orig.tar.gz
tilda-debianrepository from Github and copy the
Update the Debian specific change log at
debian/changelog, such that it contains the latest version that you are building.
To build the source package you need to run debuild. You can use one of the following two methods to do this:
Run debuild inside a change root by using
sudo pdebuild --use-pdebuild-internal \ -- --basetgz ~/pbuilder/unstable-base.tgz
debuilddirectly from the current folder (e.g. from
debuildfinishes without a problem next run
pbuilder, this will verify that the packge is buildable (without warnings or errors) in a clean environment:
sudo pbuilder --build --basetgz ~/pbuilder/unstable-base.tgz tilda_1.2.#-1.dsc
debsignto sign the package with your PGP key:
pbuilderdoes not complain and you don not see any warnings in
lintian, then upload the package to mentors:
dput mentors tilda_1.#.#-1_amd64.changes