Skip to content

herbertjones/ffizer-templates

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 

Repository files navigation

ReadMe

Templates for use with ffizer.

cl-script-project

Usage:

ffizer apply --source https://github.com/herbertjones/ffizer-templates \
    --source-subfolder cl-script-project \
    --rev main \
    --destination ./my-project \
    -v project=my-project

This is a Common Lisp template based on:

It uses package-inferred-system to keep files organized. Although you can place the code inside the ~/common-lisp/ directory, it is not required thanks to using ocicl and peru.

To use it interactively, just add the directory to your asdf sources. I happen to use something like this in my interactive .sbcl file:

(let ((path #P"/home/herbert/.local/share/ocicl/"))
  (defun initialize-local-source-registry ()
    (asdf:initialize-source-registry
     `(:source-registry
       :ignore-inherited-configuration
       (:directory "/home/herbert/devel/my-project/")          ;; <-- add this
       (:tree ,(merge-pathnames "peru-managed-systems/" path))
       (:tree ,(merge-pathnames "systems/" path)))))
  (cl:export 'initialize-local-source-registry)
  (initialize-local-source-registry))

It is already setup to be run as a script with command line argument parsing using clingon. You can also dump an image using the build command.

Testing is setup using parachute. Run the test script to run the tests or (asdf:test-system 'your-system) when interactivity is setup.

About

Templates to use with ffizer.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published