Also export some command-line related symbols from the driver.

into the encodings feature. utf-8 is the default encoding and use :default
at your own risk. Anything else gets delegated to asdf-encodings.

Move more release code from Makefile to CL.
Fix shell-tokens-to-Makefile on CLISP (CLISP bug in loop, or my misreading the spec?)
Fix some tests, make them more verbose.
Driver: Fix native-namestring on SCL; fix issues on CLISP:
Setting the *source-file-types* and *compiled-file-types* to nil
was preventing (require "linux") from working(!).

allows full bootstrap of XCVB, including ironclad.
Disable nemk self-build from tests,
as there is no ASDF equivalent to :around-compile.
Also, fix a2x wrt latest ASDF's find-system and reuse of component objects.

Fix a few glaring recent bugs.

c::builder'ing shared libraries.  Refactored the grain class hierarchy
a bit.

Fix list-files and export it to the command-line.
Fix version extraction in bootstrapped build.
Update documentation: document :executable. Remove ASDF1 crud.

+ Partial changes to get xcvb to build a binary of xcvb.
+ Extending :create-image to support executables.
+ Support for command line arguments when resuming the executable.
  These are passed to the entry-point. However, each lisp vendor
  mangles the argv a little and it needs work to be really right.
  For now it is good enough.
+ dump-image for ecl got hacked upon, but it is currently broken.
+ Changed example-1 to produce an executable, but currently this
  only works for lisp implementations which can produce them. This
  needs more consideration in the future, for example, the
  "executable" could be a script which invokes an image.
+ simple-build can now accept targets with empty computations.
  This implements the "phony target" idea in simple-build.

* extract fasl type from target:
 at least lispworks depends on pathname type and its fasl type varies!
* rucksack not available on clisp (and needed fixes; see our xcvb repo of it)
* accept compile-file failure semantics of clisp
* suppress duplicate entries for a directory in the source-registry:
 The first one wins, with its recurse and exclude flags.
* fix hello and test/runme
* fix various option parsing mistakes

(xcvb-unit-tests::test-simple-build :implementation 'lispworks)

when emitting output so it looks nice on the screen.
Added much more instrumentation of what xcvb isdoing at verbosity 10.
Got rid of some commented out code we don't need.

Rename search-path to source-registry, registry to grain-registry.
Extract ASDF implementation identifier from target, so we may use it later.

TODO: need to better control the cwd vs *default-pathname-defaults*

Try to improve release.

Unrot release and test scripts.
Tested: XCCL=stccl make test LISP=ccl

My, that what much more painful than it ought to be.

However, we don't interact correctly with cl-launch
to produce a standalone executable from an ECL executable image.
Presumably, we ought to support builds as .a files
instead of just as executable images. Future work.
At least, a proof of concept is here.

refactor vp handling, using a miniDSL default-vp-for-fullname.

Using a new lisp-object-grain class for .o, and fasl-grain for .fas.
Idea: for .515 I will undo much of that and use CFASL for .fas and FASL for .o

* fix various bugs left over from .507.
* back out generation of Lisp files in object tree
 until we can provide build processes with a mapping from name to pathname.
* pass self-test.

* cfasl support: *use-cfasls*, not *has-cfasls*.
* Normalize lisp module names to (:lisp ...).
* Validate names of grains.
* Tweak parse-module-declaration signature.
* Generated files go in object directory, not source!

distinct from their parent's.

Add (but not use yet) a pure grain set implementation.

Passes pre-release-test.

Give proper semantics to resolve-absolute-module-name and resolve-module-name.
Make the hello example work properly.
hello now uses the generate functionality to extract version from parent XCVB.
Have log-format do fresh-lines for you.
Make sure builds are only interned once.
Recognize that builds may be invalid because of inherited conflict.