[updated web page
david@lichteblau.com**20080208121558] {
hunk ./doc/GNUmakefile 1
-all: index.html
-
-index.html: index.xml index.xsl
- xsltproc index.xsl $< >index.html
rmfile ./doc/GNUmakefile
addfile ./doc/index.html
hunk ./doc/index.xml 1
-
- A script to update/install the latest versions of all the most
- important Common Lisp packages.
-
- clbuild is a shell script helping with the download, compilation, and
- invocation of Common Lisp applications. It defaults to SBCL but
- otherwise tries to be somewhat independent of your local
- environment.
-
- clbuild was originally written by Luke Gorrie.
- (Idea from jhbuild by James Henstridge, a Gnome hacker).
-
- Currently, the following libraries and applications are supported
- (2007-06-24):
-
- Please send patches and bug reports
- to
- clbuild-devel@common-lisp.net
- (list information).
-
- Q How does clbuild differ from asdf-install?
-
- A clbuild includes a list of
- In contrast, asdf-install can install
- About
-
- FAQ
-
-
-
- To starts clbuild's slime, make sure to use the Windows version of - Emacs, not cygwin's Emacs. -
- - -- At this point, clbuild is maintained in darcs. There are several - branches of clbuild, the most recent of which is probably David's: -
-$ darcs get http://www.lichteblau.com/blubba/clbuild-
- Other repositories are Christophe's - tree at http://common-lisp.net/~crhodes/clbuild and Luke's - original - repository at http://fresh.homeunix.net/~luke/misc/repo/clbuild -
- -You might want to make the shell script executable:
-$ cd clbuild -clbuild$ chmod +x clbuild- -
- Try the interactive dialog if you have dialog(1): -
-clbuild$ ./clbuild dialog-
- Without the dialog, use command line arguments: -
-- clbuild depends on various helper applications. - Try check to make sure they are installed: -
-clbuild$ ./clbuild check -Checking for helper applications... -found /usr/bin/X11/cvs -found /usr/bin/X11/svn -found /usr/bin/X11/darcs -found /usr/bin/X11/wget -found /bin/tar -found /bin/mktemp -Success: All helper applications found. - -Checking Lisp startup... -Success: Lisp starts up using "sbcl" - -Looking for installable systems... -0 systems definition files registered- -
- If that worked, run update or build to download - (and optionally also build) the userland: -
-clbuild$ ./clbuild update -cvs co flexichain... -cvs co mcclim... -... lots of output not shown ... -update complete -46 systems definition files registered-
- Use dumpcore update to create a core file containing all - applications, accelerating application startup considerably. -
-clbuild$ ./clbuild dumpcore -... lots of output not shown ... -[undoing binding stack and other enclosing state... done] -[saving current Lisp image into /home/david/clbuild/monster.core: -writing 1664 bytes from the read-only space at 0x20000000 -writing 5024 bytes from the static space at 0x20100000 -writing 181661696 bytes from the dynamic space at 0x1000000000 -done] -./clbuild ok -monster.core dumped-
- You can also download and recompile SBCL using buildsbcl - or buildworld: -
-clbuild$ ./clbuild buildsbcl-
- For other options, see help: -
-clbuild$ ./clbuild help -Usage: - check check availability of all necessary helper applications - - update download/update all applications - recompile recompile all applications - dumpcore recompile and dump a core file for faster startup - build update && dumpcore - - buildsbcl download/update and compile SBCL - world buildsbcl && build - - clean delete all compiled object files - mrproper delete all downloaded source and fasl files - - slime run the Superior Lisp Interaction Mode in a fresh Emacs - lisp run Lisp in the terminal - sbcl alias for "lisp" (with all packages available to REQUIRE) - openmcl alias for "lisp" - - listener run the McCLIM listener - gsharp run the Gsharp score editor - climacs run the Climacs text editor - closure run the CLOSURE web browser - (required Debian packages: gif2png,libjpeg-progs) - beirc run the Beirc IRC client - climplayer run the CLIMPlayer music player - (required Debian packages: mplayer, fileschanged, fam) - eclipse run the eclipse window manager - - hunchentoot run the Hunchentoot web server test - webdav DIR run the CL-WEBDAV server, serving directory DIR - (required Debian packages: libssl-dev) - - dialog show an interactive menu - -Default when started without arguments is 'dialog'. - -If you do 'world' or 'buildsbcl' then SBCL will be installed in -target/ and used for future commands. If you don't run these commands -(or you remove target/) then clbuild uses the 'sbcl' in your PATH. - -Set CCL to your OpenMCL binary to use OpenMCL instead of SBCL. -Example: CCL=~/ccl/lx86cl64 ./clbuild build -(Not supported with targets 'buildsbcl' and 'sbcl'.) - -Set CLIM_BACKEND=gtkairo to enable clim-gtkairo instead of clim-clx. -(Requires GTK+ >= 2.8.)- rmfile ./doc/index.xml hunk ./doc/index.xsl 1 -
+ A script to update/install the latest versions of all the most + important Common Lisp packages. +
+ ++ clbuild is a shell script helping with the download, compilation, an + invocation of Common Lisp applications. It defaults to SBCL but + otherwise tries to be somewhat independent of your local + environment. +
+ ++ clbuild was originally written by Luke Gorrie. + (Idea from jhbuild by James Henstridge, a Gnome hacker). +
+ ++ The last time someone updated this web page, the following libraries and + applications were supported as part of the main project list: +
++ And the following projects were part of the wnnp list (work-needing + and prospective projects): +
++ Please send patches bug reports + to + clbuild-devel@common-lisp.net + (list information). +
+ ++ 2008-01-20 + In addition to the main projects list, we now have a list of projects + that are not downloaded by default, called WNPP projects (work-needing and + prospective projects). Acceptance criteria for WNPP projects are less + strict than for main projects, allowing us to add more projects than + previously. +
+
+ 2007-10-07 David's repository moved from
+ http://www.lichteblau.com/blubba/clbuild
+ to
+
+http://common-lisp.net/project/clbuild/clbuild.
+ Project members should be able to push into this repository.
+
+ How does clbuild differ from asdf-install? + +
++ clbuild includes a list of selected libraries + and applications and their well-known locations, and + downloads the newest version or CVS/SVN/darcs repositories if + possible. It can also build SBCL for you and includes convenient + commands to start various applications. +
++ In contrast, asdf-install can install any software + listed on Cliki. It always downloads release tarballs. (It + is up to the user to hunt down the trustworthy PGP keys as a + protection agains malicous wiki entries.) +
+ ++
+
+ Just add it to clbuild/wnpp-projects. Please + send a note to the mailing list so that we can include it, too. + (See below for notes on the dependencies + file.) +
++ + +
+
+ We use version-controlled download mechanisms to avoid losing local + changes when updating. +
++ clbuild's source directory is meant as an area + where hackers can do their work, and we wouldn't feel confident + recommending it for that purpose if we had to delete and move + directories or extract tarballs in there. +
++ Instead, we have the clbuild + mirror with darcs conversions of tarball-only projects. +
++ (Future versions of clbuild might do that darcs conversion + on-the-fly somewhere in a new directory clbuild/import, and then use + darcs pull from that directory into clbuild/source. The downside of + that approach would be that different users (and separate clbuild + checkouts by the same user) would have incompatible darcs checkouts + for the same project.)
++ + +
+
+ + +
+
+ + +
+
+ + +
+
+ + +
+
+ + +
+
This file is an educated guess and sometimes not perfect. We prefer + to err on the side of too many dependencies rather than too few. +
++However, the following situations are not necessarily bugs: +
++Make sure to distinguish between project dependencies and system +dependencies. +
++The following process computes the "project dependencies" of a project +FOO: +
++This process implies that dependencies between projects are not +transitive. +
++For example, the project `babel' depends on the project `rt' because the +system BABEL-TEST depends on the system RT. +
++But the system HUNCHENTOOT depends only on BABEL, not BABEL-TEST, so the +project `hunchentoot' does not depend on the project `rt'. +
++Think about "clbuild update hunchentoot" as "install everything I need +to use/hack all parts of hunchentoot", which doesn't include BABEL-TEST +or RT. "clbuild update babel" means "install everything I need to +use/hack babel", which includes BABEL-TEST and hence RT. +
++
+
+
+ clbuild is maintained in darcs. +
+$ darcs get http://common-lisp.net/project/clbuild/clbuild+ +
You might want to make the shell script executable:
+$ cd clbuild +clbuild$ chmod +x clbuild+ +
+ clbuild depends on various helper applications. + Try check to make sure they are installed: +
+clbuild$ ./clbuild check +Checking for helper applications... +found /usr/bin/X11/cvs +found /usr/bin/X11/svn +found /usr/bin/X11/darcs +found /usr/bin/X11/wget +found /bin/tar +found /bin/mktemp +Success: All helper applications found. + +Checking Lisp startup... +Success: Lisp starts up using "sbcl" + +Looking for installable systems... +0 systems definition files registered+ +
+ Use list to search for projects: +
+clbuild$ ./clbuild list web +i cl-webdav WebDAV server +i closure CLIM-based web browser +i hunchentoot web server formerly known as TBNL+
+ Run update to download the userland: +
+clbuild$ ./clbuild update --main-projects +cvs co flexichain... +cvs co mcclim... +... lots of output not shown ... +update complete +46 systems definition files registered+ +
+ You do not have to download all default projects (and in particular, + wnpp-projects are not part of the default download anyway). Instead, + you can specify a particular project, and download it with its + dependencies only: +
+clbuild$ ./clbuild update climacs +clbuild update climacs +climacs depends on: climacs clx flexichain mcclim slime spatial-trees +include dependencies in update? (Y/n)y +cvs co climacs... +cvs co clx... +... lots of output not shown ...+
+ To reduce start up times, you can dump a core file including all + main projects (or the projects specified on the command line, just like + with update): +
+clbuild$ ./clbuild climacs # slow, from fasls +clbuild$ ./clbuild dumpcore climacs +... +clbuild$ ./clbuild climacs # fast, using monster.core+
+ You can also download and recompile SBCL using buildsbcl + or buildworld: +
+ clbuild$ ./clbuild buildsbcl + ++ For other options, see help: +
+clbuild$ ./clbuild help +Usage: + check check availability of all necessary helper applications + + list [PATTERN] list all projects, or projects matching PATTERN + + update [--dependencies|--no-dependencies] PROJECT_NAME + download/update this project + update [--resume] + download/update main projects. With --resume, consider + only projects that a previous update run failed to fetch. + skip PROJECT_NAME + mark this project as done for the purposes of update --resume + + recompile [PROJECT_NAME] recompile main applications (or just PROJECT_NAME) + dumpcore [PROJECT_NAME] recompile and dump a core file for faster startup + build [PROJECT_NAME] update && dumpcore + + diff show local changes (for all version-controlled projects) + check-urls compared installed repository urls agains current locations + clean-links remove broken symlinks in systems/ + update-missing download only projects not present yet + register-asd PROJECT add .asd file symlinks for PROJECT + + buildsbcl [XC_HOST] download/update and compile SBCL + world buildsbcl && build + + clean delete all compiled object files + mrproper delete all downloaded source and fasl files + + slime run the Superior Lisp Interaction Mode in a fresh Emacs + lisp run Lisp in the terminal + + record-dependencies rebuild dependency information file + +Starting applications: + + run APPLICATION run this application + run --help show help for applications + +If you do 'world' or 'buildsbcl' then SBCL will be installed in +target/ and used for future commands. If you don't run these commands +(or you remove target/) then clbuild uses the 'sbcl' in your PATH. + +For configuration options (including for non-SBCL lisps), see clbuild.conf. ++ +
clbuild$ ./clbuild run --help +clbuild run APPLICATION [ARGS...] + + run listener run the McCLIM listener + run gsharp run the Gsharp score editor + run climacs run the Climacs text editor + run closure [HOME_PAGE_URL] run the CLOSURE web browser + (required Debian packages: gif2png,libjpeg-progs) + run beirc run the Beirc IRC client + run climplayer run the CLIMPlayer music player + (required Debian packages: mplayer, fileschanged, fam) + run demodemo run some random CLIM examples + run clim-alerts run CLIM alerts + run eclipse [DPY] run the eclipse window manager + + run hunchentoot run the Hunchentoot web server test + run webdav DIR run the CL-WEBDAV server, serving directory DIR + (required Debian packages: libssl-dev) + + run parse-xml FILENAME + check XML for well-formedness + run validate-xml FILENAME + check XML for validity + run validate-relax-ng [--compact yes] XML-FILENAME SCHEMA-FILENAME + check XML for validity against a Relax NG Schema + run html-to-xhtml HTML-FILENAME OUTPUT-FILENAME + run xhtml-to-html XML-FILENAME OUTPUT-FILENAME + convert between HTML 4 and XHTMl + + run vecto-demo generate a test image using vecto ++ + }