commit | 74c48cb2504bf76bd162a28aa8e7688a3d4a8f28 | [log] [tgz] |
---|---|---|
author | Ed Tanous <ed.tanous@intel.com> | Thu Apr 04 16:29:04 2019 -0700 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Mon Apr 15 23:00:48 2019 -0400 |
tree | 1a9f7073104cb0cecb5d722835ab805961b72c69 | |
parent | 5818b24d410f82b75c1a3bfc46818bdd42de5273 [diff] |
meta-phosphor: Don't build debug tarball implicitly In previous builds, the debug tarball was built as part of the obmc-phosphor-image implicitly. This increases the build times by a trivial amount, which matters, but is not that important. It also makes debugging image dependencies (using bitbake -g) a bear, given that it includes all dependencies for the debug tarball, as well as the actual image. Given that it's pretty trivial to build this manually via bitbake obmc-debug-tarball and (at least in my opinion) injecting the task seems like a bit of a violation of the yocto intracacies, and gives a surprising result to the user, this patchset removes the task add, and makes obmc-phosphor-debug-tarball a truly separate build target. (From meta-phosphor rev: 5c848ab3436bd0ed1062c4657f35a6a6890992ad) Signed-off-by: Ed Tanous <ed.tanous@intel.com> Change-Id: Ie2294f8e324249a44ef73aa10d57f332e8f54168 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake rpcgen sudo dnf groupinstall "C Development Tools and Libraries"
git clone git@github.com:openbmc/openbmc.git cd openbmc
Any build requires an environment variable known as TEMPLATECONF
to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample
. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
Machine | TEMPLATECONF |
---|---|
Palmetto | meta-ibm/meta-palmetto/conf |
Zaius | meta-ingrasys/meta-zaius/conf |
Witherspoon | meta-ibm/meta-witherspoon/conf |
Romulus | meta-ibm/meta-romulus/conf |
As an example target Palmetto
export TEMPLATECONF=meta-ibm/meta-palmetto/conf
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check
directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
Feature List
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.