gnu-mcu-eclipse / gnu-mcu-eclipse.github.io-source Goto Github PK

The The xPack install paragraph sample commad reads:

$ xpm install @gnu-mcu-eclipse/risc-none-gcc --global

It should be:

$ xpm install @gnu-mcu-eclipse/riscv-none-gcc --global

Replace images with the old tool paths, and update text to refer to the pages below the new MCU group.

Not sure if this should be here, or elsewhere

On a MAC - (new MacBook Pro, Catalina) current instructions to setup opened do not work

Part 1 - when I select the OpenOCD xpack.

the result is this:

/Users/duane/Library/xPacks/@xpack-dev-tools/openocd/0.10.0-12.1/.content/bin

The actual result should be:

/Users/duane/Library/xPacks/@gnu-mcu-eclipse/openocd/0.10.0-12.1/.content/bin

Part 2 -
For some reason - under the MacOS - there is ZERO means to browse to the /home/duane/Library location.

This is evidently COMMON - see here:

http://osxdaily.com/2016/12/12/show-user-library-folder-macos-sierra/

It might be helpful - Perhaps you did this already ... but to have a small single web/wiki page that talks about some of the "Mac-isms" that one must deal with.

This link describes the location where "packs" are stored, it's not obvious how to find this dialog in Eclipse...

Can you describe where/how/Navigation path to find this window in eclipse:

https://gnu-mcu-eclipse.github.io/plugins/packs-manager/#configuration

as @dturner suggested in https://github.com/gnu-mcu-eclipse/gnu-mcu-eclipse.github.io/issues/1 (now no longer visible):

It'd be really convenient if you could add a link to "edit this page" in the site footer. I think this can be achieved with the addition of the following link. The jekyll build should substitute the value for page.path.

<a href="https://github.com/gnu-mcu-eclipse/edit/gh-pages/{{page.path}}">Edit this page</a>

as @dturner suggested in gnu-mcu-eclipse/gnu-mcu-eclipse.github.io#2:

It wasn't clear (to me anyway) that the Packs needed to be downloaded and installed before I could associate a device with a project. The Pack plug-in installation page is very clear though so I have removed Pack plugin information from this page and linked to that one. Hope that's OK.

...

Re-reading the page I stick by my original change. The prerequisites are:

• Packs plugin installed
• Packs downloaded
• At least one device installed

All of which can be encapsulated in a single sentence, or maybe bullet points. Trying to explain these steps in more detail on this page to avoid the reader going through the Packs manager install process is needless duplication of your already excellent guide.

Ultimately it's only a very small point, I figured it out in the end as I'm sure others will.