In reply to @emilazy:matrix.org
(don't quote me on this though)

I don’t think that’s how it works. ”…” and <…> only affect default search path preferences https://gcc.gnu.org/onlinedocs/cpp/Search-Path.html. I our case this distinction does not make a difference.

To disable warnings you have to include directories via -isystem and not via -I.

For reference, Cmake does that with SYSTEM flag in target_include_directories:

https://cmake.org/cmake/help/latest/command/target_include_directories.html

Some discussions about meson’s handling of system includes: https://github.com/mesonbuild/meson/issues/963

https://github.com/mesonbuild/meson/pull/5953

Barring some unforeseen differences around search path preferences/order shenanigans it really doesn’t matter semantically.

I think in general the de-facto rule/convention is to refer to one’s own headers with quotes to highlight to the reader that it’s part of the same project and not an external library.

another question:

# boost is a public dependency, but not a pkg-config dependency unfortunately, so we
# put in `deps_other`.

why? Boost has .pc files (in Nixpkgs at least), and this breaks e.g. Rust pkg_config parsing the dependencies out of the .pc files

another question:

# boost is a public dependency, but not a pkg-config dependency unfortunately, so we
# put in `deps_other`.

why? Boost has .pc files (in Nixpkgs at least), and this breaks e.g. Rust pkg_config parsing the dependencies out of the Nix .pc files