Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
cl-launch
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jan Moringen
cl-launch
Commits
6b661661
Commit
6b661661
authored
11 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
4.0.2: updating some documentation.
parent
07c8ec11
Branches
Branches containing commit
Tags
4.0.2
debian/4.0.2-1
Tags containing commit
No related merge requests found
Changes
4
Show whitespace changes
Inline
Side-by-side
Showing
4 changed files
00INSTALL
+27
-3
27 additions, 3 deletions
00INSTALL
95TODO
+1
-0
1 addition, 0 deletions
95TODO
cl-launch.sh
+1
-1
1 addition, 1 deletion
cl-launch.sh
debian/changelog
+3
-0
3 additions, 0 deletions
debian/changelog
with
32 additions
and
4 deletions
00INSTALL
+
27
−
3
View file @
6b661661
...
...
@@ -24,6 +24,11 @@ If instead you want it in ``/usr``, do::
A list of variables you may want to modify or override is
at the beginning of the ``Makefile``.
Wherever you install cl-launch, we recommend you have a symlink
from /usr/bin/cl to wherever you installed cl-launch, so that
everyone may be able rely on that location for scripts that start with:
#!/usr/bin/cl
Advanced installation
---------------------
...
...
@@ -53,8 +58,7 @@ it would also do::
Configuration
-------------
Of course you should adjust your ``PATH``,
your ``asdf:*central-registry*`` and your ``XCVB_PATH``
Of course you should adjust your ``PATH`` and your ``CL_SOURCE_REGISTRY``
coherently with where you install cl-launch.
...
...
@@ -78,4 +82,24 @@ Get short help with
Get long help with
cl-launch --more-help | ${PAGER:-less}
See example in XCVB and Exscribe source code.
Here are three examples:
1- Running code directly from the command line:
cl -sp lisp-stripper "(count-lisp-loc \"asdf.lisp\")"
2- Defining a script that counts lines of Lisp code a la wc :
#!/usr/bin/cl -sp lisp-stripper -E main
(defun main (argv)
(if argv
(map () 'print-loc-count argv)
(print-loc-count *standard-input*)))
3- Comparing how the many implementations evaluate a same form:
for l in sbcl ccl clisp cmucl ecl abcl scl allegro lispworks gcl xcl ; do
cl-launch -l $l -i '(format t "'$l': ~S~%" `#5(1 ,@`(2 3)))' \
2>&1 | grep "^$l:" # LW, GCL are verbose
done
More examples in XCVB and Exscribe source code.
This diff is collapsed.
Click to expand it.
95TODO
+
1
−
0
View file @
6b661661
...
...
@@ -35,3 +35,4 @@ TODO for cl-launch as of 4.0.1.6
and not have to spawn an external program
unless explicitly requested a non-default implementation.
* Add support for --dispatched-entry and other options from Xach's buildapp.
This diff is collapsed.
Click to expand it.
cl-launch.sh
+
1
−
1
View file @
6b661661
#!/bin/sh
#| cl-launch.sh -- shell wrapper generator for Common Lisp software -*- Lisp -*-
CL_LAUNCH_VERSION
=
'4.0.
1.8
'
CL_LAUNCH_VERSION
=
'4.0.
2
'
license_information
()
{
AUTHOR_NOTE
=
"
\
# Please send your improvements to the author:
...
...
This diff is collapsed.
Click to expand it.
debian/changelog
+
3
−
0
View file @
6b661661
cl-launch (4.0.2-1) unstable; urgency=low
* Package control via --package and --system-package
* --entry is now a variant of --restart, not of --init.
* Fixes for ECL, LispWorks.
* Tests moved aside, which reduces script size by over 10%.
* ARGV0 support, in conjunction with ASDF 3.1.0.87.
* Documentation updated, as well as TODO file.
-- Francois-Rene Rideau <fare@tunes.org> Sun, 02 Mar 2014 15:46:55 -0500
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment