GNU MCU Eclipse

A family of Eclipse CDT extensions and tools for GNU ARM & RISC-V development

How to publish the RISC-V Embedded GCC binaries?

The RISC-V Embedded GCC binaries are published on GitHub Releases.

Update the Change log

Generally, apart from packing, there should be no local changes.

Open the gnu-mcu-eclipse/info/CHANGES.txt file from gnu-mcu-eclipse/riscv-none-gcc-build.git project git, and copy entries to the web git.

In the web git, add new entries to the Change log (pages/toolchain/riscv/, grouped by days.

Update INFO

Edit the info/INFO.txt file from openocd-build.git and update the latest commits.

Commit all project git

Commit all

  • gnu-mcu-eclipse/riscv-binutils-gdb.git
  • gnu-mcu-eclipse/riscv-none-gcc.git
  • gnu-mcu-eclipse/riscv-newlib.git

Edit the build script

Edit the RELEASE_VERSION variable to point to the actual release.

Push the build script git

Push gnu-mcu-eclipse/riscv-none-gcc-build.git to GitHub.

Possibly push the helper project too.

Check/clone/pull build scripts

Be sure the scripts in gnu-mcu-eclipse/riscv-none-gcc-build.git are up to date.

$ git clone --recurse-submodules \


$ bash ~/Downloads/riscv-none-gcc-build.git/scripts/ cleanall
$ caffeinate bash ~/Downloads/riscv-none-gcc-build.git/scripts/ --all

For more details, see the build page.

Prepare a new blog post

In the web git:

  • add a new file to _posts/riscv-none-gcc/releases
  • name the file like
  • name the post like: GNU MCU Eclipse RISC-V Embedded GCC v7.1.1-1-20170702 released.
  • as download_url use the generic
  • update the date: field with the current date

Close issues on the way. Refer to them as:

  • [Issue:[#22](…)].

Update the SHA sums

Copy/paste the build report at the end of the post as

## Checksums
The SHA-256 hashes for the files are:

a723d8c6870d1808882ea2eaa630a8c60c5cb6bd25dc238091d2f9738298c44a ?


Update the Web

  • commit the project; use a message like RISC-V Embedded GCC v7.1.1-1-20170702-0625 released
  • wait for the Travis build to complete; occasionally links to not work, and might need to restart the build.
  • remember the post URL, since it must be updated in the release page

Note: initially the link to binaries points to the parent releases folder, otherwise Travis will complain and do not publish the site to

Create a new GitHub release

  • go to the GitHub Releases page
  • click Draft a new release
  • name the tag like v7.1.1-1-20170702 (mind the dashes in the middle!)
  • select the corresponding -gme branch
  • name the release like GNU MCU Eclipse RISC-V Embedded GCC v7.2.0-1-20171109
  • as description
    • add a downloads badge like [![Github Releases (by Release)](](); use empty URL for now
    • copy the first paragraph from the Web release page
  • add a link to the Web page [Continue reading »](); use an empty URL for now
  • get URL from web and update the above links
  • attach binaries and SHA (drag and drop from the archives folder will do it)
  • click the Publish Release button

Note: at this moment the system should send a notification to all clients watching this project.

In the web git:

  • download_url:
  • use something like v7.1.1-1-20170702 update link as message

Share on Facebook

  • go to the new post and follow the Share link.
  • DO NOT select On your own Timeline, but On a Page you manage
  • select GNU MCU Eclipse
  • posting as GNU MCU Eclipse
  • click Post to Facebook
  • check the post in the Facebook page