| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Francesco Gazzetta <fgaz@fgaz.me>
|
|
It isn't possible to clear the action cache directly but we can change the
version number and adopt a new cache. Eventually the old (now unused
one) will be cleaned up.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Currently the tests do little more than fire up the simulator and
switch into (and out of) the built in applications. However this is
useful and allows us to fully integrate as a CI job.
Unfortunately the numpy warning from pysdl2 mean we have been forced
to disable all warnings to prevent pytest from collecting and reporting
them.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
- This workflow caches both the Python modules, as well as the arm-none-eabi toolchain itself, in order to save resources and time.
- This workflow is meant to imitate the building instructions as closely as possible for every board.
After the workflow compiles wasp-os for a specific board, it will package the following in separate archives (per board):
- the reloader
- the bootloader (both the standalone and the DaFlasher variations)
- a copy of MicroPython
- a copy of the documentation
- the additional tools that are necessary for interacting with devices running on wasp-os
Signed-off-by: Panagiotis Vasilopoulos <hello@alwayslivid.com>
|
