Remove backported patches and remove the introspection patch as that is
no longer needed.
(From OE-Core rev: 94bc7f8c2442f6627b001f1dd40c0023260b22e8)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We're still seeing reproducibility issues on the autobuilder with this
recipe. I was able to make the output "match" by rebuilding the PCH and
then rebuilding the binary objects, proving the PCH isn't deterministic.
Disable PCH until we can get to the bottom of why that may be.
(From OE-Core rev: 95686432ecb7e411155563643d59a3d5f683937c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upgrade mesa and mesa-gl recipes to version 20.3.2.
(From OE-Core rev: 5ab325c18640dd6d17ac4592f3ba3e484a5bdb37)
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is code to remove the prefix CMAKE_SOURCE_DIR from __FILENAME__ paths
used for logging with LOGE() in the code. We need to make this match the value we use
in the debug source remapping from CFLAGS. If we don't, the code is firstly removing
the incorrect prefix and possibly moving outside the string, secondly, it causes a
reproducibility issue depending on the length of path the build happens in.
Add a small patch and configuration to avoid the issue.
(From OE-Core rev: 410dbfd1f82b4862ced6fca88789edf0fd9d65df)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two of the patches have been applied upstream:
0001-meson-Add-xcb-fixes-to-loader-when-using-x11-and-dri.patch
0005-vc4-use-intmax_t-for-formatted-output-of-timespec-me.patch
The 'surfaceless' platform is now enabled by default, therefore it is no
longer a valid choice. The meson build system is intelligent enough now to
decide if 'drm' needs to be enabled based on whether or not gbm is available.
Therefore 'drm' also is no longer a valid platform choice:
ERROR: Options "drm, surfaceless" are not in allowed choices: "auto, x11, wayland, haiku, android, windows"
RP: Add missing mesa-gl upgrade
(From OE-Core rev: de68fe9268092c0600a81bedfc805eaed9dcb87b)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Include link to upstream report and the last autobuilder failure [1]
so it's easy to identify why this is needed in future.
[1] https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/1160/steps/8/logs/step1c
(From OE-Core rev: 28647f8e4fb5fe2e56f0609900187bc658ba9ccf)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit adds the changes of 20.2.2, 20.2.3 and 20.2.4 bug fix
releases.
(From OE-Core rev: 9c39a1360d81264e867242f238f6d14fdb395e96)
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Incorrectly set git regex meant we were stuck with a 4 year old
version.
Use tarballs as they contain prebuilt font files; building them
from source requires a bunch of obscure dependencies.
Contains portions of libglyph which are Apache 2.x licensed.
(From OE-Core rev: 4dcde0147ec4d63ab4459dc1e995cea155130e36)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a patch to fix failing ptest.
(From OE-Core rev: 1c33aa37c59f028afe3dc0250af39fd0fbc3bc65)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-License-Update: Copyright year updated to 2020.
Refresh the following patch:
0001-libjpeg-turbo-fix-package_qa-error.patch
(From OE-Core rev: 490fe53f625417494dd63a4fe4dcaa98a3c54eb9)
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
PACKAGECONFIG[directfb] already adds directfb to the build
dependencies. But the automatically generated runtime
dependencies do not add the directfb package to the runtime
dependencies. Most likely this happens because libsdl2 does not link
against directfb but uses dlopen() or similar. Thus, the runtime
dependency to directfb needs to be declared explicitly.
(From OE-Core rev: 62d3cbe7c8261c1c875ff6da11572409262aaf02)
Signed-off-by: Mark Jonas <toertel@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fix error:
| framework/lib/ppc/libframework.a(device.cpp.o): in function `std::__atomic_base<unsigned long long>::load(std::memory_order) const':
| /usr/include/c++/10.2.0/bits/atomic_base.h:426: undefined reference to `__atomic_load_8'
some arch don't have built-in atomic, so need to link it
explicitly
(From OE-Core rev: 65410c5ff4f9c34758d1e2270132c631166e7d1a)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Running the weston compositor as the root user is an insecure default
behavior for OE-core. We can do much better, at least when using
systemd. Change the recipe to create a dedicated "weston" user and start
weston as this user. The systemd service and socket units are no longer
template units, as there were several inconsistencies in the templates.
Instead, there is now a global /run/wayland-0 socket that gets created,
and systemd will start weston on demand when a client connects to that
socket or when attempting to reach graphical.target, whichever comes
first. This also allows downstream users to easily change the behavior
so that weston *only* starts on demand by adding a drop file. Access to
the global socket is controlled by a "wayland" group; any user that is a
member of the group can use the socket to talk to the compositor. This
also satisfies another use case where another systemd service might
start a graphical application that needs to display with weston (e.g. a
single function device in kiosk mode). Finally, the udev rules for
starting weston with the existance of a DRM device have been removed.
Being WantedBy= a graphical target should eliminate the need for this
behavior, and having it present makes it difficult for downstream users
to start weston on demand (having to override the udev rules).
(From OE-Core rev: dd83fb40f76749c6689807afabc63b9d5c2a4065)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
files/0001-xf86drm.c-fix-build-failure.patch
Removed since this is included in 2.4.103.
(From OE-Core rev: 689df7eb86103b59304ceb5b69bf544cc3fe3f6c)
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* it was added to weston-init in 72dd74c5d384dbe641cc7c02ecf766ff8d5f555f now world
builds are failing with:
ERROR: Nothing RPROVIDES 'weston-init' (but openembedded-core/meta/recipes-graphics/wayland/weston_9.0.0.bb RDEPENDS on or otherwise requires it)
weston-init was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES)
NOTE: Runtime target 'weston-init' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['weston-init']
ERROR: Nothing RPROVIDES 'weston-dev' (but openembedded-core/meta/recipes-graphics/wayland/weston_9.0.0.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'weston-dev'
NOTE: Runtime target 'weston-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['weston-dev']
ERROR: Nothing RPROVIDES 'weston' (but openembedded-core/meta/recipes-graphics/wayland/weston_9.0.0.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'weston'
NOTE: Runtime target 'weston' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['weston']
(From OE-Core rev: 0a882490fe75915c7a119f3498df6750be25f8e0)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backport fix for undefined symbol for xcb_xfixes_create_region in loader_dri3_helper.c.
(From OE-Core rev: fd55d41c9d2e79fd7f7665107d1640a2dd9a3dc3)
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building on Raspbery Pi OS/64-bit, libsdl2 fails with
the error:
.../tmp/work/aarch64-linux/libsdl2-native/2.9.12-r0/SDL2-2.0.12/src/video/raspberry/SDL.rpivideo.h:47:5:
error: unknown type name 'EGL_DISPMANX_WINDOW_T'
EGL_DISPMANX_WINDOW_T dispman_window;
Disable video-rpi to avoid the problem since video suppport is
not needed for rpi and this configuration option is harmless when
building on x86-64 hosts.
(From OE-Core rev: 51009ed1b88aa391aae819fd800b907badc2be8c)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
wayland-utils contains wayland-info utility which deprecates
and replaces weston-info from weston.
(From OE-Core rev: bb8fa9950e716fdcee818a38dc4df3a19b1f3c2f)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otherwise, there's a crash in swrast - the same issue as with
X11.
(From OE-Core rev: 09ef3dacc55544143a146190c3d66fcf5dc697ad)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several issues are addressed:
1. weston requires pam when starting under systemd
2. systemd was attempting to launch weston twice (from
sysvinit script and from systemd unit file) which caused confusion
and errors.
3. runtime test should stop/start weston via systemd only if systemd
actually controls system startup, not merely when systemd is present.
(From OE-Core rev: 72dd74c5d384dbe641cc7c02ecf766ff8d5f555f)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
weston uses --no-undefined option during linking which does not work
with LTO therefore override it with -z undefs when lto is enabled in
distro
(From OE-Core rev: c5252fc88938ab3425595dcf31f892ed4aba6bc1)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is host contamination and can also fail for all kinds of
reasons when running under usermode qemu.
(From OE-Core rev: fb60d0920b660dffb346b2212dc6f8ba2a0b9fde)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently the WESTON_USER variable is used as user and group name for
chown'ing XDG_RUNTIME_DIR. If WESTON_USER has no group with the same
name this fails.
Therefore add a new WESTON_GROUP variable which is set to WESTON_USER if
not specified to ensure backwards compatibility.
(From OE-Core rev: 8d4e0ac61671646749a30c72782376307b3e0c82)
Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
