search

zephyrproject-rtos / zephyr

Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
https://docs.zephyrproject.org
Apache License 2.0
10.43k stars 6.39k forks source link

doc: "Debug with Eclipse" doc needs to be refreshed (and eventually moved to Tools and IDE) #61515

Open kartben opened 1 year ago

kartben commented 1 year ago

Describe the bug

The instructions at https://docs.zephyrproject.org/latest/develop/application/index.html#debug-with-eclipse are over 5 years old (!) and need to be updated. They are refering to very old versions of Eclipse (with very old download links too), and what's more GNU MCU Eclipse is now officially part of "Eclipse IDE for Embedded C/C++ Developers" so install instructions should now be much simpler. We also have a "Tools and IDEs" doc section which would be a better home for these instructions anyways.

To Reproduce

Follow the instructions at https://docs.zephyrproject.org/latest/develop/application/index.html#debug-with-eclipse and get confused right from step 1 as it's giving red warnings about the fact you're about to download an Eclipse version from 2017 :)

Expected behavior

Documentation contains state of the art instructions for using Eclipse for debugging (and potentially building too?) Zephyr applications (or no instructions at all if we cannot get this fixed in the reasonable future). Note: CMake "Eclipse CDT4 - Ninja" generators recently got deprecated -- not sure what this means in terms of the recommended way to turn a zephyr app into a proper Eclipse CDT project now. See https://cmake.org/cmake/help/latest/generator/Eclipse%20CDT4.html

Also, not sure pyOCD is needed and openOCD plugin should just work?

Impact

False advertising as the outdated instructions will probably leave anyone trying them with a bad impression

Logs and console output

N/A

Environment (please complete the following information):

3.4.99 documentation as of August 15

Additional context

N/A

github-actions[bot] commented 10 months ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

github-actions[bot] commented 8 months ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

github-actions[bot] commented 6 months ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

github-actions[bot] commented 3 months ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

github-actions[bot] commented 1 month ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.