From: Markus Volk <f_l_k@t-online.de>
To: alex.kanavin@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCHv2] default-providers.inc: add entries for virtual/libsdl2
Date: Fri, 25 Apr 2025 10:25:23 +0200 [thread overview]
Message-ID: <B2M9VS.YHEM9X6L6IP01@t-online.de> (raw)
In-Reply-To: <CANNYZj9POGReasMqgt6=BVRexWAMGF0FYbVoPzNwRkfojTk-7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Fri, Apr 25 2025 at 09:59:58 +02:00:00, Alexander Kanavin via
lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
wrote:
> This is fine, but it makes me wonder: is libsdl2-compat compatible
> enough to build qemu-system-native with it? Can you try that? Then we
> might consider switching over to sdl3 in core.
I have already tried this. I have set it up as follows:
VIRTUAL-RUNTIME_libsdl2 = ālibsdl2-compatā
PREFERRED_PROVIDER_virtual/libsdl2 = ālibsdl2-compatā
PREFERRED_PROVIDER_virtual/libsdl2-native = ālibsdl2-compat-nativeā
PREFERRED_PROVIDER_virtual/nativesdk-libsdl2 =
ānativesdk-libsdl2-compatā
and I was able to build my complete image, which includes building
qemu-system-native
and also a lot of libsdl2 games, and at least compilation-wise there
were no problems.
I also noticed quite some runtime improvements if running libsdl2 apps
under wayland
Some possible problems I can think of:
- libsdl2-compat would add a requirement for x11 and opengl
- I'm not sure why this is, but libsdl2-compat was added to
non-repro-meta-oe.inc, which
suggests there may still be a reproducibility issue
[-- Attachment #2: Type: text/html, Size: 1483 bytes --]
next prev parent reply other threads:[~2025-04-25 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 21:39 [oe-core][PATCHv2] default-providers.inc: add entries for virtual/libsdl2 Markus Volk
2025-04-25 7:59 ` Alexander Kanavin
2025-04-25 8:25 ` Markus Volk [this message]
2025-04-25 8:36 ` Alexander Kanavin
[not found] <18395F03D66275F9.31387@lists.openembedded.org>
2025-04-24 21:40 ` Markus Volk
2025-04-24 22:53 ` Khem Raj
2025-04-24 22:56 ` Markus Volk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B2M9VS.YHEM9X6L6IP01@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox