From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Vasilii Smirnov <vasilii.smirnov@mailbox.org>
Cc: help-guix@gnu.org
Subject: Re: Difference between guix/build and guix/build-system
Date: Tue, 14 May 2024 22:59:44 +0200 [thread overview]
Message-ID: <87wmnw2jpb.fsf@pelzflorian.de> (raw)
In-Reply-To: <31b66a4c-b54e-b207-7594-902a15e351c3@mailbox.org> (Vasilii Smirnov's message of "Tue, 14 May 2024 16:13:30 +0200")
Hi,
Vasilii Smirnov <vasilii.smirnov@mailbox.org> writes:
> Oh, nice, I completely missed that page. Thanks! Although it would be
> nice if it went into more detail... Like, I see that both "build" and
> "build-system" parts define the "${name}-build" function
> (e.g. cmake-build). But the definitions are different.
>
> The way I interpret these docs is that everything in the "build" part
> is solely for use from inside of gexps?
Almost, there are exceptions like guix/build/syscalls.scm.
> And the "build-system" part is
> for use by the host code, that embeds these gexps. That would explain
> duplicate function names then...
I don’t know well; in the case of cmake-build, I guess so. Note
however: The proper term is build-side code. Gexps are an example of
build-side code, but phases are older than gexps and are build-side code
too. guix/build-system/cmake.scm is older than gexps, but uses gexps
now.
Regards,
Florian
prev parent reply other threads:[~2024-05-14 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 14:45 Difference between guix/build and guix/build-system Vasilii Smirnov
2024-05-14 9:24 ` Hartmut Goebel
2024-05-14 10:24 ` pelzflorian (Florian Pelz)
2024-05-14 14:13 ` Vasilii Smirnov
2024-05-14 20:59 ` pelzflorian (Florian Pelz) [this message]
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=87wmnw2jpb.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=help-guix@gnu.org \
--cc=vasilii.smirnov@mailbox.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).