From: Markus Volk <f_l_k@t-online.de>
To: raj.khem@gmail.com, openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH 3/9] libsdl2-image: build with cmake
Date: Tue, 22 Apr 2025 05:48:58 +0200 [thread overview]
Message-ID: <M9P3VS.BOZVDNC1WYLK3@t-online.de> (raw)
In-Reply-To: <1179f882-e39c-4943-a1d6-91a52cc82c4d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
On Mon, Apr 21 2025 at 13:54:20 -07:00:00, Khem Raj via
lists.openembedded.org <raj.khem=gmail.com@lists.openembedded.org>
wrote:
> fails to configure see <http://0x0.st/8Vz4.7805>
Yes, I accidentially added libsdl2 instead of libsdl3 as a dependency
and (probably) because I also
had set PREFERRED_PROVIDER_libsdl2 = "libsdl2-compat" it didn't fail
for me. Thanks for fixing this.
[-- Attachment #2: Type: text/html, Size: 599 bytes --]
next prev parent reply other threads:[~2025-04-22 3:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 9:48 [meta-oe][PATCH 1/9] libxmp: add recipe Markus Volk
2025-04-21 9:48 ` [meta-oe][PATCH 2/9] fluidsynth: update Markus Volk
2025-04-21 9:48 ` [meta-oe][PATCH 3/9] libsdl2-image: build with cmake Markus Volk
2025-04-21 20:54 ` [oe] " Khem Raj
2025-04-22 3:48 ` Markus Volk [this message]
2025-04-21 9:48 ` [meta-oe][PATCH 4/9] libsdl2-mixer: update and " Markus Volk
2025-04-21 21:23 ` [oe] " Khem Raj
2025-04-21 9:48 ` [meta-oe][PATCH 5/9] libsdl2-net: update anb " Markus Volk
2025-04-21 9:48 ` [meta-oe][PATCH 6/9] libsdl2-ttf: update and " Markus Volk
2025-04-21 9:48 ` [meta-oe][PATCH 7/9] libsdl3-ttf: add recipe Markus Volk
2025-04-21 9:48 ` [meta-oe][PATCH 8/9] libsdl2-compat: make mutually exclusive with libsdl2 Markus Volk
2025-04-21 9:48 ` [meta-oe][PATCH 9/9] libsdl3-image: add recipe Markus Volk
2025-04-21 10:01 ` [oe] [meta-oe][PATCH 1/9] libxmp: " Gyorgy Sarvari
2025-04-21 11:00 ` 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=M9P3VS.BOZVDNC1WYLK3@t-online.de \
--to=f_l_k@t-online.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.