From: raingloom <raingloom@riseup.net>
To: help-guix <help-guix@gnu.org>
Subject: Re: Name resolution failures during build
Date: Sat, 21 Nov 2020 21:38:43 +0100 [thread overview]
Message-ID: <20201121213843.6fdfb10f@riseup.net> (raw)
In-Reply-To: <20201121192209.GC1088@E5400>
On Sat, 21 Nov 2020 21:22:09 +0200
Efraim Flashner <efraim@flashner.co.il> wrote:
> On Fri, Nov 20, 2020 at 05:55:50PM -0500, Stephen Scheck wrote:
> > The project I'm attempting to package is a standalone application,
> > with a Makefile build system entrypoint - it is not a library, so I
> > don't think `go-build-system` is of any help here (though
> > presumably the Makefile uses golang build machinery under the
> > covers).
> >
> > Do any examples of standalone applications written in Go that are
> > already packaged for Guix jump to mind?
> >
>
> Don't look at syncthing, it needs a bunch of hand holding to compile
> correctly.
>
> containerd and docker-cli in gnu/packages/docker.scm are two examples
> of packages with binaries as outputs. I have a WIP package for
> keybase but there's a large number of unpackaged dependencies so I've
> only gotten some of them patched out.
>
I think Yggdrasil is a pretty clean example. It also uses a Makefile
wrapper, but really it just calls go build a bunch of times.
next prev parent reply other threads:[~2020-11-21 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 21:34 Name resolution failures during build Christopher Baines
2020-11-20 22:55 ` Stephen Scheck
2020-11-21 19:22 ` Efraim Flashner
2020-11-21 20:38 ` raingloom [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 20:09 Stephen Scheck
2020-11-20 20:47 ` Christopher Baines
2020-11-20 21:15 ` Stephen Scheck
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201121213843.6fdfb10f@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).