summaryrefslogtreecommitdiff
path: root/meta/recipes-connectivity/bluez/bluez4-4.82
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-07-22 14:15:20 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-07-22 15:38:40 +0100
commita10de4cf8b424ee95c8e283e75d486be5b3b8eac (patch)
tree59624b04951790878279ea151bc77844fd9d986c /meta/recipes-connectivity/bluez/bluez4-4.82
parentaeea22da699b276a97ca1a17e3c53176c9afd9de (diff)
downloadopenembedded-core-a10de4cf8b424ee95c8e283e75d486be5b3b8eac.tar.gz
openembedded-core-a10de4cf8b424ee95c8e283e75d486be5b3b8eac.tar.bz2
openembedded-core-a10de4cf8b424ee95c8e283e75d486be5b3b8eac.tar.xz
openembedded-core-a10de4cf8b424ee95c8e283e75d486be5b3b8eac.zip
conf/machine/tune: Overhaul tune include file variables
There is currently consideradble confusion over how the tune files operate and how these interact with the rest of the build system. This update/overhaul changes things so the tune files are primarily resonsible for setting: TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that represents the architecture we're targetting. TUNE_PKGARCH - The value that represents the tune confuration that this set of tune parameters results in. This allows the significant improvement that the core can now always determine the target architecture value, even when TARGET_ARCH needs to be reset to something different and likewise, there is one package architecture variable the core can reference allowing simplification of the BASE_PACKAGE_ARCH, PACKAGE_ARCH and FEED_ARCH variables. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity/bluez/bluez4-4.82')
0 files changed, 0 insertions, 0 deletions