> so yup. you need a host build and install of efl with tools like > eolian_gen and > edje_cc etc. so they are available in $PATH to then use these to > cross-build. > efl's build can and will do this in this case - but you need this > provided. i can't tho tbh cross building is painful. > if you are not used to it and know > that efl builds native tools to run during build > to generate code and data
Thanks a lot. This helped me much and I could compile efl with clickable and the efl binaries of Ubuntu noble in the build machine :-) > so it cant create a window. which is a pretty fatal thing that > cascades as > well.. your app doesnt check if window creation failed. tbh i never > do > either... if that fails all bets are off. > > elm will try a range of ways of making a window - x, then will, then > drm/kms > and fbcon etc. until all are exhausted and it fails the create. > depending on > what environment variables you have and are set this ordering may > vary a bit > and some of these will always fail or not be tried if the > engines/features are > not available in efl. > this problem still remains. I have to run it in Ubuntu with XWayland. Has someone experience with running efl applications under XWayland? Do I need special options here for XWayland? I have installed only the x11 engine in meson (and set up it with ELM_DISPLAY=x11)... I will check/ask the UBPorts developer what's the difference in application startup is between libertine (here it works) and normal clickable Ubuntu Apps. Hopefully I find a way to get it working... Best wishes, Max _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
