Reference implementation for the Armbian framework for unofficial boards by having a unique device completely configured via userpatches.
it's best let armbian build framework use docker on your behalf.
this means 2 things.
- install docker
- add your user account to the
docker
user group so that docker can be ran without sudo
that might look like this
sudo apt install docker.io -y
sudo usermod -a -G docker ${USER}
logout
git clone https://github.com/armbian/build.git
cd build
git submodule add -f -b main https://github.com/lanefu/armbian-userpatches-example-indiedroid-nova.git userpatches
will prompt for menus etc
./compile.sh nova
uses config-nova-sid.conf
to build a cli based debian sid image
./compile.sh nova-sid
uses config-nova-gnmoe-bloated.conf
to build a gnome desktop bloated by most application groups selected
./compile.sh nova-gnome-bloated
uses config-opinionated.conf
to build a debian sid cli image with custom ssh keys, strip out the normal interactive setup. ready to boot.. and names itself princess-sbc
Read the armbian docs to better understand the power available in the armbian build framework
Hookpoints allow you to make
add functions prefixed with any of these hook points in your config file.
you can use them to use existing functions or extensions
Extensions are a pluggable way to add a rich library of functions to armbian build framework. Once enabled via a enable_extension
call, They are generally available for use anywhere.
https://docs.armbian.com/Developer-Guide_Extensions/#what-is-an-extension "Specifically, extension files should not contain any code outside of functions – they should do nothing when sourced."
NOTE slight edge-case that hooks related to build dependencies may get executed durring the Docker bootstrapping for cache management purposes regardless of being enabled... those extensions aren't otherwise available unless enabled with enable_extension