Skip to main content
aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-11-10Bug 540978 Rename lsp plugins to be org.eclipse.cdt.lsp.*Doug Schaefer6-71/+0
To make it clear these are CDT's future :). Change-Id: I64935e3998a46632f4f4006589a17eb01959eb27
2018-06-28Bug 535427 - Add the lsp4e-cpp plugins to the buildNathan Ridge1-1/+1
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
2017-09-01A basic LSP4E integration with ClangdMarc-Andre Laperle6-0/+71
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>

    Back to the top