The recommended way is to write a trivial .asd file for said library. The other way is to load this library first thing in your build as part of your Lisp setup, the same that loads asdf.lisp itself and configures your central registry and defines your optimization settings.
Speaking of optimization settings, does anyone see any problem with putting in ASDF something that deterministically (re)sets the optimization setting before each and any perform operation? Otherwise, optimization settings will vary wildly depending on what implementation you use, which files get recompiled, etc. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Every country has an army, either its own or a foreign one. 2009/10/28 Tamas Papp <tkp...@gmail.com>: > Hi, > > If I have an ASDF system that :depends-on various other ones _and_ > some other library that does not have and .asd file (eg it is a > standalone .lisp file), what is the standard way of loading the > latter? I am looking for something that eg automates manually > executing > > (load (compile-file "/path/foo.lisp")) > > and how to incorporate this into a defsystem. _______________________________________________ asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
