Calling into an ECL-compiled .so from C, best practices, how to pass strings, etc...
marius.gerbershagen at gmail.com
Sun Mar 14 11:12:47 UTC 2021
unfortunately, the links in your email are all dead except for the first
one, therefore I can only offer some general comments.
1. Use ecl_base_string_pointer_safe to get a char* pointer to the
contents of a base-string. This will signal an error if the argument is
not a base-string or is not null-terminated. For converting a string
containing unicode characters to an utf-8 encoded base-string, the
can be used, e.g.
cl_object utf8_encode_base_string(cl_object string)
cl_object output = ecl_alloc_adjustable_base_string(ecl_length(string));
cl_object stream = si_make_sequence_output_stream(3, output,
cl_write_sequence(2, string, stream);
ecl_write_char(0, stream); /* write null terminator */
2. Are we talking about a utf-16/32 encoded string with 16/32 bit wide
wchar_t or a utf-8 encoded string with ordinary 8-bit char's? In the
latter case you may also use sequence streams to convert your utf-8
encoded char* into a Lisp string (see for example
for a possible implementation. This is from a feature that I'm currently
working on so that function will likely land in the next ECL release).
3. Functions from the common-lisp package should be called directly with
their exported names. For other functions, the best way is to use
ecl_make_symbol and cl_funcall, e.g.
cl_funcall(2, /* number of arguments to the funcall function */
ecl_make_symbol("SOME-FUNCTION","SOME-PACKAGE"), /* function
to call */
4. You can pass `--with-asdf=builtin` to the configure script to get an
ECL executable with ASDF built in. However that won't help with startup
time. ECL can't build an image like other lisps can, so we need to load
all fasls (or shared libraries which are really the same thing for ECL)
at runtime. I recommend not using ASDF in the final executable/shared
library if avoidable. ASDF is really a built system mostly meant for
PS: the API ECL has for converting strings between lisp and C is
definitely lacking. Feel free to open merge requests on gitlab if you
feel like improving this.
Am 09.03.21 um 01:01 schrieb Eric Schulte:
> I’m trying to compile a common lisp system into a .so which I can then
> wrap a Python library around to enable easy sharing of the functionality
> as a Python package (wheel). I’m having trouble finding examples of
> other C code calling into ECL-compiled shared objects of lisp code. I
> hope I can solicit some answer and critical code review here, or
> pointers to exemplar implementations would also be much appreciated.
> So far I have:
> 1. A Makefile  rule to build the .so from the common lisp package.
> This part actually seems to be working well (if slow to compile).
> 2. A C source file  wrapping the ECL-compiled shared object. I think
> this is likely where most of my problems are: specifically:
> 1. How does one get a string back out from Common Lisp to C?
> Currently I’m jumping through hoops that seem like they should
> be unnecessary  and only work some of the time (other times
> I’m getting multiple copies of the string text).
> 2. How does one get a UTF8 string from C (wchar_t*) into Common
> Lisp? I haven’t found a way so for now I’m limiting my input to
> ASCII (char*) .
> 3. Is the best way to invoke a function really to call
> c_string_to_object (e.g.,  among many others)? It seems like
> there should be a more efficient way than converting a string
> into a function name for every function dispatch.
> 4. Finally, calling init  has two problems. First, it takes a
> very long time every time I load the library. Is there no way
> to save the state of the lisp image after initialization?
> Second, it loads ASDF from a path relative to my local system.
> Can I get ASDF compiled into the shared object to remove as many
> external dependencies as possible?
> Any help is much appreciated. Also, thanks to those who answered issues
> on the ECL GitLab repository to help me get this far.
> The information contained in this e-mail and any attachments from
> GrammaTech, Inc may contain confidential and/or proprietary information,
> and is intended only for the named recipient to whom it was originally
> addressed. If you are not the intended recipient, any disclosure,
> distribution, or copying of this e-mail or its attachments is strictly
> prohibited. If you have received this e-mail in error, please notify the
> sender immediately by return e-mail and permanently delete the e-mail
> and any attachments.
More information about the ecl-devel