All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
To: yocto@yoctoproject.org
Cc: Chris Elledge <celledge@digitallumens.com>,
	Leo Schwab <lschwab@sensity.com>
Subject: Re: Integrating Golang
Date: Thu, 30 Oct 2014 10:47:09 +0100	[thread overview]
Message-ID: <3084764.geF1bKoAFi@comp-006-thk> (raw)
In-Reply-To: <CAPhDKbFBPuxkh_+yfFH+Q+pQ3DSpPEKRpfbVE1qyW7uEiTDoqg@mail.gmail.com>

On Wednesday 10 of September 2014 13:53:14 Ilya Dmitrichenko wrote:
> Just a quick update, thought I'd let you know that I have a basic
> working layer here:
> 
> https://github.com/errordeveloper/oe-meta-go

There's also https://github.com/digitallumens/meta-golang

Based on that I've prepped some patches not long ago that integrate go into 
OE-core base on what Chris did in meta-golang. The patches are for both meta--
golang and OE-core. OE-core piece enables Go GCC frontend and libgo same way 
as Fortran or Java is handled. Also, Chris has already defined a usable 
golang.bbclass that handles gccgo build for you. So far it seems to work with 
some simple use cases on BeagleBone Black and Raspberry.

If there's interest I can update the patches to current master and post them 
to the list.

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.


  parent reply	other threads:[~2014-10-30  9:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 21:55 Integrating Golang Leo Schwab
2014-04-16 19:10 ` Hermanus Botha
2014-04-16 19:23   ` Hermanus Botha
2014-04-16 22:57   ` Khem Raj
2014-04-17  8:49 ` Martin Donnelly
2014-04-17 16:46   ` Khem Raj
2014-04-17 19:54   ` Leo Schwab
2014-08-30 18:44     ` Ilya Dmitrichenko
2014-09-10 12:53       ` Ilya Dmitrichenko
2014-09-10 13:36         ` Burton, Ross
2014-09-10 13:43           ` Paul Eggleton
2014-10-30  9:47         ` Maciej Borzecki [this message]
2014-10-30 14:43           ` Chris Elledge

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=3084764.geF1bKoAFi@comp-006-thk \
    --to=maciej.borzecki@open-rnd.pl \
    --cc=celledge@digitallumens.com \
    --cc=lschwab@sensity.com \
    --cc=yocto@yoctoproject.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.