Re: resolution of symlinks in asdf
"Robert P. Goldman" <[email protected]>
| Newsgroups | gmane.lisp.cclan.general |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Kevin" == Kevin Layer <[email protected]> writes: Kevin> [email protected] wrote: >>> Kevin, >>> >>> The change looks fine to me. But have you checked to see if >>> the asdf-binary-locations system does what you need already? >>> I write and run my code primarily in Allegro, but I try to >>> test it for SBCL and CMUCL (time permitting). I've found that >>> the asdf-binary-locations system does the trick just fine for >>> me, as is, to allow me to put my sbcl binaries (which also end >>> in '.fasl') in a separate location while sharing cl source... Kevin> Do you mean the output-files generic function? Gary Kevin> suggested that to me in a conversation, but I believed Kevin> after looking at the source that the pathname in the Kevin> component passed to it has already been resolved. Are you Kevin> saying this is not the case? Kevin> Also, I didn't like the solution of having to provide a Kevin> definition of this method along with an asd file. It seems Kevin> like a hack. Well the asdf-installable asdf-binary-locations system provides support for specifying the behavior of the output-files generic function w/o providing a new method definition. See http://www.cliki.net/ASDF-Binary-Locations But I haven't thought very hard about whether this would meet your precise needs. best, R