forked from enlightenment/enlightenment
95 lines
3.7 KiB
Plaintext
95 lines
3.7 KiB
Plaintext
+-----------------------------------------------------------------------------+
|
|
| Enlightenment 0.17.pre CVS Code.... |
|
|
+-----------------------------------------------------------------------------+
|
|
The Rasterman - raster@rasterman.com
|
|
|
|
*******************************************************************************
|
|
**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
|
|
*******************************************************************************
|
|
|
|
This is the source code for Enlightenment 0.17 - If you got this you got it
|
|
from Enlightenment's CVS repository - or from someone who took it out of the
|
|
CVS repository.
|
|
|
|
The CVS repository is full of code *IN DEVELOPMENT* - that often means it's
|
|
in the middle of being worked on and may install strange things in strange
|
|
places, make a mess, and may not even be compatible with a final release. If
|
|
you at all use this code, you are HEAVILY URGED, when it is finally released,
|
|
to remove all traces of anything this CVS code base has installed on your
|
|
system (it is COMPLETELY up to you to keep track of that - do NOT expect any
|
|
help), and then install the full release on a cleaned system. Don't come
|
|
asking "can I just keep using CVS" once things are released - that is the
|
|
reason I put this paragraph here - so you don't ask. The answer is the same
|
|
as above - if there is a proper final release use that. CVS is really only
|
|
for those heavily hacking on the code, or whose curiosity is too much to resist
|
|
not giving it a look and try.
|
|
|
|
Now we have that warning over and done with. How to build and install from
|
|
CVS?
|
|
|
|
$ ./autogen.sh && make
|
|
$ su
|
|
Password:
|
|
<- as root ->
|
|
# make install
|
|
|
|
You should be able to use the binary of enlightenment as a window manager.
|
|
|
|
you might be advised for cleanliness to do
|
|
$ ./autogen.sh --prefix=/usr/local/e-17
|
|
|
|
so it installs relative to the /usr/local/e-17 directory and keeps all the
|
|
e-17 development code and data in that tree so it is easily removed when the
|
|
time comes.
|
|
|
|
-------------------------------------------------------------------------------
|
|
|
|
NOTES: Read these carefully!
|
|
|
|
Enlightenment only handles a small subset of ICCCM and thus will have bugs -
|
|
some applications will not behave correctly and may appear in odd spots or
|
|
not resize or place themselves properly etc. Expect this - it's code being
|
|
worked on. Just be happy it does as much as it already does.
|
|
|
|
Enlightenment RELIES on lots of libraires that have been written. Ecore,
|
|
Ebits, Evas, Edb, Imlib2, Efsd just to mention a few. Especially Ebits,
|
|
Ecore, Efsd, Ferite, and Evas change in CVS often - you will need the absolute
|
|
latest of these if you wish Enlightenment 0.17 code to run properly or compile.
|
|
If you update Enlightenment from CVS update these too to get any changes they
|
|
have in their trees.
|
|
|
|
If you want to compile & install E 0.17 you probably install the packages
|
|
Enlightenment needs in this order:
|
|
|
|
(*) imlib2
|
|
(*) edb
|
|
(*) imlib2_loaders
|
|
(*) evas
|
|
(*) ebits
|
|
(*) ecore
|
|
(*) efsd
|
|
(*) ferite (optional for now, but recommended)
|
|
(*) e17
|
|
|
|
since you got Enlightenment from CVS (if you didn't you should have) you must
|
|
get all of the above from CVS - because the libraries Enlightenment depends on
|
|
keep being updated as bugs are found and new features needed - and often they
|
|
are not released for a while until things settle down, so make sure you get
|
|
the latest of these from CVS.
|
|
|
|
before you start installing the some of the above, some of the packages you
|
|
will need - if you don't already have them, are:
|
|
|
|
(*) freetype (1.1, 1.2 or 1.3 ... NOT 2.0)
|
|
(*) libxml2
|
|
(*) libpcre
|
|
(*) fam
|
|
|
|
and possibly ...
|
|
|
|
(*) libjpeg
|
|
(*) libpng
|
|
(*) zlib
|
|
(*) libtiff
|
|
(*) libungif
|