| commit | 5a6c125093f06502865681cd5990655eb97a6e41 | [log] [tgz] |
|---|---|---|
| author | Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com> | Sat Apr 25 14:40:13 2020 -0300 |
| committer | Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com> | Wed Apr 29 14:01:53 2020 -0300 |
| tree | 1fefc07990da5f0e0108781c185e960742df482b | |
| parent | b0cfd8e6578763bd1cc254730b7d3453174acc65 [diff] |
ci: Rework SDK build steps Significantly rework how we're doing the SDK step for our CI scripts: * Reduce the number of packages to speed up SDK build step. The only reusable piece of an SDK is the toolchain and it's own dependent pieces (i.e., sysroot dir), so don't waste time by building packages that will be rebuilt when the SDK is used. * Instead of always building the SDK based on witherspoon_defconfig, take into account the platform for which the SDK is being built for, but try to canonize it and consider it's primary characteristics to make it unique, such as buildroot version, architecture, OS, Kernel Headers and GCC version used. Without this, at the time of this commit, the complete zz_defconfig build is using GCC 7.4.0, the sdk build is using GCC 6.5.0 from witherspoon_defconfig - an inconsistency in the result from a complete versus an sdk-based build. Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
The OpenPOWER firmware build process uses Buildroot to create a toolchain and build the various components of the PNOR firmware, including Hostboot, Skiboot, OCC, Petitboot etc.
https://open-power.github.io/op-build/
See the doc/ directory for documentation source. Contributions are VERY welcome!
Issues, Milestones, pull requests and code hosting is on GitHub: https://github.com/open-power/op-build
See CONTRIBUTING.md for howto contribute code.
To build an image for a Palmetto system:
git clone --recursive git@github.com:open-power/op-build.git cd op-build ./op-build palmetto_defconfig && ./op-build
There are also default configurations for other platforms in openpower/configs/. Current POWER8 platforms include Habanero, Firestone, and Garrison. Current POWER9 platforms include Witherspoon, Boston (p9dsu), Romulus, and Zaius.
Buildroot/op-build supports both native and cross-compilation - it will automatically download and build an appropriate toolchain as part of the build process, so you don't need to worry about setting up a cross-compiler. Cross-compiling from a x86-64 host is officially supported.
The machine your building on will need Python 2.7, GCC 6.2 (or later), and a handful of other packages (see below).
Install Ubuntu (>= 18.04) or Debian (>= 9) 64-bit.
Enable Universe (Ubuntu only):
sudo apt-get install software-properties-common sudo add-apt-repository universe
Install the packages necessary for the build:
sudo apt-get install cscope ctags libz-dev libexpat-dev \ python language-pack-en texinfo gawk cpio xxd \ build-essential g++ git bison flex unzip \ libssl-dev libxml-simple-perl libxml-sax-perl libxml-parser-perl libxml2-dev libxml2-utils xsltproc \ wget bc rsync
Install Fedora (>= 25) 64-bit.
Install the packages necessary for the build:
sudo dnf install gcc-c++ flex bison git ctags cscope expat-devel patch \ zlib-devel zlib-static texinfo "perl(bigint)" "perl(XML::Simple)" \ "perl(YAML)" "perl(XML::SAX)" "perl(Fatal)" "perl(Thread::Queue)" \ "perl(Env)" "perl(XML::LibXML)" "perl(Digest::SHA1)" "perl(ExtUtils::MakeMaker)" \ libxml2-devel which wget unzip tar cpio python bzip2 bc findutils ncurses-devel \ openssl-devel make libxslt vim-common lzo-devel python2 rsync hostname