Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME
Date: Fri,  9 Mar 2012 07:48:26 +0100	[thread overview]
Message-ID: <1331275706-6917-1-git-send-email-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <20120301094052.GB3831@jama.jama.net>

* also use weak assignment for SDK_NAME_PREFIX as suggested by khem
* PACKAGE_ARCH is not 100% right too, because such SDK image usually has few
  machine specific packages included (e.g. base-files, securetty, opkg configs)
  but those are not important for SDK users so it's better to have one SDK for
  whole e.g. armv7a-vfp-neon then 6 SDK for each machine which would work the
  same.
  You can see diff between crespo and om-gta04 SDK here:
  http://build.shr-project.org/shr-core-staging/031/sdk/oecore-i686-armv7a-vfp-neon-toolchain-efl-crespo-om-gta04.diff

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/conf/bitbake.conf |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 87bb71c..91f8397 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -364,8 +364,8 @@ PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
 # SDK variables, 
 ##################################################################
 
-SDK_NAME_PREFIX = "oecore"
-SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_ARCH}-${TARGET_ARCH}"
+SDK_NAME_PREFIX ?= "oecore"
+SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_ARCH}-${PACKAGE_ARCH}"
 SDKPATH = "/usr/local/${SDK_NAME_PREFIX}-${SDK_ARCH}"
 SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
 
-- 
1.7.8.5




  parent reply	other threads:[~2012-03-09  6:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26  7:48 [PATCHv2 0/5] Pending patches Martin Jansa
2012-02-26  7:49 ` [PATCHv2 1/5] bitbake.conf: use weak assignment for BB_CONSOLELOG Martin Jansa
2012-02-26  7:49 ` [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH Martin Jansa
2012-03-01  9:23   ` Khem Raj
2012-03-01  9:40     ` Martin Jansa
2012-03-01 18:25       ` Martin Jansa
2012-03-01 19:59         ` Richard Purdie
2012-03-09  6:48       ` Martin Jansa [this message]
2012-03-09 16:32         ` [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME McClintock Matthew-B29882
2012-03-09 16:33           ` McClintock Matthew-B29882
2012-03-09 17:00             ` Martin Jansa
2012-03-09 17:06               ` McClintock Matthew-B29882
2012-03-15  7:23                 ` [PATCHv2] bitbake.conf: use TUNE_PKGARCH " Martin Jansa
2012-04-27 20:49                   ` Saul Wold
2012-02-26  7:49 ` [PATCHv2 3/5] gdb-cross-canadian: build gdb with python support Martin Jansa
2012-02-26  7:49 ` [PATCHv2 4/5] sstatesig: add SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS option to exclude well defined recipe->dependency Martin Jansa
2012-02-26  7:49 ` [PATCHv2 5/5] layer.conf: add keymaps to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa
2012-02-26 11:01 ` [PATCHv2 0/5] Pending patches Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1331275706-6917-1-git-send-email-Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox