[clangd-dev] Clangd on windows+vscode

[Michael Steinberg via clangd-dev]

Hello again,

thanks for the pointer. I was a bit puzzled by the outcome until I also 
added the "--synch" option in order to see that all CUs fail out of the 
box because the cross compiler's paths and builtin defines are not 
provided. I suppose that the warnings about unsupported and thus ignored 
compilerflags don't reall hurt.

I have not yet tried further adding all the paths and defines manually 
yet, but if I become restless, I might ;)

It's a shame that this is not yet supported, as the introduction of 
clangd rendered the cquery project abandoned, which actually supported 
this out of the box :(

Michael



Am 03.06.2019 um 11:52 schrieb Kadir Çetinkaya:
> Could you try adding "-log=verbose" to clangd args? Which can be done 
> by adding
> ```
> "clangd.arguments": [
> "-log=verbose",
> ],
> ```
> to your settings.json. Then you should see the diagnostics for those 
> uncompilable errors.
>
> Wild guess; it will most likely be fixed with: 
> https://reviews.llvm.org/D62804
>
> On Sun, Jun 2, 2019 at 7:40 PM Michael Steinberg via clangd-dev 
> <clangd-dev at lists.llvm.org <mailto:clangd-dev at lists.llvm.org>> wrote:
>
>     Hi there,
>
>     I'm trying to get clangd running inside vscode on windows. The
>     project
>     is using the gnu-arm-none-eabi toolchain. For almost all compilation
>     units I get the error message "IndexingAction failed: has
>     uncompilable
>     errors". Is there any way to get more infos about the failure cause?
>
>     Kind regards
>     Michael
>
>
>     _______________________________________________
>     clangd-dev mailing list
>     clangd-dev at lists.llvm.org <mailto:clangd-dev at lists.llvm.org>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/clangd-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/clangd-dev/attachments/20190608/37482c41/attachment.html>