| 20 Feb 2025 |
 John Ericson | that solution avoids moving source files around, which will make Eelco happy. (More seriously, it will keep the headers next to their corresponding sources, which he said he likes) | 18:38:44 |
 emily | why can't you just do #include <nix/…> in the headers, have src/lib<blah>/include/nix be where the headers are, and add the built lib<blah>s as normal Meson dependencies? | 18:39:02 |
| emily | I don't think you need any symlink hacks to make that work | 18:39:07 |
| John Ericson | you need the symlink hack if you want foo.hh next to foo.cc | 18:39:23 |
| John Ericson | I am happy to have that conversation with the rest of the team, but I don't think we should be blocked on that | 18:39:53 |
| John Ericson | the symlink hack is only in the source tree | 18:40:03 |
| John Ericson | in the installed outputs, everything is normal | 18:40:13 |
| John Ericson | and also importantly, were not doing anything like sedding-in the #include "nix/... either, which would screw over meson subproject stuff | 18:40:41 |
| emily | alright. well since it doesn't affect any downstream user I guess it doesn't really matter. just seems silly to me | 18:40:47 |
| John Ericson | (and I do use that, to work on hydra and nix-eval-jobs and nix all at once, it's nice!) | 18:40:56 |
| emily | I think you could construct the symlink hack inside the Meson build rather than polluting the source tree with it. | 18:41:04 |
| emily | it supports generated include stuff etc. | 18:41:09 |
