!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

949 Members
For people hacking on the Nix package manager itself200 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
20 Feb 2025
@emilazy:matrix.orgemilyyes, I just forget whether "system headers" can use non-system includes to include other system headers without issues or not23:06:22
@Ericson2314:matrix.orgJohn Ericsonfrom the perspective of owns own project, it is weird, but headers are not for that perspective!23:06:28
@Ericson2314:matrix.orgJohn Ericson emily: Robert Hensing (roberth) OK it should work now 23:15:59
@roberthensing:matrix.orgRobert Hensing (roberth)meson is compiling, clangd is happy 🎉23:30:37
21 Feb 2025
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
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.

06:00:51
@alexandi:matrix.orgalexandi joined the room.06:52:57
@normalcea:matrix.org@normalcea:matrix.org joined the room.16:37:46

Show newer messages


Back to Room ListRoom Version: 6