Re: [PATCH] meson: ensure correct version-def.h is used
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 13, 2025, 17:01 UTC
- Message-ID
- <xmqqr056abry.fsf@gitster.g>
- In-Reply-To
- <20250113-toon-fix-meson-version-v1-1-9637e2be32e3@iotcl.com>
Toon Claes <toon@iotcl.com> writes:
> have a `version-def.h` file in project root directory as well. Because > `version-def.h` is included in `version.c` using the #include directive > with double quotes, some compilers will look for the header file in the > same directory as the source file.
What happens if we use <version-def.h> to include (which is how C standard tells us to do), with an explicit include path specified with -I<directory>? If it solves the issue, that may be a better approach.
Thanks.