packages, and Quicklisp uses ASDF to compile
and load stuff.
Thanks in advance for any light you can shed on this problem.
e's the example foo.asd I've been working with.
:maintainer "Robert Dodier"
:author "Robert Dodier"
:description "Foo, Bar, and Baz"
I'm constructing the /... part of it. I wonder if it's
possible to tell ASDF it doesn't need to put in the
Thanks for your help, and if you have any comments, I would be
interested to hear about it.
Description: Binary data
Thanks for your help,
no conscious intent to assert that one condition or
another must prevail. Any improvements by more knowledgeable people
would be welcomed by me.
All the best,
puzzle out anything.
The more general idea is that the system contains a non-Lisp data
file. Is there a general approach to work with that?
Thanks for any light you can shed on this problem.
that this systems has flaws, but at this point I am
taking it as a given; I'm trying to make progress on a lot of fronts,
and cleaning up this monstrosity is a lower priority item.
led" file in it, you
> don't have to use *LOAD-TRUENAME*.
Hmm, examining the cache after running ASDF, I don't see the static
files there. But I think using the component slot to get the file
location is promising, I will give that a try.
place where the info file is found, just
as it is when the index.lisp is loaded via LOAD).
I suppose I could create a class that has the effect of copying the
info files without any other operation on them?
unfriendly behavior; it seems better that either it should complain or
Thanks for your help, I think I'm in good shape on this front now.
;; info-index.lisp -- ASDF component type for Maxima documentation index
;; copyright 2018 by Robert Dodier
;; I release
should in the future
> replace all current occurrences of static slots :initform with this style
I dunno -- I think I'm going to play it safe and use the old pattern,
if it's necessary at all ... I'm a pretty casual ASDF user, I don't
know if I can invest the time to figure the old vs new stuff.
All the best,
ASDF currently returns the
first system found, ...".
Is there any way to intervene to return a specific system,
specifically the most recent one?
Thank you once again for your help,
would have expected (on
little reason) that the parent class CL-SOURCE-FILE would supply that.
(2) In INPUT-FILES, why doesn't (info-index-type c) yield "lisp"?
Doesn't INFO-INDEX have an accessor INFO-INDEX-TYPE?
I may well be very confused about simple things. Thank you for your
't have my maxima-file hackery. If it turns out we need to go
into this in more detail, I will devise a more minimal example. But
first maybe someone can say what the name requirement is.
nks again, and best wishes.
ing that it is required to be
I found the text about pathname specifiers as well. I didn't see a
requirement there because neither the system name nor component names
were specified by the grammar or the commentary on the grammar to be
Thanks again for your help,
Mail list logo