All of lore.kernel.org
 help / color / mirror / Atom feed
* qt5 qmake
@ 2013-09-18 20:44 Trevor Woerner
  2013-09-18 21:29 ` Martin Jansa
  0 siblings, 1 reply; 3+ messages in thread
From: Trevor Woerner @ 2013-09-18 20:44 UTC (permalink / raw)
  To: openembedded-devel

If I want to run the devshell on a qt5 recipe from meta-qt5, I can't
help notice that if I do:

    $ which qmake

I get

    /usr/bin/qmake

The qt5 qmake gets installed (in my case) to:

    $TMPDIR/sysroots/x86_64-linux/usr/bin/qt5/

Should the PATH which is generated for the devshell include this path too?


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: qt5 qmake
  2013-09-18 20:44 qt5 qmake Trevor Woerner
@ 2013-09-18 21:29 ` Martin Jansa
  2013-09-19  1:37   ` Trevor Woerner
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Jansa @ 2013-09-18 21:29 UTC (permalink / raw)
  To: openembedded-devel

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

On Wed, Sep 18, 2013 at 04:44:00PM -0400, Trevor Woerner wrote:
> If I want to run the devshell on a qt5 recipe from meta-qt5, I can't
> help notice that if I do:
> 
>     $ which qmake
> 
> I get
> 
>     /usr/bin/qmake
> 
> The qt5 qmake gets installed (in my case) to:
> 
>     $TMPDIR/sysroots/x86_64-linux/usr/bin/qt5/

Recipes internally use absolute path to qmake and other tools (through
OE_QMAKE_PATH_QT_BINS variable) but it's true that adding it to PATH
shouldn't cause any troubles.

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

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: qt5 qmake
  2013-09-18 21:29 ` Martin Jansa
@ 2013-09-19  1:37   ` Trevor Woerner
  0 siblings, 0 replies; 3+ messages in thread
From: Trevor Woerner @ 2013-09-19  1:37 UTC (permalink / raw)
  To: openembedded-devel

Hi Martin,

On 18 September 2013 17:29, Martin Jansa <martin.jansa@gmail.com> wrote:
> Recipes internally use absolute path to qmake and other tools (through
> OE_QMAKE_PATH_QT_BINS variable) but it's true that adding it to PATH
> shouldn't cause any troubles.

Okay, thanks for the explanation. I'll create a patch and see what you think.

Best regards,
    Trevor


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-09-19  1:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-18 20:44 qt5 qmake Trevor Woerner
2013-09-18 21:29 ` Martin Jansa
2013-09-19  1:37   ` Trevor Woerner

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.