This is a system to help you easily and quickly deploy standalone common lisp applications as binaries. Specifically it is geared towards applications with foreign library dependencies that run some kind of GUI.
In order to make use of Deploy, you'll have to change the ASDF system definition of your project to contain the following properties:
:defsystem-depends-on (:deploy) :build-operation "deploy-op" :build-pathname "my-application-name" :entry-point "my-package:my-start-function"
Once you have updated your system appropriately, all you need to do is start a fresh instance of your implementation from a terminal and run the following function:
This will build your system, gather the necessary information, and deploy a standalone `bin` folder within your project's root directory. You can then ship this folder to your users.
Sometimes you might want to designate a specific library for deployment, rather than the one used during development. If this is the case, you have to help Deploy out a little by defining extra information about the library with `define-library`. If the foreign library is in the source tree of a lisp library, you can simply associate the CFFI library with the system that provides it, and Deploy will find it automatically:
(deploy:define-library cffi-library-symbol :system :system-name-that-defines-the-library)
For example, the https://github.com/Shirakumo/cl-mpg123 system provides a single library, which we would annotate like this:
If the file is not contained in the directory of the system that provides it, you can also designate specific source directories to scan:
(deploy:define-library cffi-library-symbol :sources '("some/path/where/the/library/is/stored"))
Finally, you can also specify the path directly if you want Deploy to choose a particular file, rather than trying to find one on its own:
(deploy:define-library cffi-library-symbol :path "/some/path/to/the/file.so")
Generally though these extra associations should not be necessary as Deploy will simply take the path that CFFI has already figured out to find the library.
Sometimes it might not be desired to deploy all the libraries, or reload them all upon boot. You can change this behaviour with `define-library`'s `:dont-deploy` and `:dont-open` properties respectively.
Deploy also offers a hooks system with which you can easily extend the steps performed during deployment and during the boot process of the generated executable. With the `define-hook` macro you can add functions that are executed during various points of the process. Specifically, the following types are available:
If you would simply like to include a data directory to bundle with the rest, use `define-resource-directory`. After boot, all of the resource files will be in the directory returned by `data-directory`.
If you would like a nicely bundled `.app` for OS X, you can simply change the `build-operation` in your ASDF system file to `osx-app-deploy-op`. If you would like to customise the `Info.plist` file that is generated for the app, you can change `*info-plist-template*` to point to a file that contains what you want.
If you're having trouble with an application that's already deployed, there's a few things you can do to debug it by setting environment variables. The following are recognised by Deploy:
Particularly on Windows and OS X debugging can be an issue, as a GUI application will not get a standard output to write to. In that case, the above redirect might help. Alternatively, on Windows, you can build your binary with the feature flag `:deploy-console` present, which will force it to deploy as a console application.
Will recursively descend through shared libraries and copy them into a location if necessary. Will also use
install_name_tool to update paths.
In the function
process-libraries, the first list is a list of files to scan, and the second string is a path of which to copy the shared libraries to. Please use absolute paths.
All contributions and patches are accepted via email. You can use git send-email to create patches and send them to firstname.lastname@example.org. To find out more about git email patches please view the official documentation: