[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/7] include/hw/pci include/hw/cxl: Clean up includes
From: |
Markus Armbruster |
Subject: |
Re: [PATCH v2 0/7] include/hw/pci include/hw/cxl: Clean up includes |
Date: |
Wed, 15 Feb 2023 18:21:28 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 15/2/23 14:28, Markus Armbruster wrote:
>> "Michael S. Tsirkin" <mst@redhat.com> writes:
>>
>>> On Fri, Dec 23, 2022 at 06:27:07AM +0100, Markus Armbruster wrote:
>>>> "Michael S. Tsirkin" <mst@redhat.com> writes:
[...]
>>>>> It would be even better if there was e.g. a make target
>>>>> pulling in each header and making sure it's self consistent and
>>>>> no circularity. We could run it e.g. in CI.
>>>>
>>>> Yes, that would be nice, but the problem I've been unable to crack is
>>>> deciding whether a header is supposed to compile target-independently or
>>>> not. In my manual testing, I use trial and error: if it fails to
>>>> compile target-independently, compile for all targets. This is s-l-o-w.
>>
>> To spice things up, we also have headers that provide additional
>> contents in target-dependent context. These need to be tested in both
>> contexts.
>
> Do we need to figure a way to get rid of this problem
> in order to build a single qemu-system binary?
I don't know.