[OE-core] [oe-core][PATCH 2/4] gdb-cross-canadian: use NATIVESDK paths as it happens to be here

[Martin Jansa]

On Fri, Feb 17, 2012 at 02:36:48PM -0800, Saul Wold wrote:
> On 02/13/2012 07:40 AM, Martin Jansa wrote:
> > * seems like config/config in -L was also wrong
> >
> > Signed-off-by: Martin Jansa<Martin.Jansa at gmail.com>
> > ---
> >   meta/recipes-devtools/gdb/gdb-cross-canadian.inc |   10 ++++++++--
> >   1 files changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
> > index b5746ce..bac63b7 100644
> > --- a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
> > +++ b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
> > @@ -10,12 +10,18 @@ RDEPENDS += "python-nativesdk-core python-nativesdk-lang python-nativesdk-re \
> >
> >   EXTRA_OECONF_append = "--with-python=${WORKDIR}/python"
> >
> > +NATIVESDK_NAME = "oecore-${SDK_ARCH}-${SDK_ARCH}"
> > +NATIVESDK_PATH = "/usr/local/${NATIVESDK_NAME}"

Ah, I was reusing definition from bitbake.conf:
meta/conf/bitbake.conf:SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"

with only TARGET_ARCH replaced with SDK_ARCH.

Can we move "oecore" to extra varible like:

bitbake.conf:
-SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"
+SDK_NAME_PREFIX = "oecore"
+SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_ARCH}-${TARGET_ARCH}"

meta-yocto/conf/distro/poky.conf:
-SDK_NAME = "${DISTRO}-${TCLIBC}-${SDK_ARCH}-${TARGET_ARCH}"
+SDK_NAME_PREFIX = "${DISTRO}-${TCLIBC}"

SDK_PATH is worse:
meta/conf/bitbake.conf:SDKPATH = "/usr/local/${SDK_NAME}"
meta-yocto/conf/distro/poky.conf:SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"

Maybe this patch is not going in right direction, but nobody replied in
"SDK confusion Was: [oe] [meta-oe] gdb-cross-canadian: build gdb with python support"
thread so I have sent this version which works in default (distroless)
oe-core (and also for SHR as we don't override default SDK* variables.

If this variables make sense globally, then we can move them to
bitbake.conf and pokyt.conf (and maybe Angstrom too) can overwrite them
like they do with other SDK*.

Cheers,


> Martin,
> 
> These two lines will not work in the general case, since the NATIVESDK 
> might be for a different distro (not oecore) or in a different directory 
> such as /opt vs /usr/local.
> 
> The Poky build fails with this patch for example.
> 
> Sau!
> 
> > +NATIVESDK_PATHNATIVE = "${NATIVESDK_PATH}/sysroots/${SDK_SYS}"
> > +NATIVESDK_LIBDIR = "${NATIVESDK_PATHNATIVE}${libdir_nativesdk}"
> > +NATIVESDK_INCLUDEDIR = "${NATIVESDK_PATHNATIVE}${includedir_nativesdk}"
> > +
> 
> >   do_configure_prepend() {
> >   cat>  ${WORKDIR}/python<<  EOF
> >   #! /bin/sh
> >   case "\$2" in
> > -        --includes) echo "-I${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${exec_prefix}/include/python${PYTHON_BASEVERSION}/" ;;
> > -        --ldflags) echo "-L${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${libdir}/python${PYTHON_BASEVERSION}/config/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
> > +        --includes) echo "-I${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${NATIVESDK_INCLUDEDIR}/python${PYTHON_BASEVERSION}/" ;;
> > +        --ldflags) echo "-L${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${NATIVESDK_LIBDIR}/python${PYTHON_BASEVERSION}/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
> >           --exec-prefix) echo "/usr" ;;
> >           *) exit 1 ;;
> >   esac

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120218/25fa2043/attachment-0002.sig>