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
patches.diff
Description: Binary data
------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________ Ecls-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecls-list
