Re: [OE-core][PATCH] qemu: upgrade 10.2.0 -> 11.0.0

[Quan Sun <Quan.Sun@windriver.com>]

On 5/7/26 07:23, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 6 May 2026 at 23:49, Quan.Sun via lists.openembedded.org
> <Quan.Sun=windriver.com@lists.openembedded.org> wrote:
>> +SRC_URI += "git://gitlab.com/qemu-project/python-qemu-qmp.git;protocol=https;branch=main;destsuffix=python-qemu-qmp;name=qemu-qmp"
>> +SRCREV_qemu-qmp = "82006cb788d27b090a8b84fc7831feb9c528bcdc"
> This component should be provided with a separate recipe.


Yes, will do.


>> +From f013e84d382bc1bd7d49206bdf47c689b0c6fbb5 Mon Sep 17 00:00:00 2001
>> +From: Quan Sun <Quan.Sun@windriver.com>
>> +Date: Fri, 1 May 2026 13:53:24 -0700
>> +Subject: [PATCH] meson: fix subproject include paths for standalone builds
>> +
>> +Upstream-Status: Inappropriate [OE-specific]
> This should include an explanation of what makes it inappropriate.
> Don't just say 'oe specific', a lot of other patches do it, but it
> doesn't actually expain anything. What happens without the patch? Can
> we find a solution that would be acceptable upstream? Adding
> Inappropriate patches should be avoided if possible.


When these subprojects are built standalone (outside the main QEMU meson
project), they fail to compile because they cannot find headers from the
top-level QEMU source tree (e.g. include/standard-headers/ or root-level
headers). In a normal upstream build, the parent project provides these
paths implicitly. OE's build environment triggers standalone subproject
builds, requiring explicit include paths.


This is unlikely to be accepted upstream because QEMU does not support
building these subprojects standalone — they are intended to be built 
only as part of the full QEMU tree. The standalone meson.build files 
exist for use as subprojects in *other* projects (like DPDK), where 
those projects provide their own compatible headers.

Thanks,

Quan