Next: , Previous: , Up: Configuring ASDF   [Contents][Index]

4.1 Configuring ASDF to find your systems

In order to compile and load your systems, ASDF must be configured to find the .asd files that contain system definitions.

There are a number of different techniques for setting yourself up with ASDF, starting from easiest to the most complex:

Note that your Operating System distribution or your system administrator may already have configured system-managed libraries for you.



~/common-lisp/ is only included in the default configuration starting with ASDF 3.1.2 or later. If your implementation provides an earlier variant of ASDF, you may need to explicitly configure it to use this path, as further explained.


For Windows users, and starting with ASDF 3.1.5, start from your %LOCALAPPDATA%, which is usually ~/AppData/Local/ (but you can ask in a CMD.EXE terminal echo %LOCALAPPDATA% to make sure) and underneath create a subpath config/common-lisp/source-registry.conf.d/.


By requiring the .conf extension, and ignoring other files, ASDF allows you to have disabled files, editor backups, etc. in the same directory with your active configuration files.

ASDF will also ignore files whose names start with a . character.

It is customary to start the filename with two digits, to control the sorting of the conf files in the source registry directory, and thus the order in which the directories will be scanned.

Next: Configuring ASDF to find your systems — old style, Previous: Configuring ASDF, Up: Configuring ASDF   [Contents][Index]