conf/layer.conf

# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}"

# We have recipes-* directories, add to BBFILES
BBFILES += " \
  ${LAYERDIR}/recipes-*/*/*.bb \
  ${LAYERDIR}/recipes-*/*/*.bbappend \
  "

BBFILES_DYNAMIC += " \
  fii-layer:${LAYERDIR}/dynamic-layers/fii-layer/recipes-*/*/*.bb \
  fii-layer:${LAYERDIR}/dynamic-layers/fii-layer/recipes-*/*/*.bbappend \
  nuvoton-layer:${LAYERDIR}/dynamic-layers/nuvoton-layer/recipes-*/*/*.bb \
  nuvoton-layer:${LAYERDIR}/dynamic-layers/nuvoton-layer/recipes-*/*/*.bbappend \
  aspeed-layer:${LAYERDIR}/dynamic-layers/aspeed-layer/recipes-*/*/*.bb \
  aspeed-layer:${LAYERDIR}/dynamic-layers/aspeed-layer/recipes-*/*/*.bbappend \
  "

BBFILE_COLLECTIONS += "gbmc-staging-layer"
BBFILE_PATTERN_gbmc-staging-layer := "^${LAYERDIR}/"
LAYERSERIES_COMPAT_gbmc-staging-layer = "langdale nanbield scarthgap"
LAYERDEPENDS_gbmc-staging-layer += "google-layer"

# Google has forked certain OpenBMC repositories.
# This override affects how certain recipe is built.
# You can turn off it by removing "gbmcfork" from OVERRIDES on your machine,
# or by removing "gbmcfork" from your DISTRO_FEATURES.
OVERRIDES:append = "${@bb.utils.contains('DISTRO_FEATURES', 'gbmcfork', ':gbmcfork', '', d)}"

# Adding multithread as a feature to opt into. Cannot just make it a
# PACKAGECONFIG change as there are patches that need to go with it as well
OVERRIDES:append = "${@bb.utils.contains('DISTRO_FEATURES', 'bmcweb_multithread', ':bmcweb_multithread', '', d)}"