Re: Relativising FASL Cache Paths

2017-12-17 Thread Faré
On Sun, Dec 17, 2017, 06:08 Nicolas Hafner wrote: > On 17/12/17 12:02, 73budden . wrote: > > Nicolas, can you resolve source locations at SWANK level? E.g. > functions like SWANK/SBCL::SOURCE-FILE-SOURCE-LOCATION might be > appropriate for patching: you take the location that

Re: Relativising FASL Cache Paths

2017-12-17 Thread Nicolas Hafner
On 17/12/17 12:02, 73budden . wrote: > Nicolas, can you resolve source locations at SWANK level? E.g. > functions like SWANK/SBCL::SOURCE-FILE-SOURCE-LOCATION might be > appropriate for patching: you take the location that SBCL gives you, > but then redirect SWANK to other place. I guess this is

Re: Relativising FASL Cache Paths

2017-12-17 Thread 73budden .
Hi! Nicolas, can you resolve source locations at SWANK level? E.g. functions like SWANK/SBCL::SOURCE-FILE-SOURCE-LOCATION might be appropriate for patching: you take the location that SBCL gives you, but then redirect SWANK to other place. I guess this is not the only place you have to patch, it

Re: Relativising FASL Cache Paths

2017-12-15 Thread Faré
Source location via logical pathnames works great on CCL. However, on SBCL, they run afoul of SBCL's strict enforcement of the standard limitations to logical pathnames, and you will have quite a hard time with them if you succeed at all. One easy but fragile and ugly way to make it work with

Re: Relativising FASL Cache Paths

2017-12-15 Thread Nicolas Hafner
I see, thanks a lot for the hint. I've just stumbled upon another complicating factor though, which is source location information. Apparently it is not possible to manually relocate source information after it has been loaded from a FASL in SBCL. However, if the Lisp files were compiled using a

Re: Relativising FASL Cache Paths

2017-12-15 Thread Faré
The design of ASDF is that you should properly initialize the output-translations. The usual way is to use ~/.config/common-lisp/asdf-output-translations.conf, but since in your case you support the directory moving from one instantiation to the next, it is probably better to call

Relativising FASL Cache Paths

2017-12-15 Thread Nicolas Hafner
Hello everyone. I have a rather particular problem that I have so far not been able to solve on my own without brittle workarounds. Specifically, I'm looking for a way to ensure that the directory paths stored in the FASL cache directory are, if possible, truncated according to some other path