I just retested the default config for evas, on MacOS-X. ... Software X11...............: yes (Xlib: yes) (XCB: no)
And the default config for ecore: ... Ecore_X......................: no ... Ecore_Evas...................: yes Software X11...............: no So it looks like I was wrong about evas needing to specify the simple_X11 flag in the config. Looks like ecore needs the optional flags set. I'll update the wiki, but have one more test to do: I'm setting up a fresh OS install without the legacy of apps and libs on my main system, so that I can repeat the whole install process on a clean system. I'm sure I'll have some additional changes. I'll report what I find and update the wiki from that. I'll also use the order you recommended. Dave On Apr 19, 2010, at 1:08 PM, Vincent Torri wrote: > > > On Mon, 19 Apr 2010, Dave Ray wrote: > >>> 1) are you *sure* that e_dbus must be compiled *before* eina and >>> ecore ? >> >> No, definitely not. Some of the libs have an order dependency, some >> not. I would like to be more explicit but couldn't find >> documentation on the dependencies of all the libs, or the order to >> compile. This list was the result of trial and error. > > order: > > eina > eet > evas > ecore > embryo > edje > efreet > e_dbus > e17 > > efree, e_dbus and edje depend only on ecore (and its deps) so they > can be compiled in any order after ecore has been installed. > > embryo does not depend on anything but is usually compiled just > before edje, as only edje is using it. > > Btw, another question: did you try to compile and test elementary ? > >>> 2) why do you need --enable-simple-x11 when configuring evas ? >> >> e17 threw an error that software-X11 was not compiled into >> ecore_evas. >> >> I added this flag to evas initially, and then got a different e17 >> error that ecore was missing ecore_evas_software_X11. So I added >> the flag to ecore as well. >> >> EFL can be used without X11 in principle, to develop Cocoa apps >> without X11. So it's not unreasonable for software_X11 to be off by >> default. That's just a guess why I had to set the flag manually. > > if you just run evas configure (without any flag), in the configure > output, is the software Xlib enabled ? If not, paste in pastebin the > config.h file. There is a problem that must be fixed. The detection > should be automatic (see line 118 of evas configure.ac) > > The logic about Xlib in evas and ecore: > > a) evas builds the Xlib engine as a shared lib > > b) ecore builds ecore-x for the different functions about X > programming and ecore-evas Xlib part checks if > i) the Xlib evas engine is installed > ii) ecore-x is built. > > So if the Xlib evas engine or ecore-x are not built, ecore-evas will > not have the Xlib support and e17 will not work. > >>> 3) About the prerequiqites, you say that one must download them. >>> Where ? In the official web site of these libraries ? >> >> Yes. Should I provide links to those? > > well, see how i did for Windows: > > http://trac.enlightenment.org/e/wiki/EFLWindowsXP > > Vincent ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
