Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Eclipse Che and debugging large c++ project #12782

Closed
saulide opened this issue Feb 27, 2019 · 5 comments
Closed

Eclipse Che and debugging large c++ project #12782

saulide opened this issue Feb 27, 2019 · 5 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@saulide
Copy link

saulide commented Feb 27, 2019 •
edited
Loading

Description

kind/question
I wanted to use eclipse che as an IDE for not so sophisticated developers as entry point into a big project, so that they can develop some small chunks of code. The whole building of the project is made with help of cmake files. Im aware that with cmake i can build a debug version and also use flag "Eclipse CDT4 - Unix Makefiles" to help some developers to run/debug the project in eclipse locally (then they need to add sources etc). But how can enable debugging in che? Any hints or examples?
@gorkem gorkem added the kind/question Questions that haven't been identified as being feature requests or bugs. label Mar 23, 2019
@che-bot
Copy link
Contributor

che-bot commented Sep 25, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2019
@amisevsk
Copy link
Contributor

Now that we are adding a C++ stack to the sample devfiles we should document debugging if possible.

@amisevsk
Copy link
Contributor

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 26, 2019
@amisevsk
Copy link
Contributor

@saulide Sorry this one got stale; currently Che 7 has preliminary support for C++ debugging -- if you have Che 7 deployed, could you check if the current implementation suits your needs?

You can test the devfile by passing it to a factory on your server: https://<che-server-url>/f?url=https://raw.githubusercontent.com/eclipse/che-devfile-registry/ea8469eaf90192773e8cd47efacea4ceea7cb51d/devfiles/cpp/devfile.yaml

@che-bot
Copy link
Contributor

che-bot commented Mar 25, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 25, 2020
@che-bot che-bot closed this as completed Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gorkem @saulide @amisevsk @che-bot