Building a real static binary
daniel at turtleware.eu
Thu Aug 24 08:18:11 UTC 2017
you can build ECL as a static library and statically link with it. You
have to pass --disable-shared flag at configure time. Then you will have
libecl.a and statically linked ecl binary. This option isn't well tested
but it works as far as I can tell. You may want to link your library
with other static libs, like libcmp.a etc, which will be installed in
Note, that you won't be able to load natively compiled FAS files (only
bytecompiled FASC) at runtime, only to compiled with build libraries.
That could be fixed and is somewhere on my list (though it has a low
On 22.08.2017 00:27, Florian Margaine wrote:
> I've been trying to build a real static binary for easy deployment.
> So far, everything I've tried still links to libecl as a shared
> library; is it possible to have a static library of it, so that my
> static binary can bundle it?
> I guess I kind of want to shy away from building ECL myself, it's kind
> of a pain to require that for other developers working on this
More information about the ecl-devel