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

Bruce Ashfield bruce.ashfield at gmail.com
Wed Feb 8 13:57:36 UTC 2017


On Wed, Feb 8, 2017 at 8:53 AM, Joshua Lock <joshua.g.lock at linux.intel.com>
wrote:

> On Tue, 2017-02-07 at 17:35 +0000, Burton, Ross wrote:
>
>
> On 7 February 2017 at 04:24, Khem Raj <raj.khem at gmail.com> wrote:
>
> This is converging the recipes for go from
> meta-virtualization and oe-meta-go
>
>
> I'm still of the opinion that this should be in meta-go, not oe-core...
>
>
> FWIW I disagree. Go is a popular systems language and we're increasingly
> supporting a wide-array of systems with OE (from iot to ivi and beyond).
>
> Go is already in wide enough use and duplicated in enough layers that we
> would be doing folks a favour by including it in OE-Core and our build/test
> cycle.
>

I said as much during the oe developer meeting in Berlin last year as well.

I've done work in meta-virt out of necessity, as the cadence of the various
layers
was easily getting out of sync. The problem with 'language layers', is that
they
update based on the tools/packages/libs and not a system level use case.

Having something in oe-core forces that cadence of updates + QA that makes
it much easier to use as part of the eco system.

My Canadian 2 cents worth,

Bruce


>
> Joshua
>
> --
> _______________________________________________
> 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/20170208/ff1c6331/attachment-0002.html>


More information about the Openembedded-core mailing list