Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Lorn Potter <lpotter@trolltech.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building auxiliary tools in qmake2-native
Date: Wed, 25 Jul 2007 09:41:35 +1000	[thread overview]
Message-ID: <46A68E2F.5000005@trolltech.com> (raw)
In-Reply-To: <46A5F7CF.5000105@klever.net>

Michael Krelin wrote:
>> Will the opie-lrelease-native work? If not, a lrelease-native package
>> sounds like the way to go.
> 
> I'd guess opie-lrelease-native is a bit outdated for qt4, but I've never 
> used it, so I'm not sure.

Yes, lrelease is version specific.


> That wasn't a question of whether we should use build system's qt tools, 
> it was about not splitting qt into many native packages, but rather 
> using a single qt-native, since, for instance, qmake2-native has to 
> build half a qt, anyway, to support qt3 compatibility layer. I don't 
> think dropping qt3support is a feasible option. If not, then, of course 
> adding a missing lrelease-native is the way to go.


If you configure with qt3-support in qt4, I think you won't get all of 
Qt 4's features, but I could be wrong, or it might have changed.



-- 
Lorn 'ljp' Potter
Software Engineer, Systems Group, MES, Trolltech




      reply	other threads:[~2007-07-24 23:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 20:47 Building auxiliary tools in qmake2-native Matt Hoosier
2007-07-17 21:37 ` Michael Krelin
2007-07-17 21:58   ` Matt Hoosier
2007-07-17 22:06     ` Michael Krelin
2007-07-23  4:59       ` Matt Hoosier
2007-07-23 14:28       ` Richard Purdie
2007-07-24 12:59         ` Michael Krelin
2007-07-24 23:41           ` Lorn Potter [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=46A68E2F.5000005@trolltech.com \
    --to=lpotter@trolltech.com \
    --cc=openembedded-devel@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