...
You can then run the build cycle for each target:
| Code Block | ||
|---|---|---|
| ||
$ bitbake mc:generic:rdk-generic-broadband-image && \ bitbake mc:raspberrypi:rdk-generic-broadband-image && \ bitbake mc:armqemu:rdk-generic-broadband-imagemkdir rdkb-arm $ cd rdkb-arm $ repo init -u 'https://github.com/rdkcentral/meta-rdk-bsp-arm/' \ -m "manifests/rdkb-bsp-arm.xml" \ -b "develop" $ repo sync $ MACHINE="all" source meta-rdk-bsp-arm/setup-environment $ bitbake mc:generic:rdk-generic-broadband-image && \ bitbake mc:raspberrypi:rdk-generic-broadband-image && \ bitbake mc:armqemu:rdk-generic-broadband-image Cherry-pick below PRs to have support to WAN interface (erouter0), WebUI and SSH features. https://github.com/rdkcentral/ethernet-agent/pull/40 https://github.com/rdkcentral/webui/pull/81 https://github.com/rdkcentral/meta-rdk-bsp-arm/pull/53 https://github.com/rdkcentral/meta-rdk-bsp-arm/pull/50 The default ARM build have been updated to support SSH. PR: https://github.com/rdkcentral/utopia/pull/175 |
(Due to the way RDK-B components are built, it is not possible to do a "parallel" build for two targets at once, however, you will
still save a significant amount of time and disk space by using multiconfig builds sequentially)
...