[OE-core] [PATCH 1/2] go: Add recipes for golang compilers and tools

Bruce Ashfield bruce.ashfield at gmail.com
Fri Nov 11 16:44:28 UTC 2016


On Fri, Nov 11, 2016 at 11:02 AM, Khem Raj <raj.khem at gmail.com> wrote:

> On Fri, Nov 11, 2016 at 5:10 AM, Alexander Kanavin
> <alexander.kanavin at linux.intel.com> wrote:
> > On 11/10/2016 02:39 AM, Khem Raj wrote:
> >>
> >> This is converging the recipes for go from
> >> meta-virtualization and oe-meta-go
> >
> >
> > Wait a moment, why this should go to oe-core and not to meta-go? Is there
> > something in oe-core itself that requires presence of go compiler?
>
> Nothing thats enabled in OE-Core depends on go yet, however, thats not
> always the reason
> for something to be in OE-Core, if you look out, you will see there is
> no single layer for golang ( I see atleast 5 )
> support, each one of them is done differently, some are better than
> others depending upon what you need,
> This causes a lot of confusion for users who have golang needs.
>  golang is a fast growing language being adopted in verticals where OE is
> used,
> This would offer a consolidated place for golang in OE ecosystem.
>

Agreed.

There's a reason why meta-virt has such extensive go support .. we never
could
get consistent behaviour from the other layers, and changes took a while to
coordinate.

Getting a good baseline in oe-core would simplify a lot of layers, and it
is only
a matter of time before there's a direct user in oe-core.

Bruce


> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161111/663b5679/attachment-0002.html>


More information about the Openembedded-core mailing list