On Thu, 22 Feb 2018 22:13:29 + Mike Blumenkrantz
wrote:
> To be precise, theREADME.wayland file says "This Readme does not address
> the dependencies needed to enable Wayland in EFL. If you require any
> information for that..." meaning that the link is only
To be precise, the README.wayland file says "This Readme does not address
the dependencies needed to enable Wayland in EFL. If you require any
information for that..." meaning that the link is only a reference for
dependency information. The README.wayland file does accurately cover all
necessary
On Thu, 22 Feb 2018 18:32:56 + Mike Blumenkrantz
wrote: >
> It seems that this documentis tremendously out of date. If you are looking
> to run Enlightenment as a Wayland compositor, I would recommend following
> the instructions here
>
It seems that this document is tremendously out of date. If you are looking
to run Enlightenment as a Wayland compositor, I would recommend following
the instructions here
https://git.enlightenment.org/core/enlightenment.git/tree/README.wayland
On Thu, Feb 22, 2018 at 1:16 PM Antonio Palladini
Hello Devs,
I have tried to compile efl with wayland support but got the following
error ;
CC
lib/ecore_wayland/lib_ecore_wayland_libecore_la-ecore_wl.lo
In file included from lib/ecore_wayland/ecore_wl_private.h:10:0, from
lib/ecore_wayland/ecore_wl.c:6:
Hi,
I have already checkout from svn source to try the EFLs. I checked the
easy_e17.sh script that is suggested to install e17. My aim is
installing just the libraries to check what i can do with them so i
try manually running ./autogen.sh; make; sudo make install for each
directory mentioned at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 30 Dec 2008 16:44:48 +0200
Oguz Yarimtepe comp@gmail.com wrote:
So should i run with a parameter or do autogen.sh detects the fb
related libraries and enables it?
Before ecore, i installed evas by runnig ./autogen.sh --enable-fb
Hey,
Hadn't been able to compile evas for some time, been trying weekly, then the
other day it worked :) thanx
nice to hear :) I'll certainly add a gdi engine, so that an engine will
always work, whatever the configuration / installation of the user are.
And of course, the direct3d engine,
Creating library file: .libs/libecore.dll.a
.libs/ecore_getopt.o: In function `ecore_getopt_help':
d:/enlightenment/ecore/src/lib/ecore/ecore_getopt.c:577: undefined reference
to `__imp__ecore_app_args_get'
.libs/ecore_getopt.o: In function `ecore_getopt_parse':
hi again,
Hadn't been able to compile evas for some time, been trying weekly, then
the other day it worked :) thanx
So just to let relevant parties know ecore gets stuck here:
$ make
make all-recursive
make[1]: Entering directory `/d/enlightenment/ecore'
Making all in src
make[2]: Entering
10 matches
Mail list logo