hi William;
On 6 August 2012 14:48, William Deshaies <williamdesha...@hotmail.com> wrote:
> I open a bug report for tracking the change on the documentation:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=681300
>
> I'm wiling to do a patch, but I just need some clarification because, even
> if I enable egl backend via --enable-egl-backend option for configure, I
> can't use it. It say Unrecognizad input backend. Same for evdev.
the EGL backend is not an input backend: it's an output-only backend.
the input backends are:
x11
win32
osx
evdev
tslib (deprecated)
wayland
gdk
the windowing system backends are:
x11
win32
osx
wayland
egl
cex100
gdk
as you can see, some windowing system backends have input backends as
well, whereas other windowing systems don't and have to use extra
input backends; for instance, if you use the cex100 windowing system
backend you'll also have to use the evdev or the tslib input backend,
as the CEx100 platform only provides API on top of the EGL system to
get a native surface to render to. on the other hand, on X11, Windows,
and MacOS the windowing system API also provides a way to handle input
events coming from HCI devices like keyboards, pointers, tablets, or
touchscreens.
there are thus two different environment variables/configuration options:
- CLUTTER_BACKEND: used to select the windowing system backend
- CLUTTER_INPUT_BACKEND: used to select the input backend
you cannot mix and match, though; i.e. you cannot use the X11 input
backend with the Windows "output" backend.
if you are using an EGL-based windowing system (either fullscreen
framebuffer or through the Intel CEx100 platform libraries) then you
can opt to use the evdev or the tslib input backends.
hopefully this clarified the issue.
ciao,
Emmanuele.
>> Date: Sat, 4 Aug 2012 08:33:47 +0100
>> Subject: Re: Clutter 1.10.8: eglnative backend
>> From: eba...@gmail.com
>> To: williamdesha...@hotmail.com
>> CC: clutter-app-devel-list@clutter-project.org
>
>>
>> hi;
>>
>> On 3 August 2012 18:16, William Deshaies <williamdesha...@hotmail.com>
>> wrote:
>> > Finally solve my problem. I set the environnement variable
>> > CLUTTER_INPUT_BACKEND to NULL:
>> > $ export CLUTTER_INPUT_BACKEND='null'
>>
>> the 'null' input backend does exactly what it says on the tin: it
>> stops Clutter from handling any event; it's meant to be used for
>> porting purposes only, as well as on platforms that do not have any
>> HCI. if you want to handle events you will need to enable the evdev
>> input backend at compile time.
>>
>> > I think it would be a good idea to update the documentation in the
>> > Running
>> > Clutter section about this.
>>
>> yes, it would; care to submit a patch? :-)
>>
>> ciao,
>> Emmanuele.
>>
>> > ________________________________
>> > From: williamdesha...@hotmail.com
>> > To: clutter-app-devel-list@clutter-project.org
>> > Subject: Clutter 1.10.8: eglnative backend
>> > Date: Thu, 2 Aug 2012 18:32:57 +0000
>> >
>> >
>> > Hi,
>> >
>> > I'm trying to port my clutter 1.6.20 application to clutter 1.10.8, but
>> > I
>> > got the following error:
>> >
>> > Clutter-ERROR **: Unknown input backend
>> > Trace/breakpoint trap
>> >
>> > I usually use eglnative backend but its not present in the new clutter
>> > or
>> > cogl. Here is my old configure option:
>> >
>> > ./configure --prefix=%{_prefix} --host=arm-none-linux-gnueabi \
>> > --build=%{_build} --with-flavour=eglnative --with-gles=2.0 \
>> > --with-x=no --disable-xinput
>> >
>> > Here is the new configure option for clutter:
>> > ./configure --prefix=%{_prefix} --host=arm-none-linux-gnueabi \
>> > --build=%{_build} --enable-egl-backend --enable-deprecated \
>> > --with-x=no --disable-xinput
>> >
>> > Here is the Cogl configure option:
>> > ./configure --prefix=%{_prefix} --build=%{_build}
>> > --host=arm-none-linux-gnueabi \
>> > --enable-gles2 --disable-gl --enable-null-egl-platform
>> >
>> > I'm using a imx53 processor from Freescale with ARM architecture and
>> > LTIB.
>> >
>> > Any idea to solve this?
>> >
>> > Thanks
>> >
>> > William Deshaies
>> >
>> > _______________________________________________ clutter-app-devel-list
>> > mailing list clutter-app-devel-list@clutter-project.org
>> > http://lists.clutter-project.org/listinfo/clutter-app-devel-list
>> >
>> > _______________________________________________
>> > clutter-app-devel-list mailing list
>> > clutter-app-devel-list@clutter-project.org
>> > http://lists.clutter-project.org/listinfo/clutter-app-devel-list
>> >
>>
>>
>>
>> --
>> W: http://www.emmanuelebassi.name
>> B: http://blogs.gnome.org/ebassi/
>
> _______________________________________________
> clutter-app-devel-list mailing list
> clutter-app-devel-list@clutter-project.org
> http://lists.clutter-project.org/listinfo/clutter-app-devel-list
>
--
W: http://www.emmanuelebassi.name
B: http://blogs.gnome.org/ebassi/
_______________________________________________
clutter-app-devel-list mailing list
clutter-app-devel-list@clutter-project.org
http://lists.clutter-project.org/listinfo/clutter-app-devel-list
