Problem with adding input files...
rpgoldman at sift.net
Fri Jun 30 15:25:01 UTC 2017
On 6/30/17 Jun 30 -10:11 AM, Faré wrote:
> First, can you confirm that the compute-action-stamp called by
> mark-operation-done called by the perform :after method on define-op
> returns the correct value?
Hm. I don't see any such after method. All I see is this:
(defmethod perform ((o define-op) (s system))
(assert (equal (coerce-name s) (primary-system-name s)))
(if-let ((pathname (first (input-files o s)))))
(let ((*print-readably* nil)
;; Note that our backward-compatible *readtable* is
;; a global readtable that gets globally side-effected. Ouch.
;; Same for the *print-pprint-dispatch* table.
;; We should do something about that for ASDF3 if possible,
or else ASDF4.
(*package* (find-package :asdf-user))
;; resolve logical-pathnames so they won't wreak havoc in
(pathname-directory-pathname (physicalize-pathname pathname)))))
(((and error (not missing-component))
:name (coerce-name s) :pathname pathname
(asdf-message (compatfmt "~&~@<; ~@;Loading system definition~@[
for ~A~] from ~A~@:>~%")
(coerce-name s) pathname)
;; dependencies will depend on what's loaded via
(unset-asdf-cache-entry `(component-depends-on ,o ,s)))
(load* pathname :external-format (encoding-external-format
This looks like it should do the right thing, but I don't know. At any
rate, I'm having a hard time tracking down exactly where we determine
whether or not a define-op needs redoing. The caching code makes things
much more efficient, but it also effectively camouflages the algorithm....
More information about the asdf-devel