This avoids either littering lsp4e-cpp code with "restriction"
warnings, or suppressing them (which can hide useful warnings).
It seems pointless to expose the relevant internals as public APIs
since lsp4e-cpp is conceptually an internal consumer.
Change-Id: I9d8c70570682fa86b2369445a812af14de4930e6
To build and run only lsp4e-cpp tests do:
mvn verify -P skip-tests-except-lsp4e-cpp
Also-by: Jonah Graham <jonah@kichwacoders.com>
Change-Id: Id6f3cd8ae291283c0cad7f1e63fbcdce683f4d2d
Not sure we have the right dependency in the cdt target file but
I get a compile error when I use it.
Change-Id: Ie357ea76da82ac552b6c95662d725fb660434ff6
FileEvents are useful for indexing and lsp4e (so far) does not send
them. It is not clear whether or not this will be implemented in lsp4e.
In the mean time, lsp4e-cpp can have its own mechanism to generate
the events.
Change-Id: I09aac4fda7755260f47b73fd683ca6d2ad317f81
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
This plug-in adds an simple integration between LSP4E and Clangd.
It simply launches clangd when opening C/C++ files with the
Generic Editor.
To try it, you need to:
- Import the projects in your Eclipse workspace (you can only import the
lsp4-cpp ones, the sources for CDT are not needed)
- Open lsp4e.cpp-staging.target and set it as the target platform
- You need to have clangd built and on the PATH. See
https://clang.llvm.org/get_started.html
- Start Eclipse: right-click on a project > Run as > Eclipse Application
- In the new Eclipse instance, you can right-click on a C/C++ file >
Open As > Generic Editor. This should make use of clangd, providing some
basic diagnostics and formatting commands.
This should help the Eclipse community to start playing with Clangd.
Change-Id: I688d3a952dbc80d9f61186178f3c8a033afcc587
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
