Philippe Mathieu-Daudé <phi...@linaro.org> writes: > On 15/2/23 14:28, Markus Armbruster wrote: >> "Michael S. Tsirkin" <m...@redhat.com> writes: >> >>> On Fri, Dec 23, 2022 at 06:27:07AM +0100, Markus Armbruster wrote: >>>> "Michael S. Tsirkin" <m...@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.
