E17 User Guide/Scripts for automated CVS installation

«	E17 User Guide Scripts for automated CVS installation	»
E17 User Guide/Installing from Source Repository	E17 User Guide Scripts for automated CVS installation	Installing Using Development Snapshots

Although it's easy to install Enlightenment once it's a bit hard and boring to keep it up to date with the current CVS sources. The reason is, that you'll have to repeat all commands that we typed in the previous section.

Some pragmatic users made some nice scripts that are doing everything automatically for you - download the sources from the CVS repository and install them. We will list the best here but it should be noted that installing E17 using these scripts is not supported by the Development Team.

The project leader, Carsten "Rasterman" Haitzler made the Get_E script, mainly for himself and he shared it with the community. It's very simple and will fetch and install only the most necessary libraries, E17 and the Entrance login manager (we will talk about it a bit later in this guide). Note that you will have to edit the script before use it just to customize what and how to install.

Brian 'morlenxus' Miculcy made the popular Easy_E17. It's quite easy to work with it as it provides command line options for a lot of things.

If using the easy_e17 script, there are some tips:

while easy_e17 automatically sets (if using bash) export PKG_CONFIG_PATH=/opt/e17/lib/pkgconfig, that is not remembered. If you want to compile your own e17 apps, you need to set that env variable so the ./configure can find the e17 libraries.

Also, if compiling your own libraries/apps from cvs into an existing easy_e17 install, to keep things clean (not messy & all over the place, ie /usr/local or /usr/local/bin) it can be handy to run autogen as so: ./autogen.sh --prefix /opt/e17 .This will install the new libs with the rest of your e17.

currently e17 is transitioning to pkg_config, though not all cvs apps have updated yet. They will have trouble running e17 commands in the make process (this can happen in easy_e17 as well). The most common error is not being able to locate ecore-config. To fix this simply run export PATH=/opt/e17/bin:$PATH to append e17's binary path to the current paths.

Retrieved from "http://wiki.enlightenment.org/index.php/E17_User_Guide/Scripts_for_automated_CVS_installation"