jgart <jg...@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.
signature.asc
Description: PGP signature
