yocto-bsp: add a LICENSE_FLAGS_WHITELIST blurb for emgd to README
Add a text snippet to the README to say that if emgd-driver-bin is included in the BSP, LICENSE_FLAGS_WHITELIST needs to be set to for a successful build. (From meta-yocto rev: e9437a58a99eefa23402b82a1d9a85e7381e109f) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
f6b2e90fda
commit
7c5c1ad72b
|
@ -65,6 +65,14 @@ You should then be able to build a {{=machine}} image as such:
|
|||
$ source oe-init-build-env
|
||||
$ bitbake core-image-sato
|
||||
|
||||
NOTE: if the '{{=machine}}' machine includes the emgd-driver-bin
|
||||
package (i.e. if the emgd version of the xserver is being used), it
|
||||
has a proprietary license that must be whitelisted by adding the
|
||||
string "license_emgd-driver-bin_1.14" to the LICENSE_FLAGS_WHITELIST
|
||||
variable in your local.conf. For example:
|
||||
|
||||
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14"
|
||||
|
||||
At the end of a successful build, you should have a live image that
|
||||
you can boot from a USB flash drive (see instructions on how to do
|
||||
that below, in the section 'Booting the images from /binary').
|
||||
|
|
Loading…
Reference in New Issue