[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
howtos:window_managers:installing_e17 [2012/11/22 09:05 (UTC)] – [Sources] ngc891howtos:window_managers:installing_e17 [2018/10/23 16:17 (UTC)] – [Compilation] trite
Line 1: Line 1:
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
 +<!-- Reviewed 2012-02-18 by Hazel -->
 ====== Using Enlightement DR17 with Slackware ====== ====== Using Enlightement DR17 with Slackware ======
  
 ===== What is E17? ===== ===== What is E17? =====
  
-[[http://www.enlightenment.org/p.php?p=about&l=en | Enlightenment DR17]] (E17) is the long awaited successor of E16, a window manager which was distributed in Slackware 10 years ago. +[[http://www.enlightenment.org/p.php?p=about&l=en | Enlightenment DR17]] (E17) is the long awaited successor of E16, a [[slackware:window_manager|window manager]] which was distributed in Slackware 10 years ago. 
-It is classed as a "desktop shell" providing the things you need to operate your desktop (or laptop), but is not a whole application suite. This covered launching applications, managing their windows and doing other system tasks like suspending, reboots, managing files, etc.+It is classed as a "desktop shell"providing the things you need to operate your desktop (or laptop), but not a whole suite of applications. This includes launching applications, managing their windowsand doing other system tasks like suspending, rebooting, managing files, etc.
  
-E17 doesn't come alone. Actually, it uses the [[http://trac.enlightenment.org/e/wiki/EFLOverview | Enlightenment Foundation Libraries]] (EFL) which can be used to develop other applications like in the Qt/KDE world for instance. There are, as in November 2012, 15 libraries in EFL and a lot of external modules or applications that can be used with E17.+E17 doesn't come alone. Actually, it uses the [[http://trac.enlightenment.org/e/wiki/EFLOverview | Enlightenment Foundation Libraries]] (EFL) which can be used to develop other applications like in the Qt/KDE world for instance. There are, as in February 2013, 15 libraries in EFL and a lot of external modules or applications that can be used with E17.
  
 ===== Installing E17 ===== ===== Installing E17 =====
Line 15: Line 16:
 === SlackE17 === === SlackE17 ===
  
-The easiest and fastest way to get E17 running on Slackware is to install the E17 packages from the [[http://slacke17.sourceforge.net/ | SlackE17 project]]. You just need to have the last release of Slackware or Slackware64.+The easiest and fastest way to get E17 running on Slackware is to install the E17 packages from the [[http://slacke17.sourceforge.net/ | SlackE17 project]]. You just need to have the latest release of SlackwareSlackware64 or ArmedSlack.
  
-Just [[http://sourceforge.net/projects/slacke17/files/slacke17/ | download]] the tarball corresponding to your architecture (i486 or x86_64), unpack it and read the doc. To install the packages, you have several options:+Just [[http://sourceforge.net/projects/slacke17/files/slacke17/ | download]] the tarball corresponding to your architecture (i486x86_64 or ARM), unpack it and read the doc. To install the packages, you have several options:
  
   * Install everything using:   * Install everything using:
Line 29: Line 30:
  
 ==== Compilation ==== ==== Compilation ====
 +
 +First you need to install the dependencies needed to compile Enlightenment. These can be found in SlackBuilds-website or with sbopkg:
 +
 +  * check
 +
 +  * lua
 +
 +  * luajit
 +
 +  * bullet
 +
 +
 +Once you have those packages installed we can proceed to make a build directory and commence with the fun stuff!
 +
 +<code bash>
 + # mkdir -p /build/e22/core
 +
 + # cd /build/e22/core
 +
 + # git clone https://git.enlightenment.org/core/efl.git
 +
 + # git clone https://git.enlightenment.org/core/enlightenment.git
 +
 + # cd /build/e22/core/efl
 +
 + # ./autogen.sh --prefix=/opt/e22 --disable-systemd --disable-avahi
 +</code>
 +
 +Make symlink for dbus (installer tells you to do this so please check output if it has been updated just to be sure).
 +<code bash>
 + # ln -s /opt/e22/share/dbus-1/services/org.enlightenment.Ethumb.service /usr/share/dbus-1/services/org.enlightenment.Ethumb.service
 +
 + # make && make install
 +</code>
 +
 +
 +Now we need to add Enlightenment library directory to the system so it knows where to look for the libraries.
 +<code bash>
 + # echo "/opt/e22/lib" >> /etc/ld.so.conf
 +</code>
 +
 +
 +Load the new configuration.
 +<code bash>
 + # ldconfig
 +</code>
 +
 +
 +An environmental variable need to be set for PKGCONFIG, this is only needed when building and doesnt need to be permanent.
 +<code bash>
 + # export PKG_CONFIG_PATH=/opt/e22/lib/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig
 +</code>
 +
 +
 +Add enlightenment bin to PATH for build, also make it persist after reboot.
 +<code bash>
 + # export PATH=/opt/e22/bin:$PATH
 +
 + # vi /etc/profile
 +</code>
 +Add "/opt/e22/bin" to your PATH.
 +
 +
 +
 +Start building Enlightenment.
 +<code bash>
 + # cd /build/e22/core/enlightenment
 +
 + # meson --prefix=/opt/e22 -Dsystemd=false -Davahi=false . build
 +
 + # meson configure build
 +
 + # ninja -C build install
 +</code>
 +
 +
 +(Optional, build Terminology. Terminology is the default terminal in Enlightenment.)
 +<code bash>
 + # mkdir /build/e22/apps
 +
 + # cd /build/e22/apps
 +
 + # git clone https://git.enlightenment.org/apps/terminology.git
 +
 + # cd terminology
 +
 + # meson --prefix=/opt/e22 . build
 +
 + # meson configure build
 +
 + # ninja -C build install
 +</code>
 +
 +
 +To make your sessionmanager find Enlightenment you need to create a .desktop file in the right directory.
 +<code bash>
 + # vi /usr/share/xsession/enlightenment.desktop
 +</code>
 +
 +
 +Should look something like this (please check already existing .desktop files for other language examples and please add relevant lines for your language):
 +
 +<code bash>
 +[Desktop Entry] 
 +
 +Encoding=UTF-8 
 +
 +Type=XSession 
 +
 +Exec=/opt/e22/bin/enlightenment_start 
 +
 +TryExec=/opt/e22/bin/enlightenment_start 
 +
 +DesktopNames=Enlightenment 
 +
 +Name=Enlightenment 
 +
 +Comment[en_GB]=Enlightenment by Enlightenment
 +
 +Comment[sv]=Enlightenment av Enlightenment 
 +
 +X-KDE-PluginInfo-Version=0.22.9
 +</code>
 +
 +If you want to start enlightenment with startx (xinit):
 +/etc/X11/xinit/xinitrc.e22
 +<code>
 +#!/bin/sh
 +
 +userresources=$HOME/.Xresources
 +usermodmap=$HOME/.Xmodmap
 +sysresources=/etc/X11/xinit/.Xresources
 +sysmodmap=/etc/X11/xinit/.Xmodmap
 +
 +# merge in defaults and keymaps
 +
 +[ -f $sysresources ] && xrdb -merge $sysresources
 +[ -f $sysmodmap ] && xmodmap $sysmodmap
 +[ -f $userresources ] && xrdb -merge $userresources
 +[ -f $usermodmap ] && xmodmap $usermodmap
 +
 +if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
 +  export DESKTOP_SESSION="e22"
 +  exec ck-launch-session dbus-launch --exit-with-session enlightenment_start
 +else
 +  export DESKTOP_SESSION="e22"
 +  exec enlightenment_start
 +fi
 +</code>
 +
  
 === SlackE17 === === SlackE17 ===
Line 57: Line 208:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must remove the tag-word "template" below before saving your new page --> <!-- You must remove the tag-word "template" below before saving your new page -->
-{{tag>howtos e17}}+{{tag>howtos e17 author_ngc891 }}
 howtos:window_managers:installing_e17 ()