The various branches (other than this one) available here will configure the repo build for the appropriate branches in each repository and clone them in the typical fashion, ie, with either poky or oe-core as the parent directory and the additional metadata layers underneath (as documented in the upstream setup).
The 2 main choices are:
- The yocto BSP (and poky reference distribution) with meta-openembedded metadata plus meta-pine64/meta-rockchip BSPs and meta-small-arm-extra
- The openembedded-core metadata with meta-pine64/meta-rockchip BSPs, plus
meta-openembedded metadata and meta-small-arm-extra for additional recipes
- The more recent release layers have additional metadata (layers) such as meta-uav and meta-browsers; add to bblayers.conf as needed
- There are additional kernel and u-boot recipes in meta-small-arm-extra based on the latest patches and mainline branches
Note that oe-core will build "distroless" by default, however, you can set DISTRO = "vctlabs" in your local.conf. See the meta-small-arm-extra README file for manual config setup for the extra kernel recipes.
There are (or will be) several branches for each of the above choices. Select the main build branch using the github branch button above, which will select the correct manifest branches and BSP/metadata using the respective branches in this repo as shown below.
Follow the steps in the readme for the branch you select, then use the same branch name with the "repo init" command. This will checkout the corresponding branch HEAD commits on the configured branch for each repository.
You can get status and more using the repo command in the top level directory
once you've run the repo init and repo sync commands. Try:
$ repo info $ repo show $ repo status
See the default.xml file for repo and branch details; the following example is generic so go back and select a branch from this repo.
$ mkdir ~/bin $ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repo
$ PATH=${PATH}:~/bin
$ mkdir rockwinner-bsp
$ cd rockwinner-bsp
$ repo init -u https://github.com/VCTLabs/vct-rockwinner-bsp-platform -b poky-fido
$ repo sync
At the end of the above commands you have all the metadata you need to start building with poky and meta-oe on fido branches.
To start a simple image build:
$ cd poky
$ source ./oe-init-build-env build-dir # you choose name of build-dir
$ ${EDITOR} conf/local.conf # set MACHINE to roc-rk3328-cc
$ bitbake core-image-minimal
You can use any directory (build-dir above) to host your build. The above commands will build an image for beaglebone using the core yocto BSP machine config and the default yocto-linux kernel. You can replace the default BSP config with either meta-ti or the meta-beagleboard BSP. This will provide a more Beagle-centric set of defaults for kernel and bootloader, as well as a bigger selection of kernels and TI support tools.
The main source code is checked out in the bsp dir above, and the build dir will default to poky/build-dir unless you choose a different path above.
Download the manifest source here:
$ git clone https://github.com/VCTLabs/vct-rockwinner-bsp-platform
Replace the repo init command above with one of the following:
For developers - hardknott
$ repo init -u https://github.com/VCTLabs/vct-rockwinner-bsp-platform -b oe-hardknott
For intrepid developers and testers - master
Patches are typically merged into master-next and then are merged into master after a testing and comment period. It’s possible that master has something you want or need. But it’s also possible that using master breaks something that was working before. Use with caution.
$ repo init -u https://github.com/VCTLabs/vct-rockwinner-bsp-platform -b oe-master