Compiling e17 for ubuntu dapper

Get E


a) Get the latest packages from:

extract with

for i in `ls *.tar.gz`; do tar xfvz $i; done


b) get the latest cvs sources:

cvs -d login
cvs -z3 -d co e17

Build packages

install some packages:

sudo apt-get install fakeroot cdbs debhelper libpng3-dev libpng3 libjpeg62 libjpeg62-dev html2text libgtk2.0-dev libxine-dev libtagc0-dev libtagc0 libcurl3-dev libcurl3 devscripts giflib3g-dev giflib3g libid3-3.8.3-dev libtiff4-dev libtiff4

There are probably alot more you need, but these were the ones that were not installed when I wanted to install e17 – you can tell you need more packages if a configure script fails. The error message will usually be informative enough to let you do a search for the right packages (just make sure to install the “*-dev” packages as well as the normal libraries/apps). There are optional packages you may want too (such as the gif and tiff ones above) and you can find out about these from keeping a eye on “Configuration Options Summary” at the end of a “configure” run.

The build order we’ll follow is:

Then the apps:

cd libs/imlib
chmod u+x debian/rules
fakeroot debian/rules binary
cd ..

You should now have imlib2-demo, imlib2-test, libimlib2, libimlib2-dev .deb files in the libs directory. You possibly don’t need the ./ step if ./configure files already exist.
Install these packages using dpkg, you might get some issues with dependencies but they can be fixed by “apt-get -f install” usually.

Do the same for “eet”:

cd ../libs/eet
chmod u+x debian/rules
fakeroot debian/rules clean
fakeroot debian/rules binary

I found that ‘fakeroot debian/rules binary’ couldn’t find eet-config, this is fixed by running ‘fakeroot debian/rules clean’ first. This happens for most of the libraries, so follow the above order of commands to avoid trouble. Install the eet packages that are created.

Do the same for edb if you like. (EDB is a database convenience library wrapped around the Berkeley DB 2.7.7 by Sleepycat Software. It is intended to make accessing database information portable, easy, fast and efficient). Then do the same for evas to ewl in the list above. Each time installing the .deb afterwards. You need to do this because the later packages depend on the previous ones being installed.

Next go through the applications you want to install using the same process.
1. Entice – an image viewer.
2. Entrance – a login manager. When configuring after it will warn about specifying the xsession path. You don’t have to worry about this when compiling to a .deb file.
3. Elicit – the screen zoomer and colour picker.
4. E – The window manager itself.
5. I also compiled e_utils as it has some themes and other tidbits in it – this requires the lib/engrave package to be built as well.

Now logout and then switch to the console using ctrl-f1. Login as root or a user capable of sudo and then run (replace gdm with kdm if you use kubuntu):

/etc/init.d/gdm stop
/etc/init.d/entrance start

Update: People have reported that Entrance currently can do something strange to your environment. Java won’t work, gcc returns “collect2: can’t locate ld”, and the eaps (the files that represent applications in the enlightenment ibar launcher) are not detected. These are fixed by just using gdm instead of entrance, run the following and select gdm as your display manager:

dpkg-reconfigure gdm


1. For some reason libedje0-dev couldn’t find the libedje0 package even though it was installed.
Fix by editing libs/edje/debian/control and removing the “(= ${Source-Version})” following all entries of libedje on lines beginning “Depends”.


Hope this is of some help to people. I found it quite rejuvenating to get back into compiling and experimenting with new stuff. I’ll post my opinions on E17 soon enough I suspect.


#1   andrew brown on 04.20.06 at 3:53 pm

yet despite all this, people still choose windows over linux?

hey don’t get me wrong, I love unix (freebsd4lyfe i’m admin at but until they work out how to make all that transparent then the general public will always stay with windows

the most we can realistically hope for is for them to switch to OSX which will happen 🙂

#2   Joel on 04.20.06 at 5:10 pm

oh, don’t think this is normal procedure for installing something. Usually you can use a graphical interface and new software is but a click away (and updating is automatic).

This is unreleased code in alpha stage which I want to use because it is fancy.

Although XGL and Compiz are alot more fancy.

Leave a Comment