[usocket-devel] Usocket and ECL's MAKE-BUILD

[Juan Jose Garcia-Ripoll]

There are various things in how the usocket library is packaged that prevent
it from being used in standalone programs with ECL. I summarize them

- A package usocket-system is defined and used in package.lisp. This package
is not needed, as ASDF provides it and when the executable is created it
does not exist.

- Standalone executables do not have ASDF in it. There is no need. Yet
usocket uses it to define a logical hostname which is never used.

- The references to usocket-system propagate to usocket-test.

I attach a patch against the version that quicklisp distributes. With this
patch usocket builds as an independent library without problems and can be
shipped in standalone executables as well.

Juano

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/usocket-devel/attachments/20110826/b408a565/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patches.diff
Type: application/octet-stream
Size: 2764 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/usocket-devel/attachments/20110826/b408a565/attachment.obj>