diff options
| -rw-r--r-- | cheatsheet.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/cheatsheet.md b/cheatsheet.md index 544a35f..0d73b42 100644 --- a/cheatsheet.md +++ b/cheatsheet.md @@ -44,6 +44,23 @@ $ TEMPLATECONF=meta-ingrasys/meta-zaius/conf . openbmc-env $ bitbake obmc-phosphor-image ``` +## Building a specific machine configuration + +If the system you want to build contains different machine configurations: + + meta-<layer>/meta-<system>/conf/machine/machineA.conf + meta-<layer>/meta-<system>/conf/machine/machineB.conf + +You can specify the machine configuration you want to build by setting the +MACHINE environment variable. Then add `MACHINE` to the BB_ENV_EXTRAWHITE +environment variable to make the new MACHINE value available to BitBake: + + $ cd openbmc + $ TEMPLATECONF=meta-<layer>/meta-<system>/conf . openbmc-env + $ export MACHINE="machineB" + $ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MACHINE" + $ bitbake obmc-phosphor-image + ## Building the OpenBMC SDK Looking for a way to compile your programs for 'ARM' but you happen to be running on a 'PPC' or 'x86' system? You can build the sdk receive a fakeroot environment. ``` |
