[asdf-devel] [armedbear-devel] Patches for ABCL against asdf-1.641

[Faré]

Alan,

ASDF-Binary-Locations has been obsoleted and replaced by the more
easily configurable ASDF-Output-Translations, which is now built into
ASDF itself.

ASDF 1.660 also includes some compatibility mode with ABL, if for some
reason you love the old ABL way.

I hope ABCL has fixed its merge-pathnames woes.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
My understanding of macros is expanding
        — Matthias Felleisen wrt the PLT Scheme module system




On 16 March 2010 12:58, Alan Ruttenberg <alanruttenberg at gmail.com> wrote:
> How do you feel about integrating asdf-binary-locations into ABCL as
> well. I would make one change to what's there now, which is to add
> :java-1.4, :java-1.5, :java-1.6 to the list of architectures it has.
>
> -Alan
>
> On Tue, Mar 16, 2010 at 11:59 AM, Mark Evenson <evenson at panix.com> wrote:
>> Attached are patches in 'abcl-asdf.patch' to get asdf-1.641 to work against
>> ABCL for the run-tests.sh.
>>
>> Unfortunately, you will need to build [ABCL from trunk][1] using at least
>> svn r12550, because I had to patch ABCL to work with ASDF.  And you'll need
>> to apply the 'abcl-translate-pathname.patch'.
>>
>> [1]: svn://common-lisp.net/project/armedbear/svn/trunk/abcl
>>
>>
>> Notes:
>>
>> 1.  The fugliness of the conditional around ASDF:GET-UID works around a bug
>> in the ABCL compiler.  We are in the process of [analyzing the error][2].
>>
>> [2]: http://trac.common-lisp.net/armedbear/ticket/89
>>
>> 2.  There is some undiagnosed problem in translating the binary location for
>> the new ASDF2 "~/.cache" conventions, as ABCL seems to "collapses"
>> everything into a single directory.  Somehow, the default
>> *output-translations* have a "/**/**/*.*" where there should be "/**/*.*".
>>  I'm not sure if this is a problem in "abcl-translate-pathname.patch", which
>> is why I didn't apply this to ABCL trunk.
>>
>> 3. ASDF's run-tests.sh seems to ignore the "flags" setting, which seems to
>> be broken on the ASDF side.
>>
>> 4.  The changes for ASDF look quite interesting.  However I would advocate
>> you shouldn't do any of the subsumed ASDF-BINARY-LOCATIONS stuff without
>> being asked to by configuration.