Re: Target-dependent include path, why?

[Markus Armbruster]

Richard Henderson <richard.henderson@linaro.org> writes:

> On 12/8/22 23:12, Markus Armbruster wrote:
>> I stumbled over this:
>>      ../include/ui/qemu-pixman.h:12:10: fatal error: pixman.h: No such file 
>> or directory
>>         12 | #include <pixman.h>
>>            |          ^~~~~~~~~~
>> Works when included into target-dependent code.
>> Running make -V=1 shows we're passing a number of -I only when compiling
>> target-dependent code, i.e. together with -DNEED_CPU_H:
>>      -I/usr/include/pixman-1 -I/usr/include/capstone 
>> -I/usr/include/spice-server -I/usr/include/spice-1
>>      -I/usr/include/cacard -I/usr/include/nss3 -I/usr/include/nspr4 
>> -I/usr/include/PCSC
>>      -isystem../linux-headers -isystemlinux-headers
>> Why?
>
> Because of where [pixman] is added as a dependency in meson.build.

Is it added where it is for a reason, or is it accidental?

> If you want to use it somewhere new, you've got to move the dependency.