Closed dch closed 2 years ago
@dch Can you post your rebar.config
? It looks like you don't have the target GRiSP Erlang version configured there... (if so, we should really have a better error for that)
{build, ...}
section configured in the GRiSP configuration in rebar.config
This should now be solved in version 2.2.0 by running rebar3 grisp package list
to see which pre-built versions exist. In addition, selecting a partial version (like "23"
) will automatically select the latest available package when deploying.
I'm assuming a great deal from this blog post1 that if I have e.g. OTP20.x from my system package manager, then I should be able to produce a grisp release without needing to build RTEMS from scratch, if:
I've tried with the 2 latest OTP releases (OTP 21, OTP 20) and haven't had great success, using the robot example with included wifi support:
some questions: