commit fc72bba55f2fccd57130227eb3e2c5427d1b732b
author Patrick Venture <venture@google.com> Wed Jul 03 07:21:51 2019 -0700
committer Gunnar Mills <gmills@us.ibm.com> Wed Jul 10 13:38:17 2019 +0000
tree eb2dc99dde182c80ebdaccf57c19ab6c8dc4fb60
parent 500f7b6e5b4fe6c739c4c4e8c62e2bfaaf00aea7

cheatsheet: MACHINE is available by default

The MACHINE environment variable is available by default and is the
typical way to specify what machine configuration you wish to build, or
with devtool, modify.

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I59c524846df88be6b25144ceef2fc76e477622bd

cheatsheet.md

diff --git a/cheatsheet.md b/cheatsheet.md
index 0d73b42..bc34ce4 100644
--- a/cheatsheet.md
+++ b/cheatsheet.md
@@ -52,13 +52,11 @@
     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:
+MACHINE environment variable.
 
     $ 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