[clangd-dev] Clangd on windows+vscode
Ilya Biryukov via clangd-dev
clangd-dev at lists.llvm.org
Wed Jun 12 06:47:00 PDT 2019
Thanks for describing the setup. Clang is generally good at mocking GCC
rules for searching includes and such, but only for widely used targets
(e.g. gcc targeting linux).
However, this does not seem to work as nicely for less supported toolchains
(like the bare-metal arm toolchain you're using).
+Kadir Çetinkaya <kadircet at google.com> is working on adding a cquery-like
configuration mechanism to clangd, that should address your use-case. And
in general, this seems to be a reasonable
fallback mechanism in case we hit a toolchain not well-supported by clang.
At the same time, adding better support for bare-metal arm into clang's
driver would give other benefits:
- other clang-based tools, like clang-tidy, would work without extra
- would allow to more closely mimic various non-include-path flags, which
could also affect correctness for some corner cases;
- allow easy switching (no extra flags needed, etc) from gcc to clang for
the actual builds.
But we don't plan to put more effort of the clangd team into the bare-metal
toolchain's driver. Hopefully someone else will improve this in the future.
On Tue, Jun 11, 2019 at 9:40 PM Michael Steinberg <michsteinb at gmail.com>
> Hi there,
> - I use cmake + ninja, which generates the necessary compile_commands file.
> - I mentioned cquery, which opts to query the compiler found in
> compile_commands for its builtins, as you can ask gcc to disclose them
> - I would prefer not to be locked into actually using clang to build the
> projects, and there are targets which clang does not support
> - I could live really well with clangd ignoring inline assembly and such,
> for which the syntax and availability of features differs between clang and
> Kind Regards
> Am 11.06.2019 um 16:13 schrieb Ilya Biryukov:
> We don't really have alternatives to compile_commands.json that support
> automatic indexing. You could use 'compile_flags.txt', but the
> auto-indexing won't know which files it should feed into.
> - What build system do you use and how did you generate the
> compile_commands.json file?
> - You mentioned ccls could index your project, did it work out of the box?
> If it required user configuration, what was it?
> Clangd relies on clang's code to parse command line, which is *mostly* compatible
> with GCC, but I'm not sure how it handles custom GCC toolchains (and
> whether it handles those at all).
> In general, if you manage to set up your build so that it uses clang and
> generate compile_commands.json from that configuration - it should work
> just fine.
> On Sat, Jun 8, 2019 at 8:59 PM Michael Steinberg via clangd-dev <
> clangd-dev at lists.llvm.org> wrote:
>> Hello again,
>> is there maybe a way to add --include directives for the clangd indexer
>> only? I couldn't find any command line option for this :( I don't really
>> feel like adding around 400 defines through the commandline....
>> Am 03.06.2019 um 11:52 schrieb Kadir Çetinkaya:
>> Could you try adding "-log=verbose" to clangd args? Which can be done by
>> "clangd.arguments": [
>> to your settings.json. Then you should see the diagnostics for those
>> uncompilable errors.
>> Wild guess; it will most likely be fixed with:
>> On Sun, Jun 2, 2019 at 7:40 PM Michael Steinberg via clangd-dev <
>> 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
>>> clangd-dev mailing list
>>> clangd-dev at lists.llvm.org
>> clangd-dev mailing list
>> clangd-dev at lists.llvm.org
> Ilya Biryukov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clangd-dev