forked from enlightenment/enlightenment
Carsten Haitzler
4b4a51d189
now e only uses elementary's theme. this is to stop the bitrot and forking of e's theme vs the unified elm theme that has everything for e in it already. this obviously makes elm a requirement of e18 on, and this also notes that emotion is always in efl these days, so its no longer an option, and ecore-imf is no longer used as edje does the entires now itself. in future it'll all be elm. this is a major unification point for themes for elm and e. this will need some testing, but everything seems to work day-to-day, but theme selector is untested. this also removes the theme selector for splash as that is now simply unified with the same theme as everything else. |
||
---|---|---|
config | ||
data | ||
doc | ||
m4 | ||
po | ||
src | ||
.arcconfig | ||
.gitignore | ||
.mailmap | ||
AUTHORS | ||
BUGS | ||
COPYING | ||
ChangeLog | ||
INSTALL | ||
Makefile.am | ||
NEWS | ||
README | ||
autogen.sh | ||
configure.ac | ||
enlightenment.pc.in | ||
enlightenment.spec.in | ||
netwm.txt | ||
x-ui.sh | ||
xdebug.sh |
README
Enlightenment 0.17.99 - Development on the way to 0.18. Requirements: ------------- Must: libc libm libX11 libXext evas ecore ecore-evas ecore-file ecore-ipc ecore-con ecore-imf ecore-x edje eet embryo efreet e_dbus eio xcb xcb-shape xcb-keysyms [png loader in evas, jpeg loader in evas, eet loader in evas, software_x11 engine in evas, buffer engine in evas] NOTE: Users of DR16 will need to rename the $prefix/bin/enlightenment file prior to installing DR17 or it will be overwritten. You can also use the configure --prefix option to put e17 in a separate tree of its own (recommended) like: ./configure --prefix=/usr/local/e17 You will, as usual, need to add the subsequent bin dir to your $PATH etc. NOTES: * do NOT use -mfpmath=sse in CFLAGS - we are not sure, but it may have bugs and screws up things in edje, evas and e17. if your gcc uses this by default (which apparently gcc4.x does on amd64), turn it off with a -fpmath=387 in your CFLAGS. * your freetype2 version must be > 2.1.7 * if you do not want security issues make sure sysactions.conf is in /etc/enlightenment (not PREFIX/etc/enlightenment) as this is the first place it looks at. This file is intended to be customized by packagers and system integrators to match your policies and scripts/tools.