RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
The following commands fetches the source code of emulator using repo tool
$ mkdir emulator && cd emulator
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
mkdir emulator && cd emulator repo init -u https://code.rdkcentral.com/r/ |
...
manifests -m |
...
rdkv-nosrc.xml repo sync |
Note: For latest code iteration, check the RDK-V Releases page to get the latest iteration branch |
---|
|
$ repo sync
$ source meta-cmf/setup-environment
The above step configures and sets up your directory to start an appropriate build for hybrid or media client.
...
Following options are just a sample guide:
For HybridMediaclient:
Select option for qemux86hyb-morty - 1 if you need to build a hybrid device.
Note: For RDK2.1 emulator builds, the option would be option 3.
For Media Client:
Select option qemux86mc-morty - 2 if you need to build a media client device.
Next, you would need to initiate the build using the following command:
For Hybrid:
$ bitbake rdk-generic-hybrid-image
For Media Client:
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
MACHINE=qemux86mc-morty source meta-cmf/setup-environment
bitbake rdk-generic-mediaclient-wpe-image |
For Hybrid:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
MACHINE=qemux86hyb-morty source meta-cmf/setup-environment bitbake rdk-generic-hybrid-wpe-image |
On Successful build, the ROOTFS (in vmdk format) would be available at the following reference location based on whether your build type was Hybrid (qemux86hyb-morty) or Media Client (qemux86mc-morty):
...