From: Guillaume Le Vaillant <glv@posteo.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Improve ASDF build system for Common Lisp libraries
Date: Sun, 13 Sep 2020 14:49:50 +0200 [thread overview]
Message-ID: <87pn6phmdt.fsf@yamatai> (raw)
In-Reply-To: <87y2le9d67.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> I thought about having the sources, SBCL compiled files and ECL compiled
>> files respectively in the 'out', 'sbcl' and 'ecl' packages outputs;
>> however I thought there could be issues in some cases.
>>
>> For example, if a profile contained cl-xyz and cl-xyz:sbcl, and if the
>> user tried to load this xyz system in ECL, then I think ECL would try
>> to compile the system and write the compiled files to cl-xyz:sbcl and
>> fail because it is read-only. That's because cl-xyz:sbcl contains the
>> ASDF configuration indicating "the compiled files for cl-xyz are in
>> cl-xyz:sbcl", and ECL is going to read that configuration.
>>
>> It might be possible to have smarter ASDF configuration files behaving
>> differently depending on the lisp implementation running, but I have not
>> investigated this for the moment.
>
> There is probably a way to tell where to load the libraries from, and
> where to compile them.
>
> By default, each compiler compiles to
> ~/.cache/common-lisp/$compiler_name-$compiler_version.
>
> This is what ECL should do here. The ASDF configuration should be so
> that it does not change this behaviour.
The ':implementation-type' or ':function' keywords of ASDF
configuration files described in [1] and [2] could be useful to do that.
Now, let's suppose that we put the sources in cl-xyz, the SBCL
pre-compiled files in cl-xyz:sbcl and the ECL pre-compiled files in
cl-xyz:ecl.
If a user installs only cl-xyz (the sources) and loads the system using
SBCL or ECL, I think he would expect the lisp implementation to compile
the thing and store the compiled files in the default
'$HOME/.cache/common-lisp/...' location, because he didn't install the
pre-compiled files.
So we would need the ASDF output-translation configuration to be able to
say something like: "if the pre-compiled files for the running lisp
implementation exist in '/gnu/store/...' and if the Guix package for
these pre-compiled files is installed in the current profile or
environment, then use them, else use the default
$HOME/.cache/common-lisp/...' directory".
I guess cl-xyz:sbcl and cl-xyz:ecl would also need to have links to the
ASDF configuration and to the sources in cl-xyz, in case the user
installs only cl-xyz:sbcl or only cl-xyz:ecl.
[1] https://common-lisp.net/project/asdf/asdf/Configuration-DSL.html
[2] https://common-lisp.net/project/asdf/asdf/Output-Configuration-DSL.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-09-13 12:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 9:36 Improve ASDF build system for Common Lisp libraries Guillaume Le Vaillant
2020-09-12 10:26 ` Pierre Neidhardt
2020-09-12 11:11 ` Pierre Neidhardt
2020-09-12 12:06 ` Guillaume Le Vaillant
2020-09-13 10:08 ` Guillaume Le Vaillant
2020-09-13 10:31 ` Pierre Neidhardt
2020-09-13 11:56 ` Guillaume Le Vaillant
2020-09-13 10:36 ` Pierre Neidhardt
2020-09-13 12:49 ` Guillaume Le Vaillant [this message]
2020-09-13 13:15 ` Pierre Neidhardt
2020-09-14 13:39 ` Guillaume Le Vaillant
2020-09-15 6:18 ` Pierre Neidhardt
2020-09-12 12:07 ` Pierre Neidhardt
2020-09-15 10:00 ` Guillaume Le Vaillant
2020-09-15 10:54 ` Pierre Neidhardt
2020-09-15 11:07 ` Ricardo Wurmus
2020-09-15 14:12 ` Katherine Cox-Buday
2020-09-15 16:28 ` Guillaume Le Vaillant
2020-09-17 9:45 ` Pierre Neidhardt
2020-09-23 11:15 ` Pierre Neidhardt
2020-09-23 12:44 ` Guillaume Le Vaillant
2020-09-23 13:35 ` Ricardo Wurmus
2020-09-23 13:41 ` Pierre Neidhardt
2020-09-12 15:35 ` Katherine Cox-Buday
2020-09-12 18:59 ` Konrad Hinsen
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=87pn6phmdt.fsf@yamatai \
--to=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.