| Age | Commit message (Collapse) | Author |
|---|
|
This was just a trick to provide a folder in the build tree where only
artifacts are stored. These artifacts are moved to the root of the build
tree.
This has the disadvantage that they are mixed with other files inside
this folder. Nevertheless they should soon be added by Meson to the file
archive used for deployment which solves this issue because it contains
by definition only artifacts.
|
|
This can be used to order the PCB depending on the manufacturers
software capabilities.
|
|
This presents only the `factory-image.bin` and `update-image.bin` for
MCU firmware. A separate bootloader image is not available.
The reason is that the `factory-image.bin` is used during production
once (flashing at default boot address) to set up the device. Later only
the `update-image.bin` of future versions would be required to remotely
update devices.
|
|
This automatically creates `build/artifacts/factory-image.bin` with the
Meson build system. The resulting file can simply be moved to the
virtual file system of the `nucleo_f767zi` board to flash bootloader and
application making the board ready for operation and remote updates.
|
|
Using the installation step to copy selected artifacts into one folder
was anyway a hack.
This commit shows that the complexity can be reduced by adding copy
targets. The `build/artifacts` folder contains the selected artifacts,
they are always up to date, the user does not have to call the install
step separately and the target definitions do not require
install-related keyword arguments.
|
