summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2024-04-26 19:41:00 +0100
committerLeah Rowe <leah@libreboot.org>2024-04-26 20:36:42 +0100
commitce7fd754a3d831c563a8589f1cc35e55ce027814 (patch)
treed6cd5435b7759e919dd34a42243cb3b4e191ce2f /COPYING
parenta2f423535840382d72bfa1ae1e1cb5c06e4f8604 (diff)
build/roms: report status when building images
export LBMK_VERSION_TYPE=x x can be: stable, unstable in target.cfg files, specify: status=x x can be: stable, unstable, broken, untested if unset, lbmk defaults to "unknown" if LBMK_VERSION_TYPE is set, no confirmation is asked if the given target matches what's set (but what's set in that environmental variable can only be stable or unstable) if LBMK_RELEASE="y", no confirmation is asked, unless the target is something other than stable/unstable "unstable" means it works, but has a few non-breaking bugs, e.g. broken s3 on dell e6400 whereas, if raminit regularly fails or it is so absolutely unreliable as to be unusable, then the board should be declared "broken" untested means: it has not been tested With this change, it should now be easier to track whether a given board is tested, in preparation for releases. When working on trees/boards, status can be set for targets. Also: in the board directory, you can add a "warn.txt" file which will display a message. For example, if a board has a particular quirk to watch out for, write that there. The message will be printed during the build process, to stdout. If status is anything *other* than stable, or it is unstable but LBMK_VERSION_TYPE is not set to "unstable", and not building a release, a confirmation is passed. If the board is not specified as stable or unstable, during a release build, the build is skipped and the ROM is not provided in that release; this is in *addition* to release="n" or release="y" that can be set in target.cfg, which will skip the release build for that target if "n" Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions