3:39:19gendl1. have a .asd file for your application which has a :depends-on (:cl-ppcre ...)
3:39:49gendl2. When ready for release, use (asdf:operate 'asdf:monolithic-compile-bundle-op <your-application-system-name>)
3:40:24gendlthat will produce one big .fasl with your whole application including its depended-upon stuff, presumably in the right order.
3:40:52gendlthen start a fresh sbcl image, load this .fasl, then dump image. (I'm not sure the specifics of that with sbcl). ASDF also has built-in operators for doing that.
3:41:43gendlSee this ancient blog post which needs to be updated/added to: http://gendl.blogspot.com/2013/03/saving-images-with-asdf3.html
3:43:37gendlit was suggested earlier today that someone needs to make a do's-and-don'ts for production application release and maybe a how-to. It's something which should be pretty routine and well known at this point but doesn't seem to be.
5:45:44no-defun-allowed- use burgled-batteries to interface python module that interfaces opencv for images
6:22:44no-defun-allowedstill, most of this box-mangling and vision stuff would read better in lisp but common-cv is just a very fine wrapper over C unfortunately
15:27:25|3b|if i'm defining an asdf module type that processes a directory of files, what do i need to do to get asdf to reprocess it when files in the dir change?
15:29:15|3b|right now i have (additional-input-files compile-op) that returns list of files (as relative pathnames) in the dir currently, and (perform compile-op) sees them, but it doesn't re-run compile-op if i reload the system after changing input files