diff options
| author | Adriana Kobylak <anoo@us.ibm.com> | 2019-03-22 13:41:44 -0500 |
|---|---|---|
| committer | Adriana Kobylak <anoo@us.ibm.com> | 2019-04-02 11:23:17 -0500 |
| commit | d5afde3325b0622a2e9d19f41192a88321145014 (patch) | |
| tree | bf5a99b54025ab6f2c1b5ef00661741304607b25 | |
| parent | fb52846db7b094724a3fd7859d90a40d208ade79 (diff) | |
| download | openbmc-docs-d5afde3325b0622a2e9d19f41192a88321145014.tar.gz openbmc-docs-d5afde3325b0622a2e9d19f41192a88321145014.zip | |
cheatsheet: Add instructions to build a machine configuration
The instructions include setting the MACHINE environment variable,
and making this value available to BitBake via BB_ENV_EXTRAWHITE.
Reference:
- https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_EXTRAWHITE
- https://stackoverflow.com/questions/17366984/is-it-possible-to-pass-in-command-line-variables-to-a-bitbake-build
Change-Id: Iab16dfb7e6692e876efd6a23d4455d5aff3d6510
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
| -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. ``` |

