Commit d39d628d authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files add prototypical examples early in the documentation.

Tweak 95TODO.
parent ff2b108a
......@@ -46,6 +46,11 @@ TODO for cl-launch as of 4.0.6
* Support these other options from Xach's buildapp?
--load-path --asdf-path --asdf-tree --manifest-file --logfile
* asdf-path and asdf-tree would be accumulated into a source-registry
argument to be passed to cl-launch.
* load-path would not only require something similar, but also
using a SEARCH-AND-LOAD function that consults this path
before it loads something.
* Maybe add these SBCL-specific options, too?
* --compress-core
#| -- shell wrapper generator for Common Lisp software -*- Lisp -*-
license_information () {
# Please send your improvements to the author:
......@@ -150,6 +150,12 @@ Output options:
-d IMAGE --dump IMAGE dump IMAGE for faster startup
-X ... -- (see more help) use #!/.../cl-launch as script interpreter
-- -- end of arguments when using -x or -X
A typical command-line invocation would be such as:
cl -l sbcl -sp my-system-and-package '(some form)'
A typical Common Lisp script starts with a line such as:
#!/usr/bin/cl -sp my-system-and-package -E main
print_help_footer () {
......@@ -176,6 +182,9 @@ We'd like to homestead the path /usr/bin/cl while we can, so that
script authors can reasonably expect a script to work when it starts with:
(See SIMPLE CL-LAUNCH SCRIPTS below for caveats with #! scripts though.)
Recent Linux kernels support a script interpreter itself being a script;
BSD kernels don't and require a small C program cl-shim to be compiled and
installed as /usr/bin/cl to use cl-launch this way.
To work properly, cl-launch 4.0.4 depends on ASDF 3.0.1 or later, and
on its portability layer UIOP, to manage compilation and image life cycle.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment