Hmmm. An ASDF definition lists :split-sequence as a dependency. I have
split-sequence.lisp, and I took a stab and pushed the pathname of its
directory onto *central-registry*, but ASDF still says it cannot find
the component.
I will be debugging the old-fashioned way in the meantime, but:
(a) this actually works? a single source file as an ASDF dependency?
(b) if so, the magic incantation is...what, create split-sequence.asd?!
thx
--
Kenny
Why Lisp? http://lisp.tech.coop/RtL%20Highlight%20Film
"I've wrestled with reality for 35 years, Doctor, and I'm happy to state
I finally won out over it."
Elwood P. Dowd, "Harvey", 1950
Kenny Tilton <·······@nyc.rr.com> writes:
> (a) this actually works? a single source file as an ASDF dependency?
No.
> (b) if so, the magic incantation is...what, create split-sequence.asd?!
Get the tarball from http://www.cliki.net/split-sequence, which
contains split-sequence.asd. Link that file to somewhere in your
*central-registry* or, if you're on a link-poor platform, add
something to your *central-registry* which resolves to the location
where you unpacked the tarball.
Christophe
Christophe Rhodes wrote:
> Kenny Tilton <·······@nyc.rr.com> writes:
>
>
>>(a) this actually works? a single source file as an ASDF dependency?
>
>
> No.
>
>
>>(b) if so, the magic incantation is...what, create split-sequence.asd?!
>
>
> Get the tarball from http://www.cliki.net/split-sequence, which
> contains split-sequence.asd.
ah, thx, I had just found s-s in a clocc distro.
--
Kenny
Why Lisp? http://lisp.tech.coop/RtL%20Highlight%20Film
"I've wrestled with reality for 35 years, Doctor, and I'm happy to state
I finally won out over it."
Elwood P. Dowd, "Harvey", 1950
On Fri, 02 Sep 2005 19:02:01 +0100, <·····@cam.ac.uk> wrote:
>
> Kenny Tilton <·······@nyc.rr.com> writes:
>
>> (b) if so, the magic incantation is...what, create split-sequence.asd?!
>
> Get the tarball from http://www.cliki.net/split-sequence, which
> contains split-sequence.asd. Link that file to somewhere in your
> *central-registry* or, if you're on a link-poor platform, add
> something to your *central-registry* which resolves to the location
> where you unpacked the tarball.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; find the ASDF files
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(defparameter *original-asdf-registry* ASDF:*CENTRAL-REGISTRY*)
(defun asdf-scanner ()
(directory
(make-pathname :directory
'(:absolute "usr" "local" "lib" "cmucl" "lib" "subsystems" :wild-inferiors)
:type "asd")))
(defun update-asdf-registry ()
(setf ASDF:*CENTRAL-REGISTRY*
(nconc (asdf-scanner)
*original-asdf-registry*)))
(update-asdf-registry)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
I've used the above hack to auto-build the *central-registry* for
months (in CMUCL).
--
Program A uses CLOS, Program B is implemented with structs, leading
to a fourfold increase in execution speed. --J. B. Heimatseiten
Kenny Tilton <·······@nyc.rr.com> writes:
> Hmmm. An ASDF definition lists :split-sequence as a dependency. I have
> split-sequence.lisp, and I took a stab and pushed the pathname of its
> directory onto *central-registry*, but ASDF still says it cannot find
> the component.
>
> I will be debugging the old-fashioned way in the meantime, but:
>
> (a) this actually works? a single source file as an ASDF dependency?
>
> (b) if so, the magic incantation is...what, create split-sequence.asd?!
>
> thx
Just in case you missed it, asdf-install will look for those
dependencies on CLiki, then download and unpack the depended-on
tarballs for you. The system you can ask it to install can be from
CLiki, or from a tarball.
--
/|_ .-----------------------.
,' .\ / | Free Mumia Abu-Jamal! |
,--' _,' | Abolish the racist |
/ / | death penalty! |
( -. | `-----------------------'
| ) |
(`-. '--.)
`. )----'