From: Paolo Bonzini <pbonzini@redhat.com>
To: Katsuhiro Ueno <uenobk@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] meson: Set implicit_include_directories to false
Date: Mon, 17 May 2021 13:41:57 +0200 [thread overview]
Message-ID: <8f6be65f-b3d9-c5fd-38a8-c52f9275430f@redhat.com> (raw)
In-Reply-To: <CANrJRqLyfijWWbrAwpQLrWuH1-hmraGnx2EQO4GaTH6D1TVxEQ@mail.gmail.com>
On 01/05/21 04:08, Katsuhiro Ueno wrote:
> 2021-04-30 16:48 Paolo Bonzini <pbonzini@redhat.com>:
>>
>> On 29/04/21 04:43, Katsuhiro Ueno wrote:
>>> Without this, libvixl cannot be compiled with macOS 11.3 SDK due to
>>> include file name conflict (usr/include/c++/v1/version conflicts with
>>> VERSION).
>>>
>>> Signed-off-by: Katsuhiro Ueno <uenobk@gmail.com>
>>> ---
>>> meson.build | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/meson.build b/meson.build
>>> index c6f4b0cf5e..d007bff8c3 100644
>>> --- a/meson.build
>>> +++ b/meson.build
>>> @@ -2129,6 +2129,7 @@ common_all = common_ss.apply(config_all, strict: false)
>>> common_all = static_library('common',
>>> build_by_default: false,
>>> sources: common_all.sources() + genh,
>>> + implicit_include_directories: false,
>>> dependencies: common_all.dependencies(),
>>> name_suffix: 'fa')
>>>
>>
>> Can you include the difference in the include paths (the -I and -iquote
>> arguments)? There are many cases in which we rely on having the current
>> source directory in the build path, for example all inclusions of "trace.h".
>
> This only removes -I.. (current (top-level) source directory) from the
> arguments. The meson manual says that it also removes -I. (current
> (top-level) build directory) but -I. is still in the arguments (I am
> not sure why). This does not change any -iquote argument.
>
> As far as I know, this does not affect the inclusions of "trace.h"
> because each "trace.h" is in the same directory as the files that
> include it, and the top-level build directory, which has the "trace"
> directory containing generated "trace-*.h" files, is still in the
> include path.
Queued, thanks. It looks like "implicit" only refers to the directory
that meson.build lies in.
It would be nicer to have _all_ targets in meson.build have
implicit_include_directories: false, since we would have the same
problem for other C++ sources, but that can be done later.
Paolo
next prev parent reply other threads:[~2021-05-17 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 2:43 [PATCH] meson: Set implicit_include_directories to false Katsuhiro Ueno
2021-04-30 7:48 ` Paolo Bonzini
2021-05-01 2:08 ` Katsuhiro Ueno
2021-05-17 11:41 ` Paolo Bonzini [this message]
2021-05-16 14:05 ` Alexander Graf
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=8f6be65f-b3d9-c5fd-38a8-c52f9275430f@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=uenobk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).