BMC/tmp/openbmc.git/setup, branch 2.12.0

setup: enable all qemu* machines

2022-04-07T20:36:34+00:00

The existing support for qemuarm wasn't working. Sometimes, when submitting recipes to upstream, it is useful to test image builds against various qemu* machine models. Enhance the setup script so that we can build any of the qemu* machines that Poky supports and treat them like a generic meta-phosphor machine. Tested: Used `setup qemumips` and was able to `bitbake phosphor-image` successfully. Signed-off-by: Patrick Williams Change-Id: Ide141c879dd674fe3771984f7fd41006a64ce54f

setup: retab to soft-tabs

2022-04-07T19:37:24+00:00

Change-Id: Id9d3d4ff314c0635f9f5ad6fc81d5f19977f65c1 Signed-off-by: Patrick Williams

setup: handle invalid machine argument more gracefully

2022-01-28T12:39:08+00:00

If 'setup' is sourced with an invalid machine name, the error message is now sent to stderr and the failure is propagated back up the stack with a non-zero return value. Change-Id: I50ad40b58c1479ce9ee80ea52536075eddd09b4c Signed-off-by: Zev Weiss

setup: fix shellcheck errors

2021-11-03T23:09:42+00:00

Signed-off-by: Patrick Williams Change-Id: I4c09e61294506659500f9760993dd4b8b6f22f23

setup: skip non-phosphor machines

2021-02-20T01:49:38+00:00

We already had logic to skip non-phosphor machines in the 'list' operation, but did not skip those machines when targeting them. Those machines are almost certain to not operate as expected and in some cases, such as EVB models, we have two meta-layers associated with the machine. Skipping non-phosphor machines ensures that the setup script picks the right configuration and does not attempt to target a machine that won't work. Signed-off-by: Patrick Williams Change-Id: If68c27e2a8675405672df497827dde6e86147108

setup: tolerate `which` failures

2021-02-19T21:10:20+00:00

If this script is sourced in a shell that has something like `set -e`, then it fails if the column program does not exist because the `which columm` fails. Make a few changes to tolerate this and not fail: - Use $(...) rather than `...`. - Use `... || true` when appropriate to allow continuance. Signed-off-by: Patrick Williams Change-Id: I9008778e8aee4747faa4decff74a2fb361a206ed

setup: support any level of machine conf depth

2021-01-27T22:00:40+00:00

Modify setup script to support any level of machine conf depth. Internally Google uses machines that sit yet another layer deep in the repository. Instead of adding yet another level of depth to the expansion, look for all configs using `find`, if it's available. If it's not, ball back to the old wildcard expansion. Signed-off-by: Maksym Sloyko Change-Id: I1066fe5f6ece4454e3555ca97f75bd91d6da1dba

setup: support single-deep machine conf directories

2020-05-01T13:10:48+00:00

The witherspoon config was moved directly into meta-ibm, which caused the setup script to not be able to find it. Modify the setup script to also find machine config files in single-deep meta directories. Signed-off-by: Patrick Williams Change-Id: Icb24649c2e90cd29f72e8b661085b85cde6fcad5

setup: Use machine-specific build directories by default

2020-04-27T22:08:58+00:00

bitbake can struggle to cope with switching machine configurations in the one build directory, so default to using machine-specific build directories. It's recommended that the following be added to your .profile to provide a common location for bitbake data caches: ``` BB_ENV_EXTRAWHITE="SSTATE_DIR DL_DIR" SSTATE_DIR="/var/cache/bitbake/sstate-cache" DL_DIR="/var/cache/bitbake/downloads" export BB_ENV_EXTRAWHITE SSTATE_DIR DL_DIR ``` Change-Id: I70abb6a6bc901c42266f92c9f8c230b793b7a0f9 Signed-off-by: Andrew Jeffery

setup: filter out unsupported machines

2020-04-08T15:32:27+00:00

Due to the import of meta-layers from out of openbmc, some of which have their own machine configs, running `source setup` reveils a long list of machines many of which are unsupported. Any supported machine should be using the `meta-phosphor` layer in some way, so look for that in the `bblayers.conf.sample` file. Signed-off-by: Patrick Williams Change-Id: I3ee4aa33a643d5f7faf0c6e1bd6f3d9c84cddab8