Hi Anton,

Interesting suggestion! I'll try it out. It still means changing the asd file that came with the package, but I think that's inevitable.

Thanks for the post!

Kevin


On Thu, Dec 12, 2013 at 9:38 PM, Anton Vodonosov <avodonosov@yandex.ru> wrote:
Why do you consider fasl files?
As far as I understand, grovel generates .lisp file first,
and only after that this Lisp code is compiled to .fasl.
 
So you could save the generated .lisp file and add it
as any other .lisp file to your ASDF system.
 
But note, this might be non-portable. The lisp code
is generated from C includes, which may have different
meaning on different platforms (different sizes of integer,
char and structure types, refer to different functions, etc).
 
If you distribute your ASDF system to the same platforms,
you can distribute it together with pre-generated grovel
output. But if you distribute it to different platforms,
the user still may need to run grovel himself.
 
Best regards,
- Anton