Re: [asdf-devel] New version of ASDF with enhanced Allegro test script

Dave Cooper wrote: > > > > On Wed, Dec 11, 2013 at 11:04 AM, Robert P. Goldman > wrote: > > Now you can configure by simply pointing the test script at an install > directory (32- or 64-bit, conventional or SMP). > > > > But for the ASDF_TEST_LISPS we sti

Re: [asdf-devel] Loading pre-compiled fasls

>: Yellow Dog > I'm currently working with lisp-zmq which uses grovel to create the CFFI > declarations. This is fine and works great on my development box, but I > would prefer not to require that other developers in my organization also > run grovel. > > As such, I would like to be able to check

Re: [asdf-devel] New version of ASDF with enhanced Allegro test script

On Wed, Dec 11, 2013 at 11:04 AM, Robert P. Goldman wrote: Now you can configure by simply pointing the test script at an install > directory (32- or 64-bit, conventional or SMP). > > But for the ASDF_TEST_LISPS we still have to list out each executable, right? e.g. export ASDF_TEST_LISPS="alle

[asdf-devel] New version of ASDF with enhanced Allegro test script

I just pushed version 3.1.0.25 that contains a modified version of the test script dealing with tests of Allegro Common Lisp. I tweaked the configuration of ACL testing to more closely reflect the directory structure and executable naming as Franz ships their systems. Now you can configure by sim

[asdf-devel] Loading pre-compiled fasls

Hi, I was wondering if I could ask for some advice. I'm currently working with lisp-zmq which uses grovel to create the CFFI declarations. This is fine and works great on my development box, but I would prefer not to require that other developers in my organization also run grovel. As such, I wo