enoch/armbian-build
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
The official build framework for the Armbian Linux distribution. This repository contains the complete toolchain and scripts required to compile custom OS images from source, including kernel configuration, U-Boot handling, and board-specific tweaks for various ARM and ARM64 single-board computers.
6,580 Commits 95 Branches 139 Tags 940 MiB
Shell 71.5%
Python 9.1%
GSC 8.5%
Batchfile 3.9%
QML 1.6%
Other 5.4%
78d28f8083
Go to file
zhangn1985 78d28f8083 rebase sunxi-next to upstream LTS (#1507) 
1, format all patches from https://github.com/megous/linux
   `git format-patch 79bf89b88a87f2ebf147f76d8c40183283b49b51...2a7cb228d29c3882c1414c10a44c5f3f59bfa44d`
   and copy them to sunxi-next with prefix `0000-`

2, remove unnecessary patches, due to they are revert of upstream patches:
    4d867e2bd6
    4e674a3000
    b8e05fe47e
    8bb8175edd
    a2888276ee

3, remove fail to apply and no use:
    960ddd63a8

4, remove WireGuard patch:
    1cd13b836c

5, remove meaningless patch:
    f26e36379a

6, remove merged or included by megous/linux patches:
   0112-mfd-axp20x-Add-supported-cells-for-AXP803.patch
   board-bpi-m3-make-ethernet-working.patch
   board-pine-h6-pine-h6-0025-phy-sun4i-usb-add-support-for-missing-USB-PHY-index.patch

7, remove stable release update patches.
   ignored.

8, rebase sunxi-next/sunxi64-next to upstream linux-4.19.y

test result:
   all patches applied, no error.
   orangepipc/orangpioneplus build OK.

Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
2019-08-06 21:00:05 -04:00
.github Create FUNDING.yml 2019-06-16 18:53:35 +02:00
config rebase sunxi-next to upstream LTS (#1507) 2019-08-06 21:00:05 -04:00
lib merge KVIM1 u-boot blobs to odroidc2-blobs 2019-08-05 12:42:02 +08:00
packages Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) 2019-07-31 12:51:00 +02:00
patch rebase sunxi-next to upstream LTS (#1507) 2019-08-06 21:00:05 -04:00
.dockerignore Improve Docker support 2017-08-01 12:30:34 +03:00
.gitignore Add USERPATCHES_PATH optional setting to config file. (#1450) 2019-07-09 22:50:49 -04:00
compile.sh Add USERPATCHES_PATH optional setting to config file. (#1450) 2019-07-09 22:50:49 -04:00
config-docker.conf Bugfix 2019-07-11 07:51:25 +02:00
config-vagrant.conf More automation for Vagrant environment 2017-09-05 17:04:21 +03:00
Dockerfile Docker speedup - adding pigz to the Docker package base 2019-07-18 21:07:04 +02:00
LICENSE Create LICENSE 2014-10-08 10:14:29 +02:00
main.sh Add migration checks and messages 2017-08-01 12:28:19 +03:00
README.md Update README.md 2019-01-15 12:22:56 +01:00
Vagrantfile Switch Vagrant to Bionic 2018-07-24 12:11:24 +00:00
VERSION mvebu64: update dev to 5.2.y, rockchip64-default: attach to new tag + upstream patch, bump with version due to htop and sunxi kernels update 2019-08-02 23:12:38 +02:00

README.md

Armbian

Debian based Linux for ARM based single-board computers

https://www.armbian.com

How to build an image or a kernel?

Supported build environment is Ubuntu Bionic 18.04 x64 (minimal iso image).

  • guest inside a VirtualBox or other virtualization software,
  • guest managed by Vagrant. This uses Virtualbox (as above) but does so in an easily repeatable way,
  • inside a Docker, systemd-nspawn or other container environment (example),
  • running natively on a dedicated PC or a server (not recommended),
  • 25GB disk space or more and 2GB RAM or more available for the VM, container or native OS,
  • superuser rights (configured sudo or root access).

Execution

apt-get -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh

Make sure that full path to the build script does not contain spaces.

You will be prompted with a selection menu for a build option, a board name, a kernel branch and an OS release. Please check the documentation for advanced options and additional customization.

Build process uses caching for the compilation and the debootstrap process, so consecutive runs with similar settings will be much faster.

How to report issues?

Please read this notice first before opening an issue.

How to contribute?

  • Fork the project
  • Make one or more well commented and clean commits to the repository.
  • Perform a pull request in github's web interface.

If it is a new feature request, don't start the coding first. Remember to open an issue to discuss the new feature.

If you are struggling, check this detailed step by step guide on contributing.

Where to get more info?