On Fri, Sep 14, 2012 at 6:34 PM, Dmitri Hrapof <hra...@common-lisp.ru>wrote:
> First of all, I'd like to say that
> ("-h" 0 #0# :noloadrc)
> in +default-command-arg-rules+ in cmdline.lsp prevents -h option (that
> preserves .h file) from working
>
Thanks for pointing this out. Actually it is not such a great loss because
the header files are not expected to be used -- they are only for debugging
purposes.
> Also I'd like to ask a question: how do I build shared libraries from lisp
> code?
I've tried
>
> ecl -c oci2.c -h oci2.h -data oci2.data -s -compile oci2.lisp
> gcc -shared -fPIC -O2 -o liboci2.so -lecl oci2.c
>
This cannot be done from the command line alone. The way it has to be done
has been explained several times in the mailing list and is documented,
partially, in the manual http://ecls.sourceforge.net/new-manual/re55.html
> And no includable header for the library gets generated, either...
Because they are not needed. A shared library only exports one function,
the init function, whose name can be customized, but normally takes the
form init_dll_FILENAME(int argc, char **argv)
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219672;13503038;z?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
