All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Busch <morphis@gravedo.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] qt4-libs-native: add initial recipe
Date: Sun, 08 May 2011 19:14:53 +0200	[thread overview]
Message-ID: <4DC6CF8D.5090706@gravedo.de> (raw)
In-Reply-To: <BANLkTinafst602eBgMcMY9igWn1QA7wdJg@mail.gmail.com>

On 08.05.2011 18:59, Otavio Salvador wrote:
> On Sun, May 8, 2011 at 13:51, Simon Busch <morphis@gravedo.de> wrote:
> ...
>> Hm, I need it for the embedded variant of qt4 so we should add it to
>> qt4.inc which is already quite complex and very target specific. I think
>> the best option is to create a qt4-native recipe which provides both
>> qt4-tools-native and qt4-libs-native. This would even be the best option
>> to be backward compatible (some stuff in OE is depending on
>> qt4-native-tools in different versions).
> 
> The native variant does need to be the embedded one for you? I think
> you just needed it to run something that uses QtCore or something
> similar during the build process (my case) and then build it for the
> target.

No, the native variant should be build from the qt4 anywhere package as
it's already the case for the qt4-tools-native. My qt4-native recipe
does this too. It builds only the needed tools and libraries and
installs them to the sysroot. Currently it builds:

- src/tools/moc
- src/corelib
- src/xml
- src/network
- src/tools/uic
- src/tools/rcc
- src/xmlpatterns
- src/testlib
- src/qt3support

If some other libs/tools are needed for any other native tool we should
add it to the list above.

And yes, you are right my recipes which need the qt4-native one only
needs the Qt4 core libs (as it should be the case for most native stuff
which uses qt4).

regards,
Simon



      reply	other threads:[~2011-05-08 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07 13:07 [PATCH] qt4-libs-native: add initial recipe Simon Busch
2011-05-07 19:17 ` Otavio Salvador
2011-05-08 12:28   ` Simon Busch
2011-05-08 16:33     ` Otavio Salvador
2011-05-08 16:51       ` Simon Busch
2011-05-08 16:55         ` [PATCH] qt4-native: introduce the native version of qt4 Simon Busch
2011-05-08 17:18           ` Otavio Salvador
2011-05-08 17:48             ` Simon Busch
2011-05-08 17:54               ` Otavio Salvador
2011-05-08 18:01                 ` Simon Busch
2011-05-08 18:05                   ` Otavio Salvador
2011-05-08 20:13                   ` [PATCH] qt4-native: introduce the native version of qt4 and remove old qt4-tools-native Simon Busch
2011-05-09  1:35                     ` Otavio Salvador
2011-05-08 16:59         ` [PATCH] qt4-libs-native: add initial recipe Otavio Salvador
2011-05-08 17:14           ` Simon Busch [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=4DC6CF8D.5090706@gravedo.de \
    --to=morphis@gravedo.de \
    --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.