From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: help-guix@gnu.org
Subject: Re: Go build system - build from local directory fails
Date: Sun, 22 Dec 2024 07:12:47 +0100 [thread overview]
Message-ID: <6136144.lOV4Wx5bFT@ayase> (raw)
In-Reply-To: <87y10dntl3.fsf@coquand.email>
> An initial suspicion is that I haven't set ‘#:import-path’ as expected
> in the documentation. However, all examples I can find of this are
> builds from a github repository rather than a local file, so I am not
> sure what it needs to be set to.
>
> Any clue what I could be missing?
This is exactly it. You always must supply the #:import-path in Go build
system.
This path is vital to the operation of the build system, as it adapts Go build
environment to Guix environment. This path matches the name of the currently
built module.
In practice, it is the string that follows the 'module' keyword in go.mod
files.
I do not know the theory behind this coupling.
next prev parent reply other threads:[~2024-12-22 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 11:01 Go build system - build from local directory fails Marc
2024-12-22 6:12 ` Marek Paśnikowski [this message]
2024-12-23 20:44 ` 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
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=6136144.lOV4Wx5bFT@ayase \
--to=marek@marekpasnikowski.pl \
--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).