commit | 91a200befb4f10753483bcd831cbc81aa5955e24 | [log] [tgz] |
---|---|---|
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | Thu Aug 22 14:24:33 2019 -0400 |
committer | Joel Stanley <joel@jms.id.au> | Wed Sep 04 07:23:06 2019 +0000 |
tree | ea95f569c5cbc0c34179fc47ff63ecd7221d62e3 | |
parent | b925511c1e7213ebc851e1ee01abfa15cf3fd2b8 [diff] |
build-setup: explicitly set MACHINE and DISTRO An OE based build system typically has three inputs from the user; the machine target (MACHINE), the distro policy (DISTRO), and the package content (aka image/recipe being baked). Using TEMPLATECONF to generate local.conf attempts to map the machine target and distro policy down to a single input but is an abuse of TEMPLATECONF and places constraints on use of conventional OE metadata structure paradigms. For example a layer can only provide a single local.conf.sample but can support multiple machine targets and distro policy sets. Formalize a "target" for the build-setup script to be the desired MACHINE+DISTRO combination. Explicitly declere the desired combination for each target. This allows layer authors full flexibility when organizing their metadata. Change-Id: Ia6a335135966b82120513c75d1617bf70b811a2e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Build script for CI jobs in Jenkins.