From: Khem Raj <raj.khem@gmail.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] go-examples: Add an example, helloworld written in go
Date: Sun, 13 Nov 2016 18:07:47 -0800 [thread overview]
Message-ID: <24f641ad-b1da-4941-f882-60dfea11d72c@gmail.com> (raw)
In-Reply-To: <CABcZANmkhnCF0-p75sAC-p2fOrYmjSPo9==OqDjPDwnZd-uUzQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1675 bytes --]
On 11/10/16 6:59 PM, Christopher Larson wrote:
>
> On Wed, Nov 9, 2016 at 5:39 PM, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> wrote:
>
> diff --git a/meta/recipes-extended/go-examples/go-examples.inc
> b/meta/recipes-extended/go-examples/go-examples.inc
> new file mode 100644
> index 0000000..c632681
> --- /dev/null
> +++ b/meta/recipes-extended/go-examples/go-examples.inc
> @@ -0,0 +1,10 @@
> +DESCRIPTION = "This is a simple example recipe that cross-compiles a Go
> program."
> +SECTION = "examples"
> +HOMEPAGE = "https://golang.org/"
> +
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM =
> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
> +
> +S = "${WORKDIR}"
> +
> +inherit go
> diff --git a/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
> <http://go-helloworld_0.1.bb>
> b/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
> <http://go-helloworld_0.1.bb>
> new file mode 100644
> index 0000000..af9d3b7
> --- /dev/null
> +++ b/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
> <http://go-helloworld_0.1.bb>
> @@ -0,0 +1,15 @@
> +require go-examples.inc
> +
> +
> +SRC_URI += " \
> + file://helloworld.go \
> +"
> +
> +do_compile() {
> + go build helloworld.go
> +}
>
>
> Under what circumstances would one use the go_do_compile from go.bbclass vs this?
I think this is a good point. It would be more appropriate to use
the primitives from go.bbclass in this example. I will try to rework it
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-11-14 2:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 0:39 [PATCH 1/2] go: Add recipes for golang compilers and tools Khem Raj
2016-11-10 0:39 ` [PATCH 2/2] go-examples: Add an example, helloworld written in go Khem Raj
2016-11-11 2:59 ` Christopher Larson
2016-11-14 2:07 ` Khem Raj [this message]
2016-11-11 13:10 ` [PATCH 1/2] go: Add recipes for golang compilers and tools Alexander Kanavin
2016-11-11 16:02 ` Khem Raj
2016-11-11 16:44 ` Bruce Ashfield
2016-11-11 16:52 ` Burton, Ross
2016-11-11 18:04 ` Richard Purdie
2016-11-14 13:00 ` Alexander Kanavin
2016-11-14 17:49 ` Khem Raj
2016-11-15 18:43 ` Matt Madison
2016-11-11 17:16 ` Maciej Borzęcki
2016-11-11 18:11 ` Khem Raj
2016-12-12 12:36 ` Gary Thomas
2016-12-12 18:02 ` Khem Raj
2017-01-25 19:40 ` Maciej Borzęcki
2017-01-25 19:57 ` Khem Raj
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=24f641ad-b1da-4941-f882-60dfea11d72c@gmail.com \
--to=raj.khem@gmail.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox