| commit | 9e206396d08360bf8248e571d07337cd75ad8fe0 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Jan 19 21:20:46 2017 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Jan 19 21:20:49 2017 -0600 |
| tree | 36b8324d9e3c9b440ad372b5e10ebc5b4e90a013 | |
| parent | 48b42e0086847aa8b87b4102d7af315d91f3b45d [diff] |
phosphor-state-manager: remove daemon duplication
The phosphor-state-manager repository builds [at least] two executables:
* phosphor-host-state-manager
* phosphor-chassis-state-manager
phosphor-host-state-manager.bb and phosphor-chassis-state-manager.bb
were effectively the exact same file and had no assignment of
executables to files. The result was that both packages installed both
daemons and caused an installation collision.
Combine the two recipes into a single recipe with the correct package
relationship for each executable.
Change-Id: I76a1e598bebc5090ae374271bbd5e8e32967cb43
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
- meta-phosphor/common/recipes-phosphor/state/files/xyz.openbmc_project.State.Chassis.service[Renamed from meta-phosphor/common/recipes-phosphor/state/phosphor-chassis-state-manager/xyz.openbmc_project.State.Chassis.service - diff]
- meta-phosphor/common/recipes-phosphor/state/files/xyz.openbmc_project.State.Host.service[Renamed from meta-phosphor/common/recipes-phosphor/state/phosphor-host-state-manager/xyz.openbmc_project.State.Host.service - diff]
- meta-phosphor/common/recipes-phosphor/state/phosphor-chassis-state-manager.bb[Deleted - diff]
- meta-phosphor/common/recipes-phosphor/state/phosphor-host-state-manager.bb[Deleted - diff]
- meta-phosphor/common/recipes-phosphor/state/phosphor-state-manager.bb[Added - diff]
- meta-phosphor/conf/distro/include/phosphor-defaults.inc[diff]
6 files changed
tree: 36b8324d9e3c9b440ad372b5e10ebc5b4e90a013
- import-layers/
- meta-openbmc-bsp/
- meta-openbmc-machines/
- meta-phosphor/
- bitbake ⇨ import-layers/yocto-poky/bitbake
- documentation ⇨ import-layers/yocto-poky/documentation
- LICENSE ⇨ import-layers/yocto-poky/LICENSE
- meta ⇨ import-layers/yocto-poky/meta
- meta-poky ⇨ import-layers/yocto-poky/meta-poky
- meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
- meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
- meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
- oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
- oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
- scripts ⇨ import-layers/yocto-poky/scripts
- .gitignore
- .gitreview
- .templateconf
- openbmc-env
- README.md
README.md
OpenBMC
Building
OpenBMC uses Yocto/Open-Embedded for a build system, which supports an out-of-tree build. It is recommended that you create an empty directory somewhere to hold the build. This directory will get big.
On Ubuntu 14.04 the following packages are required to build the default target
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
On Fedora 23 the following packages are required to build the default target:
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake sudo dnf groupinstall "C Development Tools and Libraries"
To start a build:
cd <builddir> . <repodir>/openbmc-env bitbake obmc-phosphor-image