So what I’ve done is opening and saving all the asdf-install’ed libraries in my library-folder (~/.asdf-install-dir/….) with Microsoft Word. That’s why we have WORD in our HD.. well jokin’ :-)

I thought about having separate libraries for mcl and LW, but it doesnt seem feasible, as the .asdf-install file (which configures where the dwnloaded libraries will go) is customizable, but unique. Unless you want to start moving it around… but it doesnt seem very practical ….

Once all the installed libraries (.asd and .lisp files) have been converted to the mac format, I just copied the aliases to the MCL-asdf registry folder (which can be anywhere). That’s actually what asdf looks up when you load a library!

WARNING:
Preferably, I guess, it’s good to make sure you don’t re-install what has already been asdf-install’ed through lispworks: since mcl can’t read files which are not “treated” as above, i dont know what’s going to happen.

Since it’s perfectly fine to asdf-install stuff without caring whether or not the lisp implementation of choice actually runs it, it’s possible to just install everything through LW, and then use it with other implementations whenever needed!
NEAT! That’s where my knowledge arrives right now…

The sad ending of the story, however, is that what I intended to run, Hunchentoot, doesn’t work on MCL. :-((((((((((((((((
A couple of the libraries (CFFI..) are not ported yet !