[ANNOUNCE] weston 4.0.93

2018-08-10 Thread Derek Foreman
Hello, The RC1 release candidate for weston 5.0 is now available. Daniel Stone (3): doc: Update CONTRIBUTING for Weston README: Move to Markdown, rewrite introduction doc: Use GitLab MRs for patches, not the list Derek Foreman (1): configure.ac: bump to version 4.0.93 for

[ANNOUNCE] wayland-1.15.93

2018-08-10 Thread Derek Foreman
Hello, The RC1 release candidate for wayland 1.16 is now available. Daniel Stone (1): contributing: Weston now uses GitLab MRs Derek Foreman (1): configure.ac: bump to version 1.15.93 for the RC1 release git tag: 1.15.93 https://wayland.freedesktop.org/releases/wayland-1.15.93.tar.

Re: How fwrd-compatible is using dlopen and core only?

2018-08-10 Thread ferreiradaselva
Oh, I solved the problem with the extern variable (wl_registry_interface), I could get a pointer to it using `dlsym(handler, "wl_registry_interface")`. The other question remains: can I use the content of the inline functions directly (to avoid the need to include protocol headers)? Is forward

Re: [PATCH weston 2/2] input: Update to-be-restored focus when unfocused

2018-08-10 Thread Derek Foreman
On 2018-08-02 03:32 AM, Quentin Glidic wrote: > On 8/2/18 10:29 AM, Quentin Glidic wrote: >> From: Quentin Glidic >> >> If we start a special (grabbing) client when Weston is unfocused, it >> would lose focus when coming back to Weston. >> >> A first attempt to fix this was 85d55540cb64bf97a08b40f

How fwrd-compatible is using dlopen and core only?

2018-08-10 Thread ferreiradaselva
Hi, For the OSS window framework that I'm working on, the Wayland backend requires linking to the libraries. No problem here. I wish to give an option to load the Wayland libraries at runtime, using `dlopen()`. The problem is that some functions are inline'd in the headers or part of the exten

Re: How fwrd-compatible is using dlopen and core only?

2018-08-10 Thread ferreiradaselva
Another thing that I realized: Headers, such as `wayland-client-protocol.h`, contains declarations such as `wl_registry_interface`, which is an extern variable. If I am going to copy-paste this: wl_proxy_marshal_constructor((struct wl_proxy *) wl_display, WL_DISPLAY_GET_REGISTRY, &wl_registry_

Re: [PATCH libinput] doc/user: expand the Contributing document

2018-08-10 Thread Pekka Paalanen
On Fri, 10 Aug 2018 15:33:42 +1000 Peter Hutterer wrote: > This is mostly taken from the Weston Contributing.md document. > > Main changes from there are: > - more detailed step-by-step on how to create a MR > - commit history/messages in two sections > - s/Weston/libinput/ > > I skipped the Re

Re: [PATCH weston 0/3] Fix invalid memory access during de-init

2018-08-10 Thread Pekka Paalanen
On Wed, 8 Aug 2018 12:59:45 +0300 Pekka Paalanen wrote: > On Tue, 7 Aug 2018 19:05:01 +0530 > Harsha M M wrote: > > > valgrind reports several invalid memory access during shutdown of > > weston. In general problem is with components which do not remove > > the signals added using wl_signal_emi