Converting types at runtime thwarts all of CFFI's compiler
macros. CFFI-UFFI-COMPAT:ALLOCATE-FOREIGN-OBJECT already did this;
propagate the same approach to other similar places.

Move the C toolchain support to its own system cffi-toolchain.

Create linkable object files and include them in output-files for
compile-op, so that they can be found and linked by a recent-enough
ASDF (3.1.6 or later).

Allow for delivery of a system with a single static and/or dynamic
library, and on support platform (CLISP, CMUCL, SBCL), enable delivery
of a standalone executable that statically links required extensions.

This requires a recent SBCL (will hopefully be released in 1.2.17).
ASDF 3.1.6 is required, but backward compatibility code is
provided at least back to ASDF 3.1.2.

On BSD, use ld -r for "libraries" instead of ar and possibly libtool.

When forking a Lisp to dump an image, support Quicklisp.

Make CFFI-Grovel generally more robust.

Document static linking operations in manual. Improve documentation.

Add test for ASDF support including wrappers.

Signed-off-by: Daniel Kochmański <daniel@turtleware.eu>

If &key arguments are mixed with &rest, then all provided keys are
mixed with rest. Since function passes all `rest' to shell command,
then it is undesireable to have there :output *xxx* - this would break
shell command call. `output' argument is removed now and output is
bound to *trace-output*.

Signed-off-by: Daniel Kochmański <daniel@turtleware.eu>

Signed-off-by: Daniel Kochmański <daniel@turtleware.eu>

Initial patch courtesy of François-René Rideau.

Previously, it was returning an expression, acting like a macro.

Thanks to Nathan Bird for spotting this bug

Patch courtesy of Gustavo Milare.

Reported by Christophe Rhodes. Passes all of uffi-tests again.

Bug reported by Aurelio Bignoli.

The changes are summarized here:
http://article.gmane.org/gmane.lisp.cffi.devel/1029

Also adapted tests and examples and uffi-compat.

Reported by Ricardo Alves.

- Better handling of shared library extensions on Windows.

Patch courtesy of Kevin Rosenberg.

If it is just a filename without a directory, continue passing it down
to the underlying functions, as they probably know how to find a library
in default location.s

The test now matches the uffi behaviour too.

- :pointer is no longer a built-in type so we have to parse it,
  not find-type it.
- def-array-pointer actually defines an array type with 1 element.
  (this emulates UFFI's behaviour)

Bug report and initial patches courtesy of Lou Vanek.

- Fixes an error when loading FASL files that dumped UFFI-CHAR instead
  of (UFFI-CHAR :CHAR) using MAKE-LOAD-FORM.
- Reported by Ricardo Boccato.

- New cffi-sys primitive: canonicalize-symbol-name-case. Use this
  instead of read-from-string. Also new tests for this.
- cffi-scl.lisp: correct the evaluation order of %MEM-REF and %MEM-SET.
  Have 'foreign-symbol-pointer return 'nil if the symbol is not found.
- uffi-compat.lisp: better support for SCL.
- defcfun.lisp (defcfun.undefined): package at time of eval may differ
  from the compile time package.

Patch courtesy of Douglas Crosher.

Patch courtesy of: Robert J. Macomber <xbxyh8 at rojoma.com>

Convert TYPE to the equivalent UFFI type at macro-expansion time
when constant.

Determine the element type at macro-expansion time when
the array type is constant.

Basically, extra quoting is supposed to be ignored.
Thus 'foo, ''foo, '''foo, are all valid types.

- WITH-FOREIGN-OBJECT should eval the type parameter. Fixed this
  as well as the examples and tests that assumed it wasn't evaluated.
- document WITH-FOREIGN-OBJECT in the manual.
- removed the pseudo ability to specialize arguments on
  define-type-translator. That didn't quite work, doh.
- removed dead code from cffi-uffi-compat::foreign-type-size
  specialized on the uffi-array-type.
- uffi-compat: parse (:array <type>) as (:array <type> 1)
- uffi-compat: reflect the fact that CFFI:WITH-FOREIGN-OBJECT now
  evaluates the type parameter.

- Refactoring of the type translation mechanism, now based on
  generic functions. The only user-visible changes is that you can
  now specialize the on the argument of the translator, and there's
  no type argument now (which was useless too for user-defined types).
- Don't export define-type-spec-parser since it's useless on its own.
- The anonymous :enum type is gone.
- Updated manual.

- Renamed: null-ptr -> null-pointer, null-ptr-p -> null-pointer,
  inc-ptr -> inc-pointer, with-foreign-ptr -> with-foreign-pointer,
  with-foreign-ptr-as-string -> with-foreign-pointer-as-string,
  foreign-slot-address -> foreign-slot-pointer,
  get-var-ptr -> get-var-pointer and
  foreign-symbol-ptr -> foreign-symbol-pointer.
- Updated various references to the old names in the cffi code itself,
  examples, tests and the manual.
- New functions: cffi(-sys):pointer-address and cffi(-sys):make-pointer.
- Use these in uffi-compat.
- Documented them in the manual.
- New tests: POINTER.1 and POINTER.2

- Implement uffi:make-pointer and export uffi:pointer-address.

- make the uffi-array-type be aggregate. (hopefully this didn't break
  uses of this type in other situations)
- add uffi's :struct-pointer type. (not well tested, but passes all
  tests from uffi's regression suite)

- removed foreign-object-alloc, added cffi:foreign-alloc with new options
  (including the functionality foreign-object-alloc provided).
- renamed the cffi-sys:foreign-alloc's to cffi-sys:%foreign-alloc.
- updated respective documentation.
- improved mem-aref's documentation including new examples.
- fixed with buf with lisp-string-to-foreign not handling empty strings
  correctly. added regression test.
- fixed translate-to-c and translate-from-c (not exported yet)
- fixed uffi-compat bugs, implemented all operators (including a bunch
  that aren't documented in UFFI's manual) except a foreign-string-length
  which is weird and not used anywhere.
- added "UFFI" as a nickname for the cffi-uffi-compat package.