freenode/#ecl - IRC Chatlog
Search
9:15:48
princesspancake
The manual about system building says it is possible to link ECL runtime statically. How can I do this ?
9:24:20
jackdaniel
however that has a downside -- you won't be able to load fasls (you'll need to compile everything statically, or link as a .so library)
9:32:06
princesspancake
if i build a shared library and i ship it with libecl.so, i dont need anything else ? like ECL doesn't have other file dependencies ?
9:34:56
princesspancake
what i want is to build a .so file that contains everything, including the bytecode compiler so i can run some files without compiling them to C first
9:35:28
princesspancake
if i can't do that with the libecl.a i will just ship the libecl.so alongside my built .so file
9:48:52
jackdaniel
you may compile a shared library or a static library, but in that case you need to initialize them manually
9:49:08
jackdaniel
I think that a similar approach is covered in one of examples in examples/ directory
9:50:22
jackdaniel
what I'm saying is that even with statically compiled ecl you can build libraries
9:51:01
jackdaniel
that's something what should be improved by untangling libecl.a staticness and dynamic load, but we are not there yet
9:53:30
princesspancake
well i'll only have 2 use case : a lisp .so loading .lisp/.fasc files, or compiling files into a .so file from the loaded shared library so i wouldn't need to load .fas files