Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFH] Wrong behaviour regarding SDK native and target paths
Date: Mon, 04 Jul 2011 14:46:37 +0100	[thread overview]
Message-ID: <1309787198.20015.669.camel@rex> (raw)
In-Reply-To: <CAP9ODKpeG=a71mZNRTRzt=Ehjy3iEBhBa0dPCA71vKnA-Cz30A@mail.gmail.com>

On Sun, 2011-07-03 at 19:29 -0300, Otavio Salvador wrote:
> Hello,
> 
> I am looking for help to get our nativesdk working fine and I am quite
> confused how does it can work after all.
> 
> I have looked at meta/recipes-qt/meta/meta-toolchain-qte.bb and it has:
> 
> QT_TOOLS_PREFIX = "${SDKPATHNATIVE}${bindir_nativesdk}"
> 
> Running it is expanded to:
> 
> QT_TOOLS_PREFIX="/usr/local/oecore-i686-i586/sysroots/i686-oesdk-linux/usr/bin"
> 
> It seems right but in fact it is wrong since Qt binaries are installed into:
> 
> (devel)~/hacking/el% tar tjf
> tmp-eglibc-eglibc/deploy/sdk/oecore-i686-i586-toolchain-devel.tar.bz2|
> grep 'bin/moc4'
> ./usr/local/oecore-i686-i686/sysroots/i686-oesdk-linux/usr/bin/moc4
> 
> so, the generated information for the script won't work.
> 
> I am quite confused by all this is suppose to work. Someone help me?

It looks like in OE-Core we have:

conf/bitbake.conf:SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
conf/bitbake.conf:SDKPATH = "/usr/local/${SDK_NAME}"
conf/bitbake.conf:SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"

and in meta-yocto:

conf/distro/poky.conf:SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"

I suspect having TARGET_ARCH in the PATH might be a bad idea and we need
to rethink the defaults in OE-Core. Using something more like the
meta-yocto default above might help your problem.

Cheers,

Richard




      reply	other threads:[~2011-07-04 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 22:29 [RFH] Wrong behaviour regarding SDK native and target paths Otavio Salvador
2011-07-04 13:46 ` Richard Purdie [this message]

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=1309787198.20015.669.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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