Hi there,

I'm constantly seeing references to "statically compiling an extension" but
I can't find any reference on how exactly to do that. My usage case is I
want to distribute an executable completely independent of Chicken
libraries *and* the matchable extension, which is weird since even though
it simply implements macros, it still gets loaded as an .so in the compiled
code.

How would I do this? This is pretty necessary for my usage case since a big
folder full of .sos and a shell script wrapper isn't exactly elegant...

Thanks!
Eric Dong
_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users

Reply via email to