On Mon, Aug 24, 2009 at 5:18 PM, Ville Voutilainen<ville.voutilainen@gmail.com> wrote:
2009/8/24 Alessio Stalla <alessiostalla@gmail.com>:
When I run the project from the IDE, I launch a class which compiles and loads the Lisp systems using asdf. This works for me locally, but thinking about distributing the project to users, this approach has some drawbacks: - Lisp files must be true files, they can't be in a Jar (asdf doesn't understand jars). - Lisp files are recompiled every time, since the IDE always overwrites the Lisp source files in the output directory. - If I make a jar, it will contain Lisp source files, not binaries, since binaries are unknown to the IDE.
Create an ANT project, that allows you to do almost anything. Many java IDEs will be able to build with the ANT project (without trying to do their own clever, or not so clever wizardry), thus allowing all the flexibility that ANT allows.
Ok, good advice: this way I can compile the Java files first, then have ANT launch ABCL and compile my system with ASDF, and then package everything in a jar (depending on the target). However, when distributing the compiled library, I will still need code to load the Lisp parts (e.g. by extracting them and using asdf), am I correct? It's not a big deal actually... too bad ANT doesn't understand sexps, only xml ;) Ale