Date: Fri, 29 Mar 2024 05:16:29 +0000 (UTC) Message-ID: <2100372458.17751.1711689389328@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17750_1793978144.1711689389328" ------=_Part_17750_1793978144.1711689389328 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is the summary page that describes the CMF RDK-B iteration 2.1-2016= 0328. Iterations are CMF snapshots = of RDK development code.
Baseline | CMF-20160328 |
Updates from Comcast 2016-03-28. |
Post-baseline updates | ||
TDK | N/A | |
Manifest | rdkb-2.1-20160328 |
$ mkdir rdkb $ cd rdkb $ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-= 2.1-20160328 $ repo sync -j4 --no-clone-bundle $ source meta-cmf-rdkb-bsp-emulator/setup-environment (select qemux86broadb= and) $ bitbake rdk-generic-broadband-image
-m rdkb.xml
in the build sequence above is i=
mportant. If this is not specified, you will get an RDK-V tree by default.<=
/li>
-b rdkb-2.1-20160328
in the build sequence a=
bove specifies the branch to use. If you omit the -b rdkb-2.1-20=
160328
entirely, you will get the master (HEAD) of each compone=
nt. Right now they are the same, but that will change with time.-b rdkb-2.1-20160328
in the repo init&nbs=
p;command. However, unlike RDK-V, we are going to be batch updating RDK-B o=
n a 2-weekly cycle for the moment.