dan sinclair wrote:
If you have compiled the software x11 engine in with
HAVE_EVAS_ENGINE_SOFTWARE_X11_H it will try to use that by default. If that
fails, and you have HAVE_EVAS_ENGINE_FB_H defined when you compile it will try
to use the framebuffer. If that fails...well your boned.
Looks like I'm boned then! I don't even have X. My configure options are:
ecore: --without-x --disable-ecore-x
evas: --without-x
Both Evas and Edje are working fine on the framebuffer
(ecore_evas_fb_new(...)).
ewl/ewl-config.h has:
/* Define to 1 if you have the <Evas_Engine_FB.h> header file. */
#define HAVE_EVAS_ENGINE_FB_H 1
/* Define to 1 if you have the <Evas_Engine_GL_X11.h> header file. */
/* #undef HAVE_EVAS_ENGINE_GL_X11_H */
/* Define to 1 if you have the <Evas_Engine_Software_X11.h> header file. */
/* #undef HAVE_EVAS_ENGINE_SOFTWARE_X11_H */
Note that these defines are used in ewl_init (ewl_misc.c) to determine
whether ecore_x_init or ecore_fb_init is called, but not in
ewl_window_realise_cb (ewl_window.c). Here, the evas render method is
obtained from "ewl_config_render_method_get()", which in turn uses
ecore_config_string_get("/ewl/evas/render_method") with a default of
"software_x11".
Your other option is to do something like:
ewl_test --ewl-fb
ewl_test --ewl-software-x11
I've tried --ewl-fb, but to no avail. Again, in the code this only
seems to affect ecore_{fb,x}_init();
--
Simon Poole
www.appliancestudio.com
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
