• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 2053 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Run configuration: "C/C++ local Application" is missing

Rob Maris
Expert 1620 points


While having activated the standard C/C++ perspective, I'd expect to see both local and remote Application categories within the run configuration dialog. However, I only see the remote option.

I checked it with a fresh Eclipse CDT-based download (Luna, 4.4.2). There the run configurations is complete.

Consequently, I cannot run a standard GCC-based project from within eclipse. I don't find any helpful hints about this. I hope it's a CCS-related problem - then the question is right here ;)

  • 0
    Guru 92251 points

    Rob Maris said:
    However, I only see the remote option.

    To get the option to to debug a native (local) application you need to enable "CDT GDB debugging" in CCS as detailed on develop a PC application with CCS

  • 0 in reply to Chester Gillon
    Expert 1620 points

    Thanks, that's it. And... I didn't find such a comparable entry using the search function.

    However, It would be better, when a hint is expressed in the run configuraition window itself, as is the case with the project properties dialog window, where you can tick extended mode (on the bottom of the window), to open the standard settings tree that is eclipse standard. Such a hint would save expensive time.

    In general, I consider following:

    Upon Installation of CCS, an option is offered to add the TI-plugins to an existing Eclipse, or not. In the case that using an existing Eclipse would NOT alter default constructs in Eclipse, this would be the favoured installation method for experienced Eclipse users. Then it would be helpful to add a link to a pro/con document of installing CCS standalone or as a plugin-set. The link should be presented during install, as is comparably also the case with Linux installs, where the user is pointed to additional documentation.