This is the Get-E.org Enlightenment DR17 User Guide. Please note that this guide only covers the E17 windowmanager and its dependencies. For information on other EFL based programs, consult the EFL user guide instead.

3.1 - Installation from CVS

Enlightenment DR17 hasn't been released yet so you will need to get a current development version directly from CVS or use the snapshots available at http://enlightenment.freedesktop.org. If you don't know what CVS is, or need some more information about it, check http://www.nongnu.org/cvs. There are unofficial binary packages (made from CVS snapshots) available for some distributions, but that is covered in the next section.

Enlightenment DR17 is based on the Enlightenment Foundation Libraries (EFL). In order to be able to install E17, and the EFL libraries it requires, you will need a sane build environment. The following is a list of general, non distro-specific, dependencies that need to be satisfied before you can proceed. Please note that your distribution may have these dependencies named differently.

• m4
• autoconf
• automake (1.7 or higher)
• libtool
• pkg-config
• texinfo
• zlib
• jpeg
• freetype 2
• xorg-x11 or xfree86
• x11-libs

Now that you have a sane build environment, you may proceed to install the EFL libraries. You will need to first install the following EFL libraries in the order listed:

1. e17/libs/eet
2. e17/libs/evas
3. e17/libs/ecore
4. e17/libs/efreet
5. e17/libs/embryo
6. e17/libs/edje

Getting EFL Libraries and E17 From Cvs

To download the source code for these libraries (and for E17) from CVS, use the following commands as a user account. Note there is no password for the login, when prompted just press enter. A directory called "e17" will be created inside the directory from which you run these commands:

$ cvs -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e login
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/libs/eet
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/libs/evas
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/libs/ecore
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/libs/efreet
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/libs/embryo
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/libs/edje
$ cvs -z3 -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e co e17/apps/e
$ cvs -d:pserver:anoncvs@anoncvs.enlightenment.org:/var/cvs/e logout

Installing EFL Libraries and E17

Now that you have downloaded the required EFL libraries, let's install them. After this you can start installing E17 itself using similar commands which will be covered further in this book.

You will need to enter the corresponding directories, in the order specified earlier, and compile & install them. You are probably already familiar with the following basic steps:

$ ./autogen.sh
$ make
$ make install (as root)

By default, the EFL libraries will install to /usr/local/. If you wish to install them to a different location, or would like to see what other options are available, then run ./configure --help after running ./autogen.sh. If you already have E16 installed, you will need to install E17/EFL to a different path to avoid conflicts. There is one exception though: E16.8 can co-exist with E17 in the same install path, as they use different binary names.

If you are having some autogen or automake related problems, you can specify the version needed manually by adding this at the top of the autogen.sh file before running it:

#!/bin/sh
export WANT_AUTOCONF=2.5
export WANT_AUTOMAKE=1.7

Please note that there are known problems with using automake-1.10 and currently is not supported for building Enlightenment or any EFL libraries.

Make sure you have the right paths configured in /etc/ld.so.conf. For example, if you install the EFL to /usr/local, you should also add that directory to /etc/ld.so.conf and run the command ldconfig (as root) to create the necessary links and cache for the most recent shared libraries found in the directories specified in the config file. Note that you'll need to run the ldconfig command (as root) after every library that you install to this custom directory.

Now you can move on to installing E17 itself. If you want to install E17 in a prefix other than the usual ones, for example in your home directory, then you'll need to pass a prefix to autogen.sh:

$ ./autogen.sh --prefix=/path/to/install

E17 is relocatable, it will determine the install prefix on the fly when it is run so, for example, you can use the prefix /opt/e17 and just move the base dir (in this case "../../.././/usr/local/e17") to anywhere you like at any later time. E17 should adjust and find it. There are built-in fallbacks too though, so it will use the compiled prefix as default if E17 is unable to find itself anywhere else.