[prev in list] [next in list] [prev in thread] [next in thread] 

List:       meego-dev
Subject:    Re: [MeeGo-dev] Yocto (new release)
From:       Jeremiah Foster <jeremiah.foster () pelagicore ! com>
Date:       2011-10-25 15:40:19
Message-ID: CADVDRBizgFti3w2nie7aj2wix5VLLL9cd3XPeYDsPu57UB9qMg () mail ! gmail ! com
[Download RAW message or body]

On Tue, Oct 25, 2011 at 4:06 PM, Samuel Stirtzel
<s.stirtzel@googlemail.com> wrote:
> 2011/10/25 Ross Burton <ross@linux.intel.com>:
>> On Sun, 2011-10-23 at 23:51 +0200, Jeremiah Foster wrote:
>>> Has anyone tried to build MeeGo with Yocto? It looks like its starting
>>> to mature a great deal as a project, lots of cross-platform support.
>>> Any feedback on Yocto, OE, or Bitbake from this list?
>
> Hi Jeremiah, a colleague got parts of the Netbook UX running with
> OpenEmbedded, but this was back at the time of OpenEmbedded classic.
> Currently I mainly use OpenEmbedded Core, but lately I tried the new
> Poky release and liked it.
> Using a GUI (Hob) to get an overview of available packages is very comfor=
table.

I saw that they've added a GUI front end for that. Should make it easier to=
 use.

>
> Bitbake itself is a really smart program, using Autotools informations
> that already exists for most packages makes it very easy to add new
> software.
> In example I took an already programmed Qt application and slightly
> adjusted the makefile, used a basic recipe template and compiled it,
> that's all and IMHO it is amazing.
> Of course it is not always that simple, but for stand alone
> applications that only provide a GUI and some logic it works well out
> of the box.

Fascinating. Thanks for the feedback!
>>
>> Starting to mature? =A0Poky had been used in commercial products for
>> several years when it was acquired by Intel in 2008. :)
>>
> Ross, looking at the realignment of OpenEmbedded Core and Yocto, IMO,
> the new release was a great step forward.
> Personally I pretty much like the process, in which Yocto benefits
> from patches sent for OE Core and vice versa.
>
> Now and then I still wondered about why Intel didn't adapt Meego in
> Yocto/Poky, because both are very interesting projects.
> And right now I wonder where Meego will be in the future.

Well there are a lot of people with @intel.com in their email
addresses that seem to be involved in the project so perhaps we'll see
some use of it in the future. With Tizen perhaps?

Regards,

Jeremiah
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
[prev in list] [next in list] [prev in thread] [next in thread]