~wayland.admin/wayland/master : changes

~wayland.admin/wayland/master » Changes from revision 2116

From Revision 2116 to 2097

Rev	Summary	Authors	Tags	Date
2116	releasing: adapt for Wayland releasing: adapt for Wayland Remove Weston-specific bits, strip off outdated instructions. Signed-off-by: Simon Ser <contact@emersion.fr>	Simon Ser		5 years ago
2115	Add releasing.txt Add releasing.txt This file is imported from Weston (commit 53d7c243). Signed-off-by: Simon Ser <contact@emersion.fr>	Simon Ser		5 years ago
2114	configure.ac: reopen master for regular development configure.ac: reopen master for regular development Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Pekka Paalanen		5 years ago
2113	configure: detect libdl and librt configure: detect libdl and librt Signed-off-by: Leonid Bobrov <mazocomp@disroot.org>	Leonid Bobrov		5 years ago
2112	configure.ac: bump to version 1.17.0 for the official releas... configure.ac: bump to version 1.17.0 for the official release	Derek Foreman		5 years ago
2111	configure.ac: bump version to 1.16.93 for the RC1 release configure.ac: bump version to 1.16.93 for the RC1 release	Derek Foreman		5 years ago
2110	Merge branch 'mr/request-bad-size' into 'master' Merge branch 'mr/request-bad-size' into 'master' Fix demarshal of invalid size in message header Closes #52 See merge request wayland/wayland!2	Derek Foreman		5 years ago
2109	contributing: use Gitlab merge request workflow contributing: use Gitlab merge request workflow The experience from Weston shows that the Gitlab merge request based workflow works really well. Recently there have also been issues with the mailing list that have made the email based workflow more painful than it used to be. Those issues might have been temporary or occasional, but they probably are only going to increase. The MR workflow is different, it has its issues (https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/74) and we likely lose the explicit Reviewed-by etc. tags from commit messages, but it is also much easier to work with: no more whitespace damaged patches, lost email, setting up git-send-email; we gain automated CI before any human reviewer even looks at anything, and people can jump in to an ongoing discussion even if they weren't subscribed before. If you still want email, you can subscribe to that selectively(!) in Gitlab yourself. This text has been copied from Weston's CONTRIBUTING.md of the 5.0.91 release and slightly altered for Wayland. Fixes: https://gitlab.freedesktop.org/wayland/wayland/issues/49 v2: fixed two left-over mentions of Weston Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com> v1 Reviewed-by: Simon Ser <contact@emersion.fr> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Scott Anderson <scott.anderson@collabora.com> Acked-by: Ian Ray <ian.ray@ge.com> Acked-by: Derek Foreman <derek.foreman.wayland@gmail.com>	Pekka Paalanen		5 years ago
2108	wayland-util.h: add forward declaration for wl_object wayland-util.h: add forward declaration for wl_object The definition of wl_argument in wayland-util.h references wl_object, so wl_object ought to be defined in wayland-util.h. This resolves gitlab issue #78. Fixes: https://gitlab.freedesktop.org/wayland/wayland/issues/78 Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Chris Billington		5 years ago
2107	configure.ac: bump to version 1.16.92 for the beta release configure.ac: bump to version 1.16.92 for the beta release	Derek Foreman	1.16.92	5 years ago
2106	tests: fix main symbol duplication tests: fix main symbol duplication So far I got these errors before patching: libtool: link: cc -o .libs/headers-test -pthread -Wall -Wextra -Wno-unused-parameter -g -Wstrict-prototypes -Wmissing-prototypes -fvisibility=hidden -O2 -pipe tests/headers-test.o tests/headers-protocol-test.o tests/headers-protocol-core-test.o /tmp/obj/wayland-1.16.0/build-amd64/.libs/libtest-runner.a -L.libs -lwayland-client -lffi -lm -lwayland-server -lkvm -Wl,-rpath-link,/usr/local/lib ld: error: duplicate symbol: main >>> defined at headers-test.c:53 (/tmp/obj/wayland-1.16.0/wayland-1.16.0/tests/headers-test.c:53) >>> tests/headers-test.o:(main) >>> defined at test-runner.c:377 (/tmp/obj/wayland-1.16.0/wayland-1.16.0/tests/test-runner.c:377) >>> test-runner.o:(.text+0x250) in archive /tmp/obj/wayland-1.16.0/build-amd64/.libs/libtest-runner.a libtool: link: cc -o .libs/exec-fd-leak-checker -pthread -Wall -Wextra -Wno-unused-parameter -g -Wstrict-prototypes -Wmissing-prototypes -fvisibility=hidden -O2 -pipe tests/exec-fd-leak-checker.o /tmp/obj/wayland-1.16.0/build-amd64/.libs/libtest-runner.a -L.libs -lwayland-client -lffi -lm -lwayland-server -lkvm -Wl,-rpath-link,/usr/local/lib ld: error: duplicate symbol: main >>> defined at exec-fd-leak-checker.c:57 (/tmp/obj/wayland-1.16.0/wayland-1.16.0/tests/exec-fd-leak-checker.c:57) >>> tests/exec-fd-leak-checker.o:(main) >>> defined at test-runner.c:377 (/tmp/obj/wayland-1.16.0/wayland-1.16.0/tests/test-runner.c:377) >>> test-runner.o:(.text+0x250) in archive /tmp/obj/wayland-1.16.0/build-amd64/.libs/libtest-runner.a Makefile.am: error: object 'tests/test-helpers.$(OBJEXT)' created both with libtool and without libtool: link: cc -o .libs/fixed-benchmark -pthread -Wall -Wextra -Wno-unused-parameter -g -Wstrict-prototypes -Wmissing-prototypes -fvisibility=hidden -O2 -pipe tests/fixed-benchmark.o /tmp/obj/wayland-1.16.0/build-amd64/.libs/libtest-runner.a -L.libs -lwayland-client -lffi -lm -lwayland-server -lkvm -Wl,-rpath-link,/usr/local/lib ld: error: duplicate symbol: main >>> defined at fixed-benchmark.c:100 (/tmp/obj/wayland-1.16.0/wayland-1.16.0/tests/fixed-benchmark.c:100) >>> tests/fixed-benchmark.o:(main) >>> defined at test-runner.c:377 (/tmp/obj/wayland-1.16.0/wayland-1.16.0/tests/test-runner.c:377) >>> test-runner.o:(.text+0x250) in archive /tmp/obj/wayland-1.16.0/build-amd64/.libs/libtest-runner.a This commit fixes all of that. Signed-off-by: Leonid Bobrov <mazocomp@disroot.org> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Leonid Bobrov via wa...		5 years ago
2105	protocol: warn clients about some wl_output properties protocol: warn clients about some wl_output properties All wl_output properties don't always make sense for all compositors. Some compositors might not implement a "global compositor space", (e.g. 3D compositors) in which case properties like x and y don't make sense. Some compositors might expose virtual outputs, in which case modes, make and model are not relevant. In a lot of these situations, information from xdg_output is better suited. Compositors also expose output refresh rate, which shouldn't be used for synchronization purposes. Signed-off-by: Simon Ser <contact@emersion.fr> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Derek Foreman <derek.foreman.wayland@gmail.com>	Simon Ser		5 years ago
2104	configure.ac: bump version to 1.16.91 for the alpha release configure.ac: bump version to 1.16.91 for the alpha release	Derek Foreman		5 years ago
2103	TODO: remove "SDL port", it's been done by now TODO: remove "SDL port", it's been done by now Upstream SDL supports Wayland since v2.0.4 (June 2015): https://forums.libsdl.org/viewtopic.php?t=11294 Just set SDL_VIDEODRIVER=wayland and SDL will do the right thing :) Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Eric Engestrom		5 years ago
2102	Print NULL strings as "nil" in wl_closure_print Print NULL strings as "nil" in wl_closure_print Calling printf("%s", NULL) is undefined behaviour. Signed-off-by: Simon Ser <contact@emersion.fr> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Simon Ser		5 years ago
2101	proto, server: Add internal server error message. (v2) proto, server: Add internal server error message. (v2) Many languages such as C++ or Rust have an unwinding error-reporting mechanism. Code in these languages can (and must!) wrap request handling callbacks in unwind guards to avoid undefined behaviour. As a consequence such code will detect internal server errors, but have no way to communicate such failures to the client. This adds a WL_DISPLAY_ERROR_IMPLEMENTATION error to wl_display so that such code can notify (and disconnect) clients which hit internal bugs. While servers can currently abuse other wl_display errors for the same effect, adding an explicit error code allows clients to tell the difference between errors which are their fault and errors which are the server's fault. This is particularly interesting for automated bug reporting. v2: Rename error from "internal" to "implementation", in sympathy with X11's BadImplementation error. Add more justification in the commit message. Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com> Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Christopher James Ha...		5 years ago
2100	server: Split out varargs version of wl_resource_post_error. server: Split out varargs version of wl_resource_post_error. This will allow other wrappers around wl_resource_post_error to accept variable argument lists. Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com> Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>	Christopher James Ha...		5 years ago
2099	protocol: prefer wl_surface.damage_buffer protocol: prefer wl_surface.damage_buffer This commit makes wl_surface.damage_buffer preferred over wl_surface.damage. wl_surface.damage can be implemented in a non-optimal way by the compositor (e.g. by always damaging the whole buffer). Having two requests makes it complicated for the compositor to handle damage, making it necessary to transform one into the other's coordinates. Moreover, integration with wp_viewporter is tricky. Signed-off-by: Simon Ser <contact@emersion.fr> Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Derek Foreman <derek.foreman.samsung@gmail.com>	Simon Ser		5 years ago
2098	protocol: Bump seat to version 7 and require keymaps be priv... protocol: Bump seat to version 7 and require keymaps be private Weston commit 76829fc4eaea329d2a525c3978271e13bd76c078 (and similar commits for other compositors) protects the compositor's keyboard mapping from client damage by duplicating the keymap for every client. On some systems there are other potential fixes for this - such as using sealed memfds on linux - but we can't use them since essentially all client code anywhere has mapped the keyboard map with a MAP_SHARED mmap() call. While we can't break years worth of code, we can require any future clients to use MAP_PRIVATE if they use a seat version above 6. If a compositor can't use sealing or a similar facility, it should still protect itself with copied keymaps, but clients must always assume shared mapping of a keymap will fail. Signed-off-by: Derek Foreman <derek.foreman.samsung@gmail.com> Reviewed-by: Simon Ser <contact@emersion.fr> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Philipp Kerling <pkerling@casix.org> Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>	Derek Foreman		5 years ago
2097	tests: Remove memory leak checking infrastructure tests: Remove memory leak checking infrastructure There are far better ways to detect memory leaks, such as either valgrind or ASan. Having Meson makes it really easy to use these tools in our tests, and we can do that in CI as well. Having these local wrappers actually completely broke ASan usage, so remove them in favour of using the more powerful options. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>	Daniel Stone		5 years ago

Older »