[asdf-devel] Disabling "built-in" output translation

[Faré]

On 17 May 2011 07:41, Mark Evenson <evenson at panix.com> wrote:
> ASDF contains some specialized code for ABCL that enable the translation of
> ASDF systems whose source is packaged into jar files to locate the
> corresponding object files in ASDF's user cache.

The ASDF API:
* clear-output-translations means
 "clear the current state, reload it from configuration when needed".
 It's useful when the configuration has or will change,
 e.g. before saving an image. It might not help you much here.

* disable-output-translations means
 "disable any output translation except those necessary for the system to run"
 as defined in wrapping-output-translations. Unhappily, that's where we put
 those jar file translations for ABCL, instead of, say,
 some entry at the bottom of *default-output-translations*.

Also, importantly, output-translations are sorted
from most-specific to least-specific, so when you disable,
even though the default for everything is to translate to same directory,
jar files will still be translated to the cache.
As they probably should be by default indeed.

Instead of disabling translations, you ought to add some specific translation
(more specific than the default jar translation) that will tell ASDF that
indeed for this or that jar, the fasls are stored in the jar,
with an entry like:
(:output-translations
  (#p"jar:file:/path/to/my.jar!/**/*.*")
  :inherit-output-translations)

Hope this helps.

BTW, for cl-launch and XCVB, I indeed am looking for a way to create
bundles from compiled stuff. How do I create a jar from ABCL and a set
of lisp files, precompiled or not?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Most people think they need a ruler. Perhaps we should give them a fake
one that doesn't actually do anything, and then they won't think about
it. It is sort of like giving an infant a pacifier. — Perry Metzger