You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time I run my project,¹ it takes a few minutes for this library to grovel the same .c and .h files.
Given that these files are unlikely to change between executions, strikes me that we could just cache the grovel results, saving considerable time during development.
To this end, I modified my local copy of libusb-ffi.asd as follows:
It would be helpful if you could modify your library to support this. The problem, of course, would be to implement some mechanism for selectively choosing (when loading via quicklisp) between "normal" grovelling and cached grovelling.
Some ideas that might work:
Have the .asd file query the contents of the *features* special variable² (which the programmer presumably alters beforehand).
Somehow (defconstant ...) something before (ql:quickload)ing the library.
Have two different .asd files.
Alternatively, if I download this repo and place it in its own directory in my project, can I ignore the .asd file and (load) it myself in some way, but using caching-grovel instead of grovel?
¹ Specifically pkcmd-lx. I'm the dev ;)
² e.g. using the sharp-plus notation: #+cached-grovelling
The text was updated successfully, but these errors were encountered:
Every time I run my project,¹ it takes a few minutes for this library to grovel the same .c and .h files.
Given that these files are unlikely to change between executions, strikes me that we could just cache the grovel results, saving considerable time during development.
To this end, I modified my local copy of
libusb-ffi.asd
as follows:It would be helpful if you could modify your library to support this. The problem, of course, would be to implement some mechanism for selectively choosing (when loading via
quicklisp
) between "normal" grovelling and cached grovelling.Some ideas that might work:
*features*
special variable² (which the programmer presumably alters beforehand).(defconstant ...)
something before(ql:quickload)
ing the library.Alternatively, if I download this repo and place it in its own directory in my project, can I ignore the .asd file and
(load)
it myself in some way, but usingcaching-grovel
instead ofgrovel
?¹ Specifically
pkcmd-lx
. I'm the dev ;)² e.g. using the sharp-plus notation:
#+cached-grovelling
The text was updated successfully, but these errors were encountered: