On Thu, 2014-01-09 at 01:32 +0100, Martin Jansa wrote:
> I'm not saying that oe-core should be tested with 30 layers like my
> world build, but why cannot AB have special build which builds
>
> oe-core + meta-xorg + meta-gnome
>
> and runs some runtime QA tests on that and then some other build w
On 01/08/14 05:28, Richard Purdie wrote:
> On Tue, 2014-01-07 at 20:23 +0100, Martin Jansa wrote:
>> With PACKAGECONFIGs which can list optional dependencies which aren't
>> included in the the layer itself it's now easier to have recipe with
>> optional qt5 support in oe-core, but qt5 itself in se
Hello,
On Thu, Jan 9, 2014 at 4:32 AM, Koen Kooi wrote:
>
> Op 9 jan. 2014, om 01:32 heeft Martin Jansa het
> volgende geschreven:
>
> > On Wed, Jan 08, 2014 at 11:21:08PM +, Paul Eggleton wrote:
> >>> In my opinion...
> >>>
> >>> Personally I would be in favour of removing GTK+ and the GNOM
On Wed, Jan 8, 2014 at 10:32 PM, Martin Jansa wrote:
> On Wed, Jan 08, 2014 at 11:21:08PM +, Paul Eggleton wrote:
> > > In my opinion...
> > >
> > > Personally I would be in favour of removing GTK+ and the GNOME UI from
> > > the core and putting them in their own layer for all the same reason
Op 9 jan. 2014, om 01:32 heeft Martin Jansa het
volgende geschreven:
> On Wed, Jan 08, 2014 at 11:21:08PM +, Paul Eggleton wrote:
>>> In my opinion...
>>>
>>> Personally I would be in favour of removing GTK+ and the GNOME UI from
>>> the core and putting them in their own layer for all the
On Wed, Jan 08, 2014 at 11:21:08PM +, Paul Eggleton wrote:
> > In my opinion...
> >
> > Personally I would be in favour of removing GTK+ and the GNOME UI from
> > the core and putting them in their own layer for all the same reasons I
> > think Qt should be in its own layer:
> > - a "basic" im
On 01/08/2014 06:57 PM, Richard Purdie wrote:
> On Wed, 2014-01-08 at 23:21 +, Paul Eggleton wrote:
>> On Wednesday 08 January 2014 13:44:59 Trevor Woerner wrote:
>>> On 01/08/14 10:56, Paul Eggleton wrote:
However, one concern I have always had with Qt being moved out of
OE-Core thou
On Wed, 2014-01-08 at 23:21 +, Paul Eggleton wrote:
> On Wednesday 08 January 2014 13:44:59 Trevor Woerner wrote:
> > On 01/08/14 10:56, Paul Eggleton wrote:
> > > However, one concern I have always had with Qt being moved out of
> > > OE-Core though is that I very much doubt the same will happ
On Wednesday 08 January 2014 13:44:59 Trevor Woerner wrote:
> On 01/08/14 10:56, Paul Eggleton wrote:
> > However, one concern I have always had with Qt being moved out of
> > OE-Core though is that I very much doubt the same will happen with
> > GTK+ and GNOME UI components that we carry, which I
On Wed, Jan 08, 2014 at 01:44:59PM -0500, Trevor Woerner wrote:
> On 01/08/14 10:56, Paul Eggleton wrote:
> > However, one concern I have always had with Qt being moved out of
> > OE-Core though is that I very much doubt the same will happen with
> > GTK+ and GNOME UI components that we carry, whic
On 01/08/14 10:56, Paul Eggleton wrote:
> However, one concern I have always had with Qt being moved out of
> OE-Core though is that I very much doubt the same will happen with
> GTK+ and GNOME UI components that we carry, which I think will lead to
> the (perhaps erroneous, but logical) assumption
On Wed, Jan 08, 2014 at 03:56:04PM +, Paul Eggleton wrote:
> Hi all,
>
> On Tuesday 07 January 2014 13:27:22 Trevor Woerner wrote:
> > question:
> > Should some version of Qt be included in openembedded-core, or should
> > all recipes to add Qt be part of their own version-specific Qt layer?
>
Hi all,
On Tuesday 07 January 2014 13:27:22 Trevor Woerner wrote:
> question:
> Should some version of Qt be included in openembedded-core, or should
> all recipes to add Qt be part of their own version-specific Qt layer?
>
> background:
> openembedded-core[1] used to include recipes for Qt3, but
Hello folks,
On Tue, Jan 7, 2014 at 5:23 PM, Martin Jansa wrote:
> On Tue, Jan 07, 2014 at 01:27:22PM -0500, Trevor Woerner wrote:
> > Hello everyone,
> >
> > question:
> > Should some version of Qt be included in openembedded-core, or should
> > all recipes to add Qt be part of their own versio
On Tue, 2014-01-07 at 20:23 +0100, Martin Jansa wrote:
> I would like to see qt4 moved from oe-core to meta-qt4.
>
> That would remove the feeling that using oe-core defaults to using qt4
> and it would be consistent with other QT layers:
>
> meta-qt3
> meta-qt4
> meta-qt5
>
> oe-core would stay
On Tue, Jan 07, 2014 at 01:27:22PM -0500, Trevor Woerner wrote:
> Hello everyone,
>
> question:
> Should some version of Qt be included in openembedded-core, or should
> all recipes to add Qt be part of their own version-specific Qt layer?
>
>
> background:
> openembedded-core[1] used to include
Hello everyone,
question:
Should some version of Qt be included in openembedded-core, or should
all recipes to add Qt be part of their own version-specific Qt layer?
background:
openembedded-core[1] used to include recipes for Qt3, but as Qt3 became
old these recipes were replaced with Qt4 and t
17 matches
Mail list logo
