me
/
guix
Archived
1
0
Fork 0

doc: Tweak wording of 'chicken-build-system' material.

* doc/guix.texi (Build Systems): Fix spelling of "CHICKEN".  Add xref to
its web site.  Tweak wording.
master
Ludovic Courtès 2020-12-03 16:15:00 +01:00
parent eee037ec87
commit b5a6eddd8e
No known key found for this signature in database
GPG Key ID: 090B11993D9AEBB5
1 changed files with 10 additions and 9 deletions

View File

@ -7336,26 +7336,27 @@ defined by the crate.
@end defvr
@defvr {Scheme Variable} chicken-build-system
This variable is exported by @code{(guix build-system chicken)}.
It builds Chicken Scheme modules (also called ``eggs'' or ``extensions'').
Chicken generates C source code, which then gets compiled by a C compiler,
in this case GCC.
This variable is exported by @code{(guix build-system chicken)}. It
builds @uref{https://call-cc.org/, CHICKEN Scheme} modules, also called
``eggs'' or ``extensions''. CHICKEN generates C source code, which then
gets compiled by a C compiler, in this case GCC.
It adds @code{chicken} to the package inputs, as well as the packages of
@code{gnu-build-system}.
This build system adds @code{chicken} to the package inputs, as well as
the packages of @code{gnu-build-system}.
The build system can't (yet) deduce the egg's name automatically, so just like
with @code{go-build-system} and its @code{#:import-path}, you should define
@code{#:egg-name} in the package's @code{arguments} field.
For example, if you are packaging the srfi-1 egg:
For example, if you are packaging the @code{srfi-1} egg:
@lisp
(arguments '(#:egg-name "srfi-1"))
@end lisp
Egg dependencies must be defined in @code{propagated-inputs}, not @code{inputs}
because Chicken doesn't embed absolute references in compiled eggs.
Test dependecies should go to @code{native-inputs}, as usual.
because CHICKEN doesn't embed absolute references in compiled eggs.
Test dependencies should go to @code{native-inputs}, as usual.
@end defvr
@defvr {Scheme Variable} copy-build-system