enlightenment/www-content
enlightenment
/
www-content
6
0
Fork 2
Code Issues Pull Requests 1 Projects Releases Wiki Activity

e16.txt: autogen -> configure 

The e16 tarball does not contain autogen.sh.
autoreconf would work but configure is still needed.
autogen.sh is for building from git.
This commit is contained in:
Kim Woelders 2022-06-13 22:13:46 +02:00
parent 7ba69d6bc9
commit 26afdbdcad
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pages/e16.txt
View File

@ -34,17 +34,17 @@ sudo apt install asciidoc build-essential libimlib2-dev libpango1.0-dev libpulse
Untar downloaded e16 tarballs (mainly you want e16 and themes) by ''tar zxf downloaded.file.tar.gz'' and then go into the directories created. Please see the README file in this directory for each project for additional information on dependencies, configuration, etc. Just remember that all our release tarballs come with configure set up so to compile you just need to do this in the source directory:
<code bash>
./autogen.sh
./configure
make
sudo make install
</code>
If autogen fails, you are likely missing a dependency - provide it. It should tell you what that dependency is.
If configure fails, you are likely missing a dependency - provide it. It should tell you what that dependency is.
Note that combination of lightdm + .xsession + e16 is known to work on Debian systems, while using e.g. gdm3 + .xsession was observed to cause problems with launching e16.
=== Running e16 locally ===
Note that you can build and run E16 only with local user privileges -- just provide arguments to autogen such as ''--prefix=/home/user/e'' or similar and run E16 from there. How to run it varies across different systems but often putting the path to binary into ~/.xinitrc will just work.
Note that you can build and run E16 only with local user privileges -- just provide arguments to configure such as ''--prefix=/home/user/e'' or similar and run E16 from there. How to run it varies across different systems but often putting the path to binary into ~/.xinitrc will just work.
----