| 20 Feb 2025 |
 John Ericson | yes | 19:10:59 |
| John Ericson | emily: I did the symlink wrong and broke git :D | 19:22:37 |
 emily | still don't think you need an in-source symlink at all :P | 19:23:36 |
| John Ericson | I don't but I think it is an easier first step in some respects | 19:24:41 |
| John Ericson | * I don't either, but I think it is an easier first step in some respects | 19:24:46 |
| emily | FWIW, from some digging it looks like apparently the requiring -I…/nix thing dates back to 2.19… | 19:25:22 |
| John Ericson | I think it is effectively older | 19:25:44 |
| John Ericson | oh requiring | 19:25:49 |
| John Ericson | some things came up because unit tests | 19:25:57 |
| emily | if there's already a list of the header files in the source then it's only a few lines of Meson to loop over them to make an include/ in the build directory that can be used for both installation and downstream internal consumers, right? | 19:27:07 |
| John Ericson | emily: I got weird enough stuff that I am just moving the files the "normal" way | 19:34:09 |
 Robert Hensing (roberth) | clangd might be affected by such a solution, but I don't know that | 19:44:15 |
| John Ericson | emily: header-file-namespacing branch | 22:10:11 |
| John Ericson | the bug churn :) | 22:10:20 |
