Unloading libraries for delivery
John Fremlin <jf <at> msi.co.jp>
2009-02-02 02:50:04 GMT
Luís Oliveira <luismbo <at> gmail.com> writes:
> On Fri, Jan 30, 2009 at 6:05 AM, John Fremlin <jf <at> msi.co.jp> wrote:
>> Luis, would you consider a patch to add a special variable
>> *cffi-wrapper-delay-load* which would set a special mode for the
>> generated wrapper.lisps?
> I'd rather solve the problem in a more general way. (And document it
> in the manual.) Every library out there calls LOAD-FOREIGN-LIBRARY at
> load-time. What can we do to make that work in delivery-friendly way?
That's a really good point. Even if you give a quite extensive selection
of places to search for a library in, when the image is dumped the one
location where it was found on the dumping machine is stored in the
image. Restarting the image will crash before reaching user code, if
the library is not in the exact same place (as I understand it).
The ability to unload all libraries before dumping makes a lot of sense.
> Not using absolute paths is one way, but is that not enough for the
> wrapper libs?
The C libraries for wrapper files are generated inside the source
directory, or wherever asdf decides to put them. This generally means
that delivery without source (or at least, without the structure of the
source tree) is inconvenient.
It would be great if the list of the generated libraries could be
queried at delivery time, so they can all be copied into a destination