From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building auxiliary tools in qmake2-native
Date: Wed, 18 Jul 2007 00:06:56 +0200 [thread overview]
Message-ID: <469D3D80.7040104@klever.net> (raw)
In-Reply-To: <d543f5920707171458q3c13f402x16c8c8fb37f280ea@mail.gmail.com>
>> I do not know what 'lrelease' is (ignorant, remember?), so I'd also ask
>> if you really sure that, for instance, uicmoc is not a better place for
>> the tool than qmake?
>>
>
> This is the tool which generates the final binary version of the
> message catalogs. The equivalent for a libintl-based project would be
> "msgfmt."
Thanks, that explains the purpose of the tool, but I would be still in
doubt where should it go if not in lrelease-native (after all we do have
opie-lrelease-native package).
> I had completely managed to overlook the presence of the uicmoc-native
> packages. Let me give those a try before bothering anybody further
> about this stuff.
No, I think I know it's not there.
>> The other thing is that when building uicmoc with qt3support module OE
>> has to build almost the whole qt, anyway. Would it not be better if we
>> just have qt-native package with all the tools installed? That would
>> reduce the amount of merciless and senseless patching and I believe
>> would reduce the slice of disk-space/cpu-time continuum eaten up by most
>> of the builds.
>
> I'm pretty much agnostic about the breakdown of the particular
> packages that end up providing the native tools used during target
> builds.
I understand, this pretty general question was a call for opinions.
Love,
H
next prev parent reply other threads:[~2007-07-17 22:08 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 [this message]
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
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=469D3D80.7040104@klever.net \
--to=hacker@klever.net \
--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 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.