BMC/Intel-BMC/openbmc.git/setup, branch validation

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

setup: support zsh

2020-01-21T12:28:09+00:00

zsh populates $0 even when sourcing a script. This caused sourcing this script to think that it was being executed and it `exit 1`d the running shell. Since no sane distribution would ever set /bin/sh to zsh, the presence of $ZSH_NAME implies that the script is being sourced. Tested with both bash and zsh in both modes of operation. Signed-off-by: Patrick Williams Change-Id: I2843d96a7fdaa46f9ee6edb9031ca9c16ca3bd98

Make `setup` show available targets in columns

2019-08-08T15:56:29+00:00

The list of targets is getting longer and tends to not fit into one screen when displayed in one column. Filter it through `column` tool if available. If not available, then fall back to the old representation. Change-Id: I1e827d0835608d2e37ca58705e77a14b0667b170 Signed-off-by: Alexander Amelkin

setup: Add the missing quotes

2019-06-18T19:05:24+00:00

Fixes: d70e7e81bfd44553f425f (setup: Use config name instead layer name) Change-Id: Iee4a49f31bfbe137532f9be30277857d408cf7d5 Signed-off-by: Alexander Filippov

setup: Use config name instead layer name

2019-06-11T20:51:05+00:00

Allows user to pass a config name instead of a layer name. This can be extremely useful for layers, which contain several configs. E.g. to build firmware for swift you can call: ``` . setup swift bitbake obmc-phosphor-image ``` Change-Id: I397a53b0cc135f622e4b3dc712ff93f6a0c10b8a Signed-off-by: Alexander Filippov

setup: Allow user to pass in the build directory name

2018-09-28T14:04:49+00:00

This can be extremely useful if one is working on multiple platforms simultaneously Change-Id: I316ef106d972413221ab2691dfc727f8f9bcffa8 Signed-off-by: Amithash Prasad Signed-off-by: Brad Bishop

[Subtree] Bring openbmc machines to top level

2018-08-23T16:39:42+00:00

The new subtree model brings the subtrees up from the openbmc-machines layer. Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0 Signed-off-by: Dave Cobbley Signed-off-by: Brad Bishop

Refix 68a967d: setup: Fix subshell spawning

2018-04-26T12:52:40+00:00

* Fix subshell spawning due to `sort`. Subshell spawning effectively prevented the script from working. Now `sort` is only invoked for `setup` without arguments; * Add a license/copyright header Change-Id: I643a91cae14e5ddb8e6efe154d325baaab3d0100 Signed-off-by: Alexander Amelkin