Are there C API (code bindings) and pre-built binaries?

[ababo]

I would like to link AccessKit to my Golang app.

[mwcampbell]

Sorry, not yet. I want to land one more refactor (#205), and then community work on such things can begin.

[ababo]

I see #205 is already merged. Is there an estimate for addition of C API layer? Will it happen soon?

[DataTriny]

Hi @ababo ,

We have started working on this. It is too early to give an ETA though.

[DataTriny]

Status update: I've pretty much finished creating a C API for the common crate (the part needed to describe your UI), it is here. Actually, it would be great if you could give your opinion on it by having a look at its header file.

I'll implement the API for the platform adapters in the following days (which should be quick in comparison to what has already been done). By next week I should be able to move onto modifying our CI so we can ship pre-built binaries and headers.

Feedback much appreciated!

CC @bruvzg

[bruvzg]

Looks fine to me.

I assume char * strings are copies and objects returned by accesskit_*_new functions should be freed by the caller. So it should at least have a comment to indicate who's responsible for freeing stuff, and maybe have dedicated accesskit_*_destroy (or something similar) functions for the objects.

[mwcampbell]

We need a function in the C API to free the C strings that are allocated by the getters. Since those strings are allocated by the Rust allocator, it's not safe to free them using the C standard library's free function. Also, in general, memory must always be freed by the same library that allocated it, particularly when the library is built as a DLL on Windows.

[DataTriny]

I've just opened #230.

There are still some rough edges with slices and arrays, and I've not tested the bindings on macOS, but I hope to have this merged soon.