All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: meta-toolchain-qt with Qt Creator
Date: Mon, 7 Oct 2013 15:12:45 +0300	[thread overview]
Message-ID: <20131007121245.GC9225@lpalcu-linux> (raw)
In-Reply-To: <CAMCfZKGX7Giu3DhcXTofSbSQF4voERZEvTQZyBZg4kSp2ewnfg@mail.gmail.com>

Hi Diego,

On Mon, Oct 07, 2013 at 08:18:00AM -0300, Diego Sueiro wrote:
> 2013/10/7 Laurentiu Palcu <laurentiu.palcu@intel.com>
> 
>     Hi Diego,
>     It's a little more complicated than that. After building the toolchain,
>     all binaries have the default absolute path to the dynamic loader
>     (/opt/poky/...) hardcoded in the elf INTERP section. This is easy to
>     change. However, other binaries may or may not have other hardcoded
>     paths to search for different things (like configs, etc.). Most of these
>     could be easily fixed by providing the binary with an option or setting
>     an environment variable to instruct it where to find what it needs. Take
>     for example the gcc --sysroot option. By default gcc will search for the
>     sysroot in the default location (starting with /opt/poky), but providing
>     a --sysroot option, we override this default path.
> 
>     So, even though, for relocation, changing the INTERP section may suffice
>     for most of the binaries, some may need more tweaking.
> 
>     A quick search on google brought me to this page:
>     http://qt-project.org/doc/qt-4.8/qmake-environment-reference.html
> 
>     It turns out that QMAKESPEC environment variable is what QT creator
>     looks at to be able to locate qmake.conf. So, perhaps, we need to add
>     this to the environment file and the problem should be fixed...
> 
>     Can you please test this?
> 
>     Thanks,
>     Laurentiu
> 
> 
> 
> Laurentiu,
> 
> Thanks for the explanation.
> 
> I took a look at environment-setup-armv7a-vfp-neon-poky-linux-gnueabi file and
> it is already exporting the QMAKESPEC variable to the right path.
Stupid me, I should've looked in the meta-toolchain-qt.inc first. Yes,
it appears to be set...

> Maybe this variable is overridden by another one or by Qt Creator based on some
> INTERP.
> 
> I did a "grep -r \/poky\/1\.4\.2 ./*" on the toolchain (installed outside
> default path) and this is the results:
> 
>     http://pastebin.com/us9p5vVp
> 
> 
> 
> Unfortunately I don't have enough knowledge to track this.
Would you please file a bug on this? I'll have a look as soon as I find
some time.

Thanks,
Laurentiu
> 
> 
> Regards,
> 
> --
> *dS
> Diego Sueiro
>  


      reply	other threads:[~2013-10-07 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 12:45 meta-toolchain-qt with Qt Creator Diego Sueiro
2013-10-04 14:18 ` Jose Mª Ferreiro
2013-10-04 14:30   ` Diego Sueiro
2013-10-04 14:36     ` Jose Mª Ferreiro
2013-10-04 18:32       ` Diego Sueiro
2013-10-04 20:26         ` Diego Sueiro
2013-10-07  7:05           ` Laurentiu Palcu
2013-10-07 11:18             ` Diego Sueiro
2013-10-07 12:12               ` Laurentiu Palcu [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=20131007121245.GC9225@lpalcu-linux \
    --to=laurentiu.palcu@intel.com \
    --cc=diego.sueiro@gmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.