The problematic part with this name is that it is from the Roman mythology and not, as most of our products, from the Greek. Phoenix is already taken though by a charger...
First of all, make sure you really want to rebuild a complete rootfs, it takes time to compile, lots of diskspace and results in an image / sdk which already available anyway, in binary form.
Anyway, if you insist: this repo is the starting point to build Venus. It contains wrapper functions around bitbake and git to fetch, and compile sources.
For a complete build you need to have access to private repros of Victron Energy. Building only opensource packages is also possible (but not checked automatically at the moment).
For further documentation on Venus, see the Venus OS wiki.
Venus uses the OpenEmbedded, the Yocto Project build system architecture. For an introduction, start with reading their wiki and the glossary.
Building Venus requires a Linux. At Victron we use Ubuntu for this.
# clone this repository
git clone https://github.com/victronenergy/venus.git
cd venus
# install host packages (Debian based)
sudo make prereq
# fetch needed subtrees
# use make fetch-all instead, if you have access to all the private repos.
make fetch
That last fetch command has cloned several things into the ./sources/
directory. First of all there is bitbake,
which is a make-like build tool part of OpenEmbedded. Besides that, you'll find
openembedded-core and
various other layers containing recipes and other metadata defining Venus.
Now its time to actually start building (which can take many hours). Select one of below example commands:
# build all, this will take a while though... it builds for all MACHINES as found
# in conf/machines.
make venus-images
# build for a specific machine
make ccgx-venus-image
make beaglebone-venus-image
# build the swu file only
make ccgx-swu
# build from within the bitbake shell.
# this will have the same end result as make ccgx-swu
make ccgx-bb
bitbake venus-swu
Above Getting Started instructions will automatically select the config that is used for Venus OS as distributed. Alternative setups can also be used, e.g. to build for a newer OE version:
make CONFIG=rocko fetch-all
To see which config your checkout is using, look at the ./conf symlink. It will link to one of the configs in the ./configs directories.
For each config there are a few files:
repos.confcontains the repositories which need to be checked out. It can be rebuild withmake update-repos.conf.metas.whitelistcontains the meta directory which will be added to bblayers.conf, but only if they are actually present.machinescontains a list of machines that can be build in this config
To add a new repository, put it in sources, then checkout the branch you want and
set an upstream branch. The result can be made permanent with: make repos.conf.
Don't forget to add the directories you want to use from the new repository to metas.whitelist.
Repos is just like git submodule foreach -q git, but shorter, so you can do:
./repos push origin ./repos tag xyz
it will push all, tag all etc. Likewise you can revert to a certain revision with:
./repos checkout tagname
# patches not in upstream yet
./repos cherry -v
# local changes with respect to upstream
./repos diff @{u}
# local changes with respect to the push branch
./repos diff 'origin/`git rev-parse --abbrev-ref HEAD`'
or if you have git 2.5+ ./repos diff @{push}
./repos log @{u}..upstream/`git rev-parse --abbrev-ref @{u} | grep -o "[a-Z0-9]*$"` --oneline
Changing the distro version can cause some sdk packages fail to compile, this should fix that bitbake -c cleanall nativesdk-gettext nativesdk-gmp nativesdk-gdbm nativesdk-glib-2.0 nativesdk-qt4-tools