DEPRECATED > How to publish the RISC-V Embedded GCC binaries?

1 Deprecation notice
2 Commit all project git
3 Edit the build script
4 Push the build script git
5 Check/clone/pull build scripts
6 Build
7 Prepare a new blog post
8 Update the SHA sums
9 Update the Web
10 Create a new GitHub release
11 Update the web link

Deprecation notice

In mid-2019, the RISC-V toolchain binaries were moved from the GNU MCU Eclipse project to the xPack project. The new page is:

https://xpack.github.io/riscv-none-embed-gcc/

All previous releases are still available in the @gnu-mcu-eclipse scope, but were deprecated and are not recommended for new projects.

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

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 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 https://github.com/gnu-mcu-eclipse/riscv-none-gcc-build.git \
  ~/Downloads/openocd-build.git

Build

$ bash ~/Downloads/riscv-none-gcc-build.git/scripts/build.sh cleanall
$ caffeinate bash ~/Downloads/riscv-none-gcc-build.git/scripts/build.sh --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 2016-01-11-riscv-none-gcc-v7-1-1-2-20160110-released.md
name the post like: GNU MCU Eclipse RISC-V Embedded GCC v7.1.1-1-20170702 released.
as download_url use the generic https://github.com/gnu-mcu-eclipse/riscv-none-gcc/releases/
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 ?
gnu-mcu-eclipse-riscv-none-gcc-7.1.1-1-20170702-0625-debian32.tgz

...

Update the Web

commit the gnu-mcu-eclipse.github.io-source 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 gnu-mcu-eclipse.github.io.

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)](https://img.shields.io/github/downloads/gnu-mcu-eclipse/riscv-none-gcc/v7.1.1-1-20170702/total.svg)](); 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.

Update the web link