Excuse if this is a tricky explanation; I'm not sure I understand what's going
on.
I have a C-like language and compiler for which I use clang libraries to do the
preprocessing. My compiler lets users specify `-I` directories for searchpaths
for includes, per usual convention. I'm doing someth
eaders that aren't in the very first included
searchpath -- ONLY for llvm 10, ONLY on Mac, ONLY if I'm doing it through a
second spawned shell (works fine when I directly type the command).
Any guesses?
> On Apr 27, 2020, at 12:00 PM, Larry Gritz via cfe-users
> wrot
blah.osl -> blah.oso
>
>
> Works fine again. I don't have a working theory for what's going on here.
>
> So I know the -I commands are making it to my program, and I know I'm passing
> those paths to libclang, because its own diagnostics list those directorie
I'm using clang libraries to implement the preprocessor for my language -- set
up a CompilerInstance, setDiagnostics, ... DoPrintPreprocessedInput.
When I preprocess code that has a #error or #warning, it just gets reported as
"invalid preprocessing directive" on the clang side, no different tha
