From: Guillaume Le Vaillant <glv@posteo.net>
To: jgart <jgart@dismail.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix and Coleslaw Home Recipe!
Date: Fri, 16 Sep 2022 11:31:29 +0000 [thread overview]
Message-ID: <871qsbr0w2.fsf@kitej> (raw)
In-Reply-To: <20220915184406.GB32204@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
jgart <jgart@dismail.de> skribis:
> jgart ponders to self:
>
> Will this package build the `coleslaw` CLI command with our current asdf-build-system?
>
> What's missing?
>
> https://github.com/coleslaw-org/coleslaw
>
> Here's my attempt but there's no executable in the store for `coleslaw`:
>
> https://git.sr.ht/~whereiseveryone/guixrus/commit/9f8a48141c5e6c4bcdde21164db733c66d189724
By default, unless upstream put code in the ASDF system definition to
make a standalone binary automatically, asdf-build-system will only
compile the files of the library. To make a binary, you can add a phase
using the 'build-program' function, as in the stumpwm package for
example.
It might be better separate the library and the CLI program, for example
{sbcl,cl,ecl}-coleslaw packages for the libraries and a coleslaw package
for the CLI, or a single coleslaw package with several outputs ('out'
for the CLI and 'lib' for the library).
> Guillaume, what do you think if I add documentation or a tutorial
> somewhere for how to deal with common lisp packages that require to build
> an executable? Before I do that though, I'd like to first understand
> fully what I'll be writing about ;()
>
> any advice much appreciated,
>
> jgart
There is a little paragraph about the 'build-program' function in the
"Build Systems" section of the manual. You could improve it by adding
more details or examples.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2022-09-16 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 23:44 Guix and Coleslaw Home Recipe! jgart
2022-09-16 11:31 ` Guillaume Le Vaillant [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qsbr0w2.fsf@kitej \
--to=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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.