> I am looking for a portable way to specify configuration for a library > before/during loading with ASDF2. It would be sufficient if the user > could specify an ALIST (or something similar) somewhere and I could read/ > use it when the library is loaded. Does ASDF2 have a "standard" > mechanism for library config files (eg where they are, how to handle them > etc), or should I use something else? I thought of using *features*, but > I need actual values instead of merely checking for the presence of > symbols. > ASDF (1 or 2) does not handle C libraries. Extensions to ASDF do. In this case, you might want to ask on the CFFI mailing-list.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org _______________________________________________ pro mailing list pro@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/pro
