On 17 Apr 2021, at 17:09, Faré wrote:
One way to avoid unneeded regeneration in the future without lying
about the dependency would be to modify the script to:
1. Remember in the output the hash of the input.
2. In the regeneration script, have a shortcut that leaves the output
unchanged if the
thanks for the ideas Robert!
> I was wondering why it was important to avoid the build when the .h file
> is newer than the .spec file. This shouldn't happen very often, should
> it? Is it because:
>
the problem is much more down to earth: generating the spec file requires
launching a libllvm
On 14 Apr 2021, at 18:38, Attila Lendvai wrote:
FTR, i have managed to solve it with this:
(defclass generate-lisp-op (selfward-operation)
((selfward-operation :initform '( ; we will specify it in our
own
COMPONENT-DEPENDS-ON
(defmethod component-depends-on ((op generate-lisp-op) (c
FTR, i have managed to solve it with this:
(defclass generate-lisp-op (selfward-operation)
((selfward-operation :initform '( ; we will specify it in our own
COMPONENT-DEPENDS-ON
(defmethod component-depends-on ((op generate-lisp-op) (c c2ffi-file))
`((load-op ,(find-system
dear hackers,
i cannot convince ASDF to only perform my custom operation if the output
file doesn't exist; i.e. regardless of the modification times.
it's in cffi/c2ffi: foo.h -> foo.spec -> foo.lisp
when the spec is there, regardless of the mod time, i'd like to skip the
spec generation task.
