From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Go build system
Date: Mon, 25 Jul 2016 00:25:40 +0200 [thread overview]
Message-ID: <87mvl68yhn.fsf@gnu.org> (raw)
In-Reply-To: <20160711213621.GA22573@jasmine> (Leo Famulari's message of "Mon, 11 Jul 2016 17:36:21 -0400")
Hello!
Leo Famulari <leo@famulari.name> skribis:
> I just wrote my first package using Go, the crude Syncthing package that
> is attached. It still needs a lot of work, especially since it builds
> Syncthing's dependencies from bundled copies instead of external
> packages.
>
> But, it does illustrate some of the assumptions that Go makes when
> building. It seems that Go is very particular about directory
> structures; it would be better if we could avoid these contortions by
> setting some environment variables.
It outlines the command sequence that needs to be run. I’d suggest
starting from that in ‘go-build-system’. Let’s make it work for this
package, and then we can adjust if some of the assumptions happened to
be specific to Syncthing.
> Should Go packages refer to the compiler? This Syncthing package does
> retain a reference.
I suppose it keeps a reference to run-time support libraries provided by
the ‘go’ package?
> I hope to get some replies from some people who have been building Go
> software for longer than 1 day ;)
I have infinitely less experience than that ;-) but since nobody replied
I thought I’d share my 2¢.
Ludo’.
next prev parent reply other threads:[~2016-07-24 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 21:36 Go build system Leo Famulari
2016-07-24 22:25 ` Ludovic Courtès [this message]
2016-07-25 8:47 ` Andy Wingo
2016-07-25 19:50 ` Leo Famulari
2016-07-25 22:05 ` Go & bundling Ludovic Courtès
2016-07-26 1:56 ` Catonano
2016-07-26 4:06 ` Alex Griffin
2016-07-26 12:07 ` Alex Griffin
2016-08-02 20:50 ` Leo Famulari
2016-07-26 6:33 ` Go build system Christopher Baines
2016-08-02 20:42 ` Leo Famulari
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=87mvl68yhn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.