| 20 Feb 2025 |
 John Ericson | and use regular #include | 00:31:37 |
| John Ericson | emily: another thing is I don't know whether #include "foo" or #include <nix/foo> is better within nix itself | 00:34:26 |
| John Ericson | the latter violates "don't know your own name" but keeps us dogfooding our headers as others would use them | 00:34:50 |
| John Ericson | (the /nix in the pkg-config is definitely bad) | 00:35:04 |
| John Ericson | * (the /nix in the *.pc is definitely bad) | 00:35:14 |
 emily | I'm honestly surprised if #include "b.h" works to find y/include/foo/b.h from x/include/foo/a.h even if both are on the include path | 00:36:45 |
| emily | but if it does then I guess it's fine | 00:36:48 |
| John Ericson | I am not sure that works | 00:43:18 |
| John Ericson | there is just the sibling even if not in same path rule | 00:43:34 |
| John Ericson | * there is just the sibling even if on directly on the path rule | 00:43:44 |
| emily | then I'm not sure how ^ ever works | 00:47:10 |
| John Ericson | emily: that's because -I.../nix in the pkg-config` | 01:38:14 |
| John Ericson | and also the meson build time C flags | 01:38:24 |
| John Ericson | * and also the meson when building Nix itself C flags | 01:38:37 |
