all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: Improve ASDF build system for Common Lisp libraries
Date: Sun, 13 Sep 2020 12:36:00 +0200	[thread overview]
Message-ID: <87y2le9d67.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87pn6rtd1y.fsf@yamatai>

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

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.

If you can't figure it out I can give it a shot.  Otherwise let's ask
the ASDF people.

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  parent reply	other threads:[~2020-09-13 10:36 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 [this message]
2020-09-13 12:49         ` Guillaume Le Vaillant
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=87y2le9d67.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=glv@posteo.net \
    --cc=guix-devel@gnu.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.
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.