diff options
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2016-08-12 16:11:00 -0400 |
---|---|---|
committer | Patrick Williams <patrick@stwcx.xyz> | 2016-08-18 17:03:41 +0000 |
commit | f5e6dbae7b1f94a01bad5691fca6c5a78119fd44 (patch) | |
tree | bca01b36a08a21cafe0b2ec3d2912bd002e8501d /meta-phosphor/common/recipes-phosphor/obmc-phosphor-user | |
parent | 2535f194917126ed3d3233940f03489d3d4ab0be (diff) | |
download | talos-openbmc-f5e6dbae7b1f94a01bad5691fca6c5a78119fd44.tar.gz talos-openbmc-f5e6dbae7b1f94a01bad5691fca6c5a78119fd44.zip |
Remove native/sdk classes from recipes
There isn't any reason to be baking pflash or libobmc_intf
recipes for sdk or build machines (x86).
This was mistakenly added (by me) based on misunderstanding
of how to get dev packages into the target sysroot.
The correct way to do this is to just have a dev package
whose main package is in IMAGE_INSTALL or has a dependency on
another dev package (whose main package is in IMAGE_INSTALL).
I'm not adding those dependencies now here because at the moment
pflash-dev is unused and libobmc_intf will eventually disappear.
Change-Id: I691cd029a69ad7554faeb4782ae97b92946c9a7b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-phosphor/common/recipes-phosphor/obmc-phosphor-user')
0 files changed, 0 insertions, 0 deletions