Tools to aid in the deployment of a fully standalone application.
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.
Customising Foreign Libraries
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 cl-mpg123 system provides a single library, which we would annotate like this:
(deploy:define-library cl-mpg123-cffi:libmpg123 :system :cl-mpg123)
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
:dont-open properties respectively.
Extending Deployment and Boot Behaviour
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:
:deployThese functions are responsible for copying files into the deployment target directory.
:buildThese functions should prepare the system for the dump to binary. Specifically you might want to shut down existing threads, close file handles, remove unneeded baggage, and remove potentially sensitive information about your system.
:bootThese functions are run right before the primary entry point is executed. Thus they are responsible for preparing the runtime to continue by restarting threads, re-opening files, and so forth.
:quitThese functions are run right before the executable exits completely. They offer a last-minute opportunity to dump some information about the system, or to clean up vital resources.
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
Deploying to an OS X App Bundle
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.
Debugging a Deployed Executable
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:
DEPLOY_DEBUG_BOOTif set to a non-empty value, on error the debugger is invoked rather than just exiting the application.
DEPLOY_REDIRECT_OUTPUTif set to a file path, the output of all streams is redirected to this file.
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.