Martin Storsjö
Martin Storsjö
Hmm, so to get the full picture - when you generate your `compile_commands.json`, you have the llvm-mingw tools added to `$PATH`, and your build system, which generates the json file,...
> But it appears to work on Windows without the path. Why would there be a discrepancy? That's indeed odd. Perhaps the last-call default fallbacks differ - on Unix assuming...
> Just to be clear, Clangd relies on heuristics on some level to find stuff (it's stated in its documentation), so it seems to me that, if the compiler driver...
> > did you happen to have that path added when you started clangd there? > > Nope, I never add toolchains on PATH except in the terminals I actively...
> > > did you happen to have that path added when you started clangd there? > > > > > > Nope, I never add toolchains on PATH except...
Thanks - I think this is fine with me. In https://github.com/mingw-w64/mingw-w64/commit/a4c0c1d00d140d69a2c72f6ca0d49c91bdb2b08c we adjusted the mingw-w64 headers in anticipation that this gets merged in Clang 19, so it'd be good to...
Compared with the original PR, inconsistencies about backslash escaping in lit substitutions and such are now fixed, so that allowed getting rid of changes to lit itself from this PR.
Ping, what do the libcxx maintainers think about this one? Happy to try taking it in one direction or another.
Ping, any directions on what you want around this one?
Ping @ldionne, can you follow up on this one? This one is required to keep having the tests pass on Windows 11 and Windows Server 2025 (the latter is available...