eclipse-cdt-cloud / cdt-cloud Goto Github PK

clangd-contexts is an API for management of clangd configuration files in C/C++ projects using contexts. A context is the set of flags, parameters, other settings and source files that clangd uses as input. This library works with the compilation database (compile_commands.json file) and compile flags in the .clangd file for a project.

Originally, this component was intended to be contributed to Eclipse Theia / CPP Extensions (see PR). However, after some discussions with the original author @cdamus and the project leads of Eclipse Theia and CDT.cloud, we concluded that this component is an excellent addition and perfect fit for the CDT.cloud scope.

This could be a good way to make it even clearer that this project is not Open Source in name only.

Would increase visibility of community efforts.

We should get a trace to best illustrate the capabilities of trace compass cloud while being easy to read. Candidates:

• ls (userspace and kernel format) It features a stutter in a for loop, and a recursion.
• Trace Compass Trace (Trace Event format)
• apt-get (kernel format) showing the O(n2) man page rebuilding.

I need to be blunt, I am not sure what is the most interesting for an every day user.

The theia-trace-extension and related repos have been transferred to the eclipse-cdt-cloud GitHub organization.

Before the transfer, the GitPod GitHub app was enabled to use the GitHub integration. It's has been useful for quick code reviews, and the theia-trace-extension uses it for a demo application for user's to try.

I'd like to enable GitPod GitHub app for the eclipse-cdt-cloud GitHub organization. As far as I know GitHub apps need to be installed on the GitHub organization level and not per repository.

Are there any objections for me requesting access for eclipse-cdt-cloud (see screenshot below)? Please let me know.

The Memory Inspector is a very powerful UI delivering the best Memory View in the market today. However today it is tied to Theia and cannot be used in VSCode as an extension.

There have been preliminary discussions at the Embedded SIG about moving the memory inspector to its own extension that can be consumed by VSCode or Theia.

Interested parties in this work include ARM, Ericsson and Renesas. Specifically @colin-grant-work, @thegecko, @jonahgraham have shown interest in contributing to this work.

This issue is the umbrella to track making it its own extension. Once there is a git repo for the extension it is expected that this issue will be moved to that repo.

As discussed with Discussion #1 it would be good to integrate code checker into cdt.cloud.

Source
https://open-vsx.org/extension/codechecker/codechecker/reviews

Acceptance criteria:

• Works
• Doesn't break with GCC
• make sure set up is simple.