I never met this problem.
But you can try to install llvm-3.3-dev.
thanks
-Original Message-
From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
Behalf Of Srivardhan M S
Sent: Thursday, March 27, 2014 1:13 PM
To: Zhang, Xiong Y
Cc: wayland-devel@lists.freedesktop.o
Thanks Zhang,
Now am struck with another issue:
configure: error: Could not find llvm shared libraries:
Please make sure you have built llvm with the --enable-shared option
and that your llvm libraries are installed in /usr/lib/llvm-2.9/lib
If you have installed your llvm libraries to a different
You can build Mesa with --disable-dri3
thanks
-Original Message-
From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
Behalf Of Srivardhan M S
Sent: Thursday, March 27, 2014 12:25 PM
To: wayland-devel@lists.freedesktop.org
Subject: Need help in builing Mesa
Hi,
I
Hi,
I am new to Wayland. I am following the instructions in the link
http://wayland.freedesktop.org/building.html to build wayland. I
successfully cloned wayland and drm and compiled them. But am struck
in mesa.
I've cloned the mesa code. When I run the autogen.sh as in the
instructions, I get fo
Hi, Pq
The information to identify the unique mode: width, height and refresh are
enough? Not enough in theory. But is enough in real world. I have checked with
xrandr. Read the following comment.
Welcome any comment for that.
Thanks
>> +
>> +
>> +
>> +Set the mode of output.
>
Both functions accept a series of event types/codes tuples, terminated by -1.
For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used
as a property to enable.
The _abs function als takes an array of absinfo, with absinfo.value
determining the axis to change. If none are given
There certainly should be no need to worry about multiple threads from
the same client. I think you can work on the assumption that the
programmer who wrote the client is not insane! This is the way commit
for wl_surface works, right?
The per-client pending mode is probably cleanest, but I sus
On 03/26/2014 03:32 PM, Pekka Paalanen wrote:
On Tue, 25 Mar 2014 19:47:21 +0100
Mario Kleiner wrote:
On 03/07/2014 04:09 PM, Pekka Paalanen wrote:
From: Pekka Paalanen
This is quick write-up of
http://cgit.collabora.com/git/user/pq/weston.git/tree/buffer-queue3.txt?h=buffer-queue-spec
How
On Tue, 25 Mar 2014 19:47:21 +0100
Mario Kleiner wrote:
> On 03/07/2014 04:09 PM, Pekka Paalanen wrote:
> > From: Pekka Paalanen
> >
> > This is quick write-up of
> > http://cgit.collabora.com/git/user/pq/weston.git/tree/buffer-queue3.txt?h=buffer-queue-spec
> >
> > How would this idea feel?
>
?Hello,
In a previous discussion on this ML [0] and blog article [1], Martin Peres
explained why Wayland should distinguish between normal and privileged clients
and what the security requirements for Wayland are. After that, I spent some
time thinking about how to handle the processes of autho
Yes. I'd say that realistically, you should never have more than one client
trying to set the mode at once. If you somehow do, your machine is already
messing up in some way. No need to design for a broken edge case in the
protocol.
Relying on message ordering is fine. We, of course, still want a
Hi Everyone,
Ozone-Wayland team is happy to announce a new source release today based on
Chromium M35[1]. Besides the usual fixes, this release saw new features being
added to Ozone-Wayland:
1.Virtual keyboard support. Contributed by Joone Hur.
2.Touch support. Contributed by Patrick Heeb.
3.x
On Wed, 26 Mar 2014 10:15:31 +
"Wang, Quanxian" wrote:
> Thanks, Pq
>
> >-Original Message-
> >From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
> >Behalf Of Pekka Paalanen
> >Sent: Wednesday, March 26, 2014 3:54 PM
> >To: Wang, Quanxian
> >Cc: wayland-devel
Thanks, Pq
>-Original Message-
>From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org] On
>Behalf Of Pekka Paalanen
>Sent: Wednesday, March 26, 2014 3:54 PM
>To: Wang, Quanxian
>Cc: wayland-devel@lists.freedesktop.org
>Subject: Re: weston: weston randr protocol for testin
On Tue, Mar 25, 2014 at 09:45:56PM +0100, Jonas Ådahl wrote:
> Signed-off-by: Jonas Ådahl
> ---
> test/touch.c | 43 +++
> 1 file changed, 43 insertions(+)
>
> diff --git a/test/touch.c b/test/touch.c
> index 61d8762..4a6af21 100644
> --- a/test/touch.c
>
On Tue, Mar 25, 2014 at 09:45:54PM +0100, Jonas Ådahl wrote:
> Add one test that checks uniqueness of seat slots when having multiple
> devices with active touch points.
>
> Add one test that checks that libinput drops touch points when it could
> not represent them with a seat wide slot.
>
> Thi
On Wed, Mar 26, 2014 at 06:29:59PM +1000, Peter Hutterer wrote:
> On Wed, Mar 26, 2014 at 09:20:27AM +0100, Jonas Ådahl wrote:
> > On Wed, Mar 26, 2014 at 06:05:19PM +1000, Peter Hutterer wrote:
> > > On Tue, Mar 25, 2014 at 09:45:52PM +0100, Jonas Ådahl wrote:
> > > > Signed-off-by: Jonas Ådahl
>
On Wed, Mar 26, 2014 at 09:24:08AM +0100, Jonas Ådahl wrote:
> On Wed, Mar 26, 2014 at 06:02:46PM +1000, Peter Hutterer wrote:
> > On Tue, Mar 25, 2014 at 09:45:55PM +0100, Jonas Ådahl wrote:
> > > libinput currently handles 16 per device touch points. Test that we
> > > behave as expected when a d
On Wed, Mar 26, 2014 at 09:20:27AM +0100, Jonas Ådahl wrote:
> On Wed, Mar 26, 2014 at 06:05:19PM +1000, Peter Hutterer wrote:
> > On Tue, Mar 25, 2014 at 09:45:52PM +0100, Jonas Ådahl wrote:
> > > Signed-off-by: Jonas Ådahl
> >
> > patch looks good, but I do wonder if it'd be better to just dyna
On Wed, Mar 26, 2014 at 06:02:46PM +1000, Peter Hutterer wrote:
> On Tue, Mar 25, 2014 at 09:45:55PM +0100, Jonas Ådahl wrote:
> > libinput currently handles 16 per device touch points. Test that we
> > behave as expected when a device has an even higher number of active
> > touch points.
> >
> >
On Wed, Mar 26, 2014 at 06:05:19PM +1000, Peter Hutterer wrote:
> On Tue, Mar 25, 2014 at 09:45:52PM +0100, Jonas Ådahl wrote:
> > Signed-off-by: Jonas Ådahl
>
> patch looks good, but I do wonder if it'd be better to just dynamically
> allocate slots based on the number of touches. A quick glance
On Tue, Mar 25, 2014 at 09:45:52PM +0100, Jonas Ådahl wrote:
> Signed-off-by: Jonas Ådahl
patch looks good, but I do wonder if it'd be better to just dynamically
allocate slots based on the number of touches. A quick glance shows we don't
really need this a fixed length anyway, MAX_SLOTS is unnec
On Tue, Mar 25, 2014 at 09:45:55PM +0100, Jonas Ådahl wrote:
> libinput currently handles 16 per device touch points. Test that we
> behave as expected when a device has an even higher number of active
> touch points.
>
> Signed-off-by: Jonas Ådahl
> ---
> test/touch.c | 50 +
On Wed, Mar 26, 2014 at 08:40:43AM +0100, Jonas Ådahl wrote:
> On Wed, Mar 26, 2014 at 05:30:14PM +1000, Peter Hutterer wrote:
> > On Wed, Mar 26, 2014 at 07:45:32AM +0100, Michael Schellenberger Costa
> > wrote:
> > > I might be dumb but doesnt this require motion between clicks?
> > >
> > > In
On Wed, 26 Mar 2014 06:47:50 +
"Wang, Quanxian" wrote:
> Hi, Pq
>
> In weston randr v2, I don't include the following question. I am still in
> confused. Sorry about that.
>
> >-Original Message-
> >From: Pekka Paalanen [mailto:ppaala...@gmail.com]
> >Sent: Saturday, March 22, 2014
On Wed, Mar 26, 2014 at 05:30:14PM +1000, Peter Hutterer wrote:
> On Wed, Mar 26, 2014 at 07:45:32AM +0100, Michael Schellenberger Costa wrote:
> > I might be dumb but doesnt this require motion between clicks?
> >
> > In that case you would lose for example track balls which do not
> > necessary
On Wed, Mar 26, 2014 at 07:45:32AM +0100, Michael Schellenberger Costa wrote:
> I might be dumb but doesnt this require motion between clicks?
>
> In that case you would lose for example track balls which do not
> necessary move between clicks.
this is for touch events only here, and the only way
hey, sorry about the delay, I got moved to other stuff for a while and only
now just picked up libinput again.
On Sat, Feb 22, 2014 at 03:33:26PM +0600, Alexander E. Patrakov wrote:
> 2014-02-21 5:26 GMT+06:00 Peter Hutterer :
> > On Fri, Feb 21, 2014 at 01:29:05AM +0600, Alexander E. Patrakov wro
28 matches
Mail list logo
