meta-phosphor: temp remove PV for git recipes

In the five step sequence of transitioning an unversioned recipe to
a versioned one, PV cannot be explicitly set to 1.0+git${SRCPV} set
until the last step.

With PV set, _both_ the unversioned recipe and the versioned recipe
end up with PV = 1.0 and bitbake will continue to use the unversioned
file.  This means that when the unversioned bbappends are removed in
step 4, the bbappend does not occur.

This commit can be reverted once the five step process is complete.

For reference, the five step process is:

1.
Create a temporary recipe symlink:
foo.bb -> foo_git.bb

This results in two available PVs for foo: "1.0" (the bitbake default
for unversioned recipes) and "git".

Further, set the preferred version for foo to "1.0" in the distro
configuration otherwise bitbake will choose PV = "git" and existing
(unversioned) bbappends will not apply and the build will break.

2.
Create a temporary bbappend symlink:
foo.bbappend -> foo_%.bbappend

This allows the manual override of the preferred version introduced in
step 1 to be removed from the distro configuration.

3.
Remove the preferred version override introduced in step 1 from the
distro configuration.  At this point the versioned recipe is now being
used.

4.
Remove the unversioned bbappends.

5.
Remove the unversioned recipe.

(From meta-phosphor rev: 883e0238adc8543b28cce8a5d283d2092026da54)

Change-Id: I3c5248a41b064462d5a34a7bc6e5438acc107a32
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
9 files changed
tree: 812e4c2b8255fc33bda47afcf0b3a3f5740013dd
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-facebook/
  5. meta-google/
  6. meta-ibm/
  7. meta-ingrasys/
  8. meta-intel/
  9. meta-inventec/
  10. meta-mellanox/
  11. meta-nuvoton/
  12. meta-openembedded/
  13. meta-openpower/
  14. meta-phosphor/
  15. meta-portwell/
  16. meta-qualcomm/
  17. meta-quanta/
  18. meta-raspberrypi/
  19. meta-security/
  20. meta-x86/
  21. meta-xilinx/
  22. poky/
  23. .gitignore
  24. .gitreview
  25. .templateconf
  26. MAINTAINERS
  27. openbmc-env
  28. README.md
  29. setup
README.md

OpenBMC

Build Status

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.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 28
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake rpcgen
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

Build Validation and Testing

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.

Submitting Patches

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.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Features of OpenBMC

Feature List

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact