How to build weston/wayland with debug information?

Dear All, How can I build wayland/weston with debug information in it? I mean debug build of wayland/weston. I am using weston 1.8.0 and building using yocto based environment. Thanks & Regards, Vikas ___ wayland-devel mailing list

Re: [PATCH wayland 2/2] protocol: Add DnD actions

What does "ask" mean? I would think "ask" is implied by the fact that more than one action is provided. Maybe an explanation as to what the drop target should do with these combinations and how they differ from each other (just write what the drop target should do for each): MOVE MOVE+ASK

Re: [PATCH libinput] tablet: invert tilt axes when left-handed is enabled

On Mon, Dec 21, 2015 at 1:24 PM, Peter Hutterer wrote: > On Mon, Dec 21, 2015 at 10:12:24AM -0800, Bill Spitzak wrote: > > I find it hard to believe this is what client programs will want. A > > painting program wants the axis of an elongated brush to be perpendicular

Re: [RFC v2] Add Primary Selection Protocol Version 1

On Fri, Dec 18, 2015 at 9:03 AM, Lyude wrote: > Signed-off-by: Lyude > --- > Changes > * Add new interfaces to replace reuse of wl_data_(source|offer) > * Get rid of the selection changed event since we now have our own

Re: [PATCH weston 5/5] dnd: Turn into a full blown example

On Mon, Dec 21, 2015 at 5:33 PM, Carlos Garnacho wrote: > In order to keep things simple, weston-dnd made a few choices that > turn out to be unrealistic, a few tweaks have been done to make it > less of a playground demo: > > - It now caters for copy/move operations, instead

Re: weston flip a null frame first before start launcher

On Thu, Dec 17, 2015 at 3:05 AM, Pekka Paalanen wrote: > On Thu, 17 Dec 2015 18:27:48 +0800 > zou lan wrote: > > > Hi pekka & others > > > > I find weston flip a null frame before start the launcher > > weston-desktop-shell. So there is always a

Re: [PATCH libinput] tablet: invert tilt axes when left-handed is enabled

I find it hard to believe this is what client programs will want. A painting program wants the axis of an elongated brush to be perpendicular to the tilt will work correctly only if *both* axes are flipped (as your code appears to be doing). But it will get "which edge is nearer" backward if it

Re: [PATCH wayland 1/2] protocol: Improve data source notification around DnD progress

Hey, On Wed, Dec 23, 2015 at 5:47 AM, Jonas Ådahl wrote: > Hi again, > > I was reading an E-mail in another thread that brought up different > types of backward compatibility promises, and it made me think of a > potential issue. I'm commenting inline close to the relevant

Re: [PATCH wayland 1/2] protocol: Improve data source notification around DnD progress

On Wed, Dec 23, 2015 at 12:05:35PM +0100, Carlos Garnacho wrote: > Hey, > > On Wed, Dec 23, 2015 at 3:07 AM, Jonas Ådahl wrote: > > On Tue, Dec 22, 2015 at 04:46:37PM +0100, Carlos Garnacho wrote: > >> Hey, > >> > >> On Tue, Dec 22, 2015 at 2:55 PM, Jonas Ådahl

Re: [RFC v2] Add Primary Selection Protocol Version 1

On 18 December 2015 at 20:34, Bill Spitzak wrote: > > > On Fri, Dec 18, 2015 at 9:03 AM, Lyude wrote: >> >> Signed-off-by: Lyude >> --- >> Changes >> * Add new interfaces to replace reuse of

RE: How to build weston/wayland with debug information?

Oh! Forgot that yocto generated debug packages as well. Regards, Vikas -Original Message- From: "Vikas Patil" Sent: ‎12/‎23/‎2015 3:26 PM To: "wayland mailing list" Subject: How to build weston/wayland with debug information?

[PATCH weston 4/5] data-device: Implement compositor-chosen actions

Set up a keyboard grab during drag-and-drop, so we can translate modifiers into preferred actions. The compositor chosen action is stored in the current weston_data_source in order to make it accessible to the source/offer at the time of calculating the new action, but would conceptually be part

[PATCH wayland v8 1/2] protocol: Improve data source notification around DnD progress

Currently, there's no means for the DnD origin to know whether the destination is actually finished with the DnD transaction, short of finalizing it after the first transfer finishes, or leaking it forever. But this poses other interoperation problems, drag destinations might be requesting

[PATCH wayland v8 2/2] protocol: Add DnD actions

These 2 requests have been added: - wl_data_source.set_actions: Notifies the compositor of the available actions on the data source. - wl_data_offer.set_actions: Notifies the compositor of the available actions on the destination side, plus the preferred action. Out of the data from these

[PATCH weston v7 2/5] data-device: Implement DnD actions

The policy in weston in order to determine the chosen DnD action is deliberately simple, and is probably the minimals that any compositor should be doing here. Besides honoring the set_actions requests on both wl_data_source and wl_data_offer, weston now will emit the newly added "action" events

[PATCH weston v5 1/5] data-device: Implement DnD progress notification

Weston now sends wl_data_source.dnd_drop_performed and .dnd_finished in order to notify about the different phases of DnD. wl_data_source.cancelled is also used as mentioned in the docs, being emitted also on DnD when the operation is meant to fail (eg. source and dest didn't agree on a

[PATCH weston 2/5] data-device: Implement DnD actions

The policy in weston in order to determine the chosen DnD action is deliberately simple, and is probably the minimals that any compositor should be doing here. Besides honoring the set_actions requests on both wl_data_source and wl_data_offer, weston now will emit the newly added "action" events

[PATCH weston 5/5] dnd: Turn into a full blown example

In order to keep things simple, weston-dnd made a few choices that turn out to be unrealistic, a few tweaks have been done to make it less of a playground demo: - It now caters for copy/move operations, instead of just move, which still remains the default nonetheless. - As "move" operations

[PATCH weston 1/5] data-device: Implement DnD progress notification

Weston now sends wl_data_source.dnd_drop_performed and .dnd_finished in order to notify about the different phases of DnD. wl_data_source.cancelled is also used as mentioned in the docs, being emitted also on DnD when the operation is meant to fail (eg. source and dest didn't agree on a

[PATCH weston 3/5] client: Add DnD cursors to the managed cursors list

That way we'll be able to set the corresponding pointer surface to a current DnD operation. Signed-off-by: Carlos Garnacho Reviewed-by: Jonas Ådahl --- clients/window.c | 16 clients/window.h | 3 +++ 2 files changed, 19 insertions(+)

Re: inserting a "wl_display" object

Hi, I am unable to understand your question. Is ti not possible for you to call the wl_display_connect() API?. It will give the wl_display object right?. Regards, Madan On Tue, Dec 22, 2015 at 7:34 AM, wrote: > Hello, I'm new to Wayland. I need a "wl_display" object in

[PATCH wayland 2/2] protocol: Add DnD actions

These 2 requests have been added: - wl_data_source.set_actions: Notifies the compositor of the available actions on the data source. - wl_data_offer.set_actions: Notifies the compositor of the available actions on the destination side, plus the preferred action. Out of the data from these

[PATCH wayland 1/2] protocol: Improve data source notification around DnD progress

Currently, there's no means for the DnD origin to know whether the destination is actually finished with the DnD transaction, short of finalizing it after the first transfer finishes, or leaking it forever. But this poses other interoperation problems, drag destinations might be requesting

Re: [PATCH] clients: Fix compositor version check for WL_SURFACE_DAMAGE_BUFFER_SINCE_VERSION

Le 20/12/2015 13:41, Chris Michael a écrit : > Signed-off-by: Chris Michael > --- > clients/simple-damage.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/clients/simple-damage.c b/clients/simple-damage.c > index 37a81f5..24c67cc 100644 >

[PATCH 3/4] compositor: Verify that the maximum number of outputs is not exceeded

output_id_pool is defined as a uint32_t, thus ffs() provides a range of 1-32 available id numbers. When the 33rd output is enabled, Weston will set the ID to (unsigned)(-1) and thus lead to some unexpected behaviors. I'm not sure what the best way to handle this error would be since this is in

[PATCH 0/4] Document the output ID pool

Weston uses bitfields to keep track of various things about outputs, such as which outputs a given view or surface is visible on. Document how these bitfield masks are created and maintained. A consequence of this design is that weston can only support a maximum of 32 outputs. I'm not sure what

[PATCH 4/4] compositor: Make types consistent for bitshifting unsigned ints

Signed-off-by: Bryce Harrington --- src/compositor.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/src/compositor.c b/src/compositor.c index a2a03a7..98efb4c 100644 --- a/src/compositor.c +++ b/src/compositor.c @@ -1069,15

[PATCH 2/4] compositor: Document how views and surfaces are mapped to outputs

Signed-off-by: Bryce Harrington --- src/compositor.c | 73 1 file changed, 73 insertions(+) diff --git a/src/compositor.c b/src/compositor.c index a0db786..230fd78 100644 --- a/src/compositor.c +++

[PATCH 1/4] compositor: Document routines relating to idle behavior

Signed-off-by: Bryce Harrington Reviewed-by: Pekka Paalanen --- src/compositor.c | 51 +++ 1 file changed, 51 insertions(+) diff --git a/src/compositor.c b/src/compositor.c index

[PATCH weston v2] tests: Adding simple waycheck validation tool.

Adds an initial implementation of a testing tool that uses the unit test framework to run checks against an arbitrary Wayland compositor. Note that this is not intended for Weston-specific testing, but for generic Wayland testing. Signed-off-by: Jon A. Cruz --- Changes

Re: [PATCH wayland 1/2] protocol: Improve data source notification around DnD progress

Hey, On Wed, Dec 23, 2015 at 3:07 AM, Jonas Ådahl wrote: > On Tue, Dec 22, 2015 at 04:46:37PM +0100, Carlos Garnacho wrote: >> Hey, >> >> On Tue, Dec 22, 2015 at 2:55 PM, Jonas Ådahl wrote: >> > On Tue, Dec 22, 2015 at 01:33:08PM +0100, Carlos Garnacho wrote: