[PATCHv2 0/5] Pending patches

[PATCHv2 0/5] Pending patches

[Martin Jansa]

Patch 0003 depends on
http://patchwork.openembedded.org/patch/22047/

0001 wasn't changed from v1, but still does apply.

0004/0005 is the same as I've sent as single patches to ML before.

The following changes since commit c44e51f281101c8933679f679e3d4a75a41bedf7:

  initscripts: mount and unmount cifs network filesystems (2012-02-24 23:25:33 +0000)

are available in the git repository at:
  git://git.openembedded.org/openembedded-core-contrib jansa/pull
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/pull

Eric BENARD (1):
  gdb-cross-canadian: build gdb with python support

Martin Jansa (4):
  bitbake.conf: use weak assignment for BB_CONSOLELOG
  bitbake.conf: remove TARGET_ARCH from in SDKPATH
  sstatesig: add SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS option to exclude well
    defined recipe->dependency
  layer.conf: add keymaps to SIGGEN_EXCLUDERECIPES_ABISAFE

 meta/conf/bitbake.conf                             |   12 +++++++++---
 meta/conf/layer.conf                               |    1 +
 meta/lib/oe/sstatesig.py                           |    6 ++++++
 meta/recipes-devtools/gdb/gdb-cross-canadian.inc   |   20 +++++++++++++++++++-
 .../recipes-devtools/gdb/gdb-cross-canadian_7.4.bb |    2 +-
 5 files changed, 36 insertions(+), 5 deletions(-)

-- 
1.7.8.4

[PATCHv2 1/5] bitbake.conf: use weak assignment for BB_CONSOLELOG

[Martin Jansa]

* some people prefer subdirectory like ${TMPDIR}/cooker/${DATETIME}.log

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

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 2539ae0..55daa9e 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -726,7 +726,8 @@ DISTRO[unexport] = "1"
 # Used by canadian-cross to handle string conversions on TARGET_ARCH where needed
 TRANSLATED_TARGET_ARCH ??= "${@d.getVar('TARGET_ARCH', True).replace("_", "-")}"
 
-BB_CONSOLELOG = "${TMPDIR}/cooker.log.${DATETIME}"
+# Complete output from bitbake, if you're changing it, make sure to use existing directory
+BB_CONSOLELOG ?= "${TMPDIR}/cooker.log.${DATETIME}"
 
 # Setup our default hash policy
 BB_SIGNATURE_HANDLER ?= "OEBasic"
-- 
1.7.8.4

[PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH

[Martin Jansa]

* SDKPATH shouldn't depend on TARGET_ARCH as discused here:
  http://lists.linuxtogo.org/pipermail/openembedded-core/2012-February/018222.html
* introduce SDK_NAME_PREFIX so that distributions can overwrite only
  this instead of whole SDK_NAME

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

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 55daa9e..f2666cb 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -360,8 +360,13 @@ DEPLOY_DIR_TOOLS = "${DEPLOY_DIR}/tools"
 
 PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
 
-SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"
-SDKPATH = "/usr/local/${SDK_NAME}"
+##################################################################
+# SDK variables, 
+##################################################################
+
+SDK_NAME_PREFIX = "oecore"
+SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_ARCH}-${TARGET_ARCH}"
+SDKPATH = "/usr/local/${SDK_NAME_PREFIX}-${SDK_ARCH}"
 SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
 
 ##################################################################
-- 
1.7.8.4

[PATCHv2 3/5] gdb-cross-canadian: build gdb with python support

[Martin Jansa]

From: Eric BENARD <eric@eukrea.com>

* python support is needed for providing finer scripting control
in gdb, and for remote controling gdb for example from qtcreator
* gdb/configure tries to autodetect python using python executable
with --includes --ldflags --exec-prefix to get the right flags
As it's difficult to achieve in OE's context, we generate a
script which will return the right values and make gdb's build
system happy. This idea was taken from the following article :
http://www.mentby.com/doug-evans-2/python-enabled-gdb-on-windows-and-relocation.html
* tested using angstrom & armv7 target & qtcreator 201005 & 2.4.0

* MJ: updated paths to python as disscussed here
  http://lists.linuxtogo.org/pipermail/openembedded-core/2012-February/018222.html
  now it's easier with cross-canadian staging dir and SDKPATH fixed :)

Signed-off-by: Eric Bénard <eric@eukrea.com>
Cc: fcooper@ti.com
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/recipes-devtools/gdb/gdb-cross-canadian.inc   |   20 +++++++++++++++++++-
 .../recipes-devtools/gdb/gdb-cross-canadian_7.4.bb |    2 +-
 2 files changed, 20 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
index ec0748e..a7cac61 100644
--- a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
+++ b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
@@ -4,4 +4,22 @@ DESCRIPTION = "cross-canadian gdb for ${TARGET_ARCH} target - GNU debugger"
 PN = "gdb-cross-canadian-${TRANSLATED_TARGET_ARCH}"
 BPN = "gdb"
 
-DEPENDS = "ncurses-nativesdk expat-nativesdk gettext-nativesdk readline-nativesdk"
+DEPENDS = "ncurses-nativesdk expat-nativesdk gettext-nativesdk readline-nativesdk python-nativesdk"
+RDEPENDS += "python-nativesdk-core python-nativesdk-lang python-nativesdk-re \
+             python-nativesdk-codecs python-nativesdk-netclient"
+
+EXTRA_OECONF_append = "--with-python=${WORKDIR}/python"
+
+do_configure_prepend() {
+cat > ${WORKDIR}/python << EOF
+#! /bin/sh
+case "\$2" in
+        --includes) echo "-I${STAGING_INCDIR}/python${PYTHON_BASEVERSION}/" ;;
+        --ldflags) echo "-L${STAGING_LIBDIR}/../python${PYTHON_BASEVERSION}/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
+        --exec-prefix) echo "/usr" ;;
+        *) exit 1 ;;
+esac
+exit 0
+EOF
+        chmod +x ${WORKDIR}/python
+}
diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian_7.4.bb b/meta/recipes-devtools/gdb/gdb-cross-canadian_7.4.bb
index a4714e7..dbcffde 100644
--- a/meta/recipes-devtools/gdb/gdb-cross-canadian_7.4.bb
+++ b/meta/recipes-devtools/gdb/gdb-cross-canadian_7.4.bb
@@ -1,7 +1,7 @@
 require gdb-common.inc
 require gdb-cross-canadian.inc
 
-PR = "${INC_PR}.1"
+PR = "${INC_PR}.3"
 
 GDBPROPREFIX = "--program-prefix='${TARGET_PREFIX}'"
 EXPAT = "--with-expat"
-- 
1.7.8.4

[PATCHv2 4/5] sstatesig: add SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS option to exclude well defined recipe->dependency

[Martin Jansa]

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/lib/oe/sstatesig.py |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index 7b80c18..1c25823 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -33,6 +33,10 @@ def sstate_rundepfilter(siggen, fn, recipename, task, dep, depname, dataCache):
     if depname in siggen.abisaferecipes:
         return False
 
+    # Exclude well defined recipe->dependency
+    if "%s->%s" % (recipename, depname) in siggen.saferecipedeps:
+        return False
+
     # Kernel modules are well namespaced. We don't want to depend on the kernel's checksum
     # if we're just doing an RRECOMMENDS_xxx = "kernel-module-*", not least because the checksum
     # is machine specific.
@@ -51,6 +55,7 @@ class SignatureGeneratorOEBasic(bb.siggen.SignatureGeneratorBasic):
     name = "OEBasic"
     def init_rundepcheck(self, data):
         self.abisaferecipes = (data.getVar("SIGGEN_EXCLUDERECIPES_ABISAFE", True) or "").split()
+        self.saferecipedeps = (data.getVar("SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS", True) or "").split()
         pass
     def rundep_check(self, fn, recipename, task, dep, depname, dataCache = None):
         return sstate_rundepfilter(self, fn, recipename, task, dep, depname, dataCache)
@@ -59,6 +64,7 @@ class SignatureGeneratorOEBasicHash(bb.siggen.SignatureGeneratorBasicHash):
     name = "OEBasicHash"
     def init_rundepcheck(self, data):
         self.abisaferecipes = (data.getVar("SIGGEN_EXCLUDERECIPES_ABISAFE", True) or "").split()
+        self.saferecipedeps = (data.getVar("SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS", True) or "").split()
         pass
     def rundep_check(self, fn, recipename, task, dep, depname, dataCache = None):
         return sstate_rundepfilter(self, fn, recipename, task, dep, depname, dataCache)
-- 
1.7.8.4

[PATCHv2 5/5] layer.conf: add keymaps to SIGGEN_EXCLUDERECIPES_ABISAFE

[Martin Jansa]

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

diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index dac9c97..93c087a 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -27,4 +27,5 @@ SIGGEN_EXCLUDERECIPES_ABISAFE += " \
   xserver-xf86-config \
   pointercal \
   base-files \
+  keymaps \
 "
-- 
1.7.8.4

Re: [PATCHv2 0/5] Pending patches

[Richard Purdie]

On Sun, 2012-02-26 at 08:48 +0100, Martin Jansa wrote:
> Patch 0003 depends on
> http://patchwork.openembedded.org/patch/22047/
> 
> 0001 wasn't changed from v1, but still does apply.
> 
> 0004/0005 is the same as I've sent as single patches to ML before.
> 
> The following changes since commit c44e51f281101c8933679f679e3d4a75a41bedf7:
> 
>   initscripts: mount and unmount cifs network filesystems (2012-02-24 23:25:33 +0000)
> 
> are available in the git repository at:
>   git://git.openembedded.org/openembedded-core-contrib jansa/pull
>   http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/pull
> 
> Eric BENARD (1):
>   gdb-cross-canadian: build gdb with python support
> 
> Martin Jansa (4):
>   bitbake.conf: use weak assignment for BB_CONSOLELOG
>   bitbake.conf: remove TARGET_ARCH from in SDKPATH
>   sstatesig: add SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS option to exclude well
>     defined recipe->dependency
>   layer.conf: add keymaps to SIGGEN_EXCLUDERECIPES_ABISAFE

Merged to master, thanks.

Richard

Re: [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH

[Khem Raj]

On 02/25/2012 11:49 PM, Martin Jansa wrote:
> +SDK_NAME_PREFIX = "oecore"

should this be weak assignment

Re: [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 491 bytes --]

On Thu, Mar 01, 2012 at 01:23:29AM -0800, Khem Raj wrote:
> On 02/25/2012 11:49 PM, Martin Jansa wrote:
> > +SDK_NAME_PREFIX = "oecore"
> 
> should this be weak assignment

Yeah, probably could be (I'm not overwritting this from my distro conf
so I haven't tried), but SDK_NAME assignment also wasn't weak and distros
were overwritting it.

Someone with custom SDK_NAME(_PREFIX) please try and send patch.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

On Thu, Mar 01, 2012 at 10:40:52AM +0100, Martin Jansa wrote:
> On Thu, Mar 01, 2012 at 01:23:29AM -0800, Khem Raj wrote:
> > On 02/25/2012 11:49 PM, Martin Jansa wrote:
> > > +SDK_NAME_PREFIX = "oecore"
> > 
> > should this be weak assignment
> 
> Yeah, probably could be (I'm not overwritting this from my distro conf
> so I haven't tried), but SDK_NAME assignment also wasn't weak and distros
> were overwritting it.
> 
> Someone with custom SDK_NAME(_PREFIX) please try and send patch.

And we should change TARGET_ARCH in SDK_NAME to
PACKAGE_ARCH or TUNE_PKGARCH

because meta-toolchain-gmae for armv7a ends in
oecore-i686-arm-toolchain-gmae-20120229.tar.bz2
and for armv4t with similar name (I was lucky that it took more then day to
build)
oecore-i686-arm-toolchain-gmae-20120301.tar.bz2

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH

[Richard Purdie]

On Thu, 2012-03-01 at 19:25 +0100, Martin Jansa wrote:
> On Thu, Mar 01, 2012 at 10:40:52AM +0100, Martin Jansa wrote:
> > On Thu, Mar 01, 2012 at 01:23:29AM -0800, Khem Raj wrote:
> > > On 02/25/2012 11:49 PM, Martin Jansa wrote:
> > > > +SDK_NAME_PREFIX = "oecore"
> > > 
> > > should this be weak assignment
> > 
> > Yeah, probably could be (I'm not overwritting this from my distro conf
> > so I haven't tried), but SDK_NAME assignment also wasn't weak and distros
> > were overwritting it.
> > 
> > Someone with custom SDK_NAME(_PREFIX) please try and send patch.
> 
> And we should change TARGET_ARCH in SDK_NAME to
> PACKAGE_ARCH or TUNE_PKGARCH
> 
> because meta-toolchain-gmae for armv7a ends in
> oecore-i686-arm-toolchain-gmae-20120229.tar.bz2
> and for armv4t with similar name (I was lucky that it took more then day to
> build)
> oecore-i686-arm-toolchain-gmae-20120301.tar.bz2

Agreed...

Cheers,

Richard

[PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME

[Martin Jansa]

* 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

Re: [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME

[McClintock Matthew-B29882]

On Fri, Mar 9, 2012 at 12:48 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> * 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}"

Why PACKAGE_ARCH over TUNE_ARCH?

-M

Re: [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME

[McClintock Matthew-B29882]

On Fri, Mar 9, 2012 at 10:32 AM, Matthew McClintock <msm@freescale.com> wrote:
> On Fri, Mar 9, 2012 at 12:48 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> * 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}"
>
> Why PACKAGE_ARCH over TUNE_ARCH?

Or rather TUNE_PKGARCH?

-M

Re: [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

On Fri, Mar 09, 2012 at 04:33:33PM +0000, McClintock Matthew-B29882 wrote:
> On Fri, Mar 9, 2012 at 10:32 AM, Matthew McClintock <msm@freescale.com> wrote:
> > On Fri, Mar 9, 2012 at 12:48 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> * 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}"
> >
> > Why PACKAGE_ARCH over TUNE_ARCH?
> 
> Or rather TUNE_PKGARCH?

In 
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-March/018543.html
I've said:

"And we should change TARGET_ARCH in SDK_NAME to PACKAGE_ARCH or TUNE_PKGARCH"

So why TUNE_ARCH/TUNE_PKGARCH over PACKAGE_ARCH?

I don't see the advantage, but if there is some I'll update it in v2.

Cheers,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME

[McClintock Matthew-B29882]

On Fri, Mar 9, 2012 at 11:00 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> On Fri, Mar 09, 2012 at 04:33:33PM +0000, McClintock Matthew-B29882 wrote:
>> On Fri, Mar 9, 2012 at 10:32 AM, Matthew McClintock <msm@freescale.com> wrote:
>> > On Fri, Mar 9, 2012 at 12:48 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> >> * 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}"
>> >
>> > Why PACKAGE_ARCH over TUNE_ARCH?
>>
>> Or rather TUNE_PKGARCH?
>
> In
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-March/018543.html
> I've said:
>
> "And we should change TARGET_ARCH in SDK_NAME to PACKAGE_ARCH or TUNE_PKGARCH"
>
> So why TUNE_ARCH/TUNE_PKGARCH over PACKAGE_ARCH?
>
> I don't see the advantage, but if there is some I'll update it in v2.

Well for powerpc (PACKAGE_ARCH) we have ppce500mc, ppce500v2, and
ppce5500 (TUNEPKG_ARCH) and for powerpc64 we have ppc64e5500. This is
what I would want my toolchain to convey - not sure what the best
generic solution is.

-M

[PATCHv2] bitbake.conf: use TUNE_PKGARCH instead of TARGET_ARCH in SDK_NAME

[Martin Jansa]

* also use weak assignment for SDK_NAME_PREFIX as suggested by khem
* TUNE_PKGARCH 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/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 216da75..01fc52a 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -365,8 +365,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}-${TUNE_PKGARCH}"
 SDKPATH = "/usr/local/${SDK_NAME_PREFIX}-${SDK_ARCH}"
 SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
 
-- 
1.7.8.5

Re: [PATCHv2] bitbake.conf: use TUNE_PKGARCH instead of TARGET_ARCH in SDK_NAME

[Saul Wold]

On 03/15/2012 12:23 AM, Martin Jansa wrote:
> * also use weak assignment for SDK_NAME_PREFIX as suggested by khem
> * TUNE_PKGARCH 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/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 216da75..01fc52a 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -365,8 +365,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}-${TUNE_PKGARCH}"
>   SDKPATH = "/usr/local/${SDK_NAME_PREFIX}-${SDK_ARCH}"
>   SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
>

Merged into OE-Core

Thanks
	Sau!