WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=71532158430deffc3aa4454e471141d8b2bb938d
commit 71532158430deffc3aa4454e471141d8b2bb938d
Author: Raster ras...@rasterman.com
Date: Tue May 19 02:41:56 2015 -0700
Wiki page download changed with summary [] by Raster
---
pages/download.txt | 22 ++
1 file changed, 6 insertions(+), 16 deletions(-)
diff --git a/pages/download.txt b/pages/download.txt
index 10c8721..f3e3d89 100644
--- a/pages/download.txt
+++ b/pages/download.txt
@@ -5,19 +5,16 @@ We place all of our releases here:
* [[http://download.enlightenment.org/rel/|download.enlightenment.org]]
-When compiling from source, our core libraries likely should be build
-in this order:
+For a list of dependencies and general build infor take a look at
[[docs-efl-start]]. But just use the below configure command instead of
autogen.sh. Everything else is the same.
+
+When compiling from source, our core libraries likely should be build in this
order:
* EFL
* Evas Generic Loaders
* Emotion Generic Players
* Elementary
-After this build applications however you like (e.g. Enlightenment,
-Terminology etc). Please see the README files for projects for
-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:
+After this build applications however you like (e.g. Enlightenment,
Terminology etc). Please see the README files for projects for 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:
code bash
./configure
@@ -33,16 +30,9 @@ Our latest releases are:
Source
-Out source code is developed collaboratively in a pretty typical open
-source manner. Our master branches are where all new development goes
-into. We try and keep master working and usable daily, as developers
-generally are living off master themselves and so bugs affect
-developers directly and immediately. Sometimes issues happen, but
-they tend to get fixed rapidly.
+Out source code is developed collaboratively in a pretty typical open source
manner. Our master branches are where all new development goes into. We try and
keep master working and usable daily, as developers generally are living off
master themselves and so bugs affect developers directly and immediately.
Sometimes issues happen, but they tend to get fixed rapidly.
-If you want to track the latest and greatest, please see our git
-repositories. If you have issues please refer to our [[contact]]
-page to get in touch with us.
+If you want to track the latest and greatest, please see our git repositories.
If you have issues please refer to our [[contact]] page to get in touch with us.
All our git repositories are listed on:
--
