grisp/grisp-devkit repository overview

⁠GRISP-DEVKIT

This software bundles our grisp2-rtems-toolchain with rebar3 and Erlang on its side.

You can effectively use this even without having any particular software other then docker.

These are the limitations to take into account when setting up your rebar.config file:

• You are forced to use the shipped erlang release, so set the major version of OTP for grisp accordingly.
• The toolchain path, for now, has to be specified and must be /grisp2-rtems-toolchain/rtems/5
• You can deploy but only in a directory inside the mounted volume

⁠Deploy on local dir:

1. Make sure that OTP major version is the same installed in the image
2. Set {deploy, [ {destination, "_deploy"} ]} undre grisp configuration in rebar3.config
3. mkdir _deploy
4. docker run --volume "/path/to/current/project:/mnt/project" grisp/grisp-devkit:25.3 sh -c "cd /mnt/project && rebar3 grisp deploy"

Note: the image will not cache any grisp package. We suggest to leave the docker container shell opened during development.

docker run -ti --volume "/path/to/current/project:/mnt/project" grisp/grisp-devkit:25.3 sh

⁠Build using the toolchain

To build OTP just make sure you set the toolchain directory precisely as /grisp2-rtems-toolchain/rtems/5.

In future versions this info should be already set as ENV inside the image.

docker run --volume "/path/to/current/project:/mnt/project" grisp/grisp-devkit:25.3 sh -c "cd /mnt/project && rebar3 grisp build"