Nim bindings for Libvips #4678
Replies: 2 comments 1 reply
-
|
Ah, very cool! Thanks for letting us know @georgelemon! It looks like you're wrapping the C API, is that correct? It's usually best to wrap the GObject API instead. There's a chapter in the docs about this: https://www.libvips.org/API/current/binding.html You can wrap all libvips operations in just a few 100 lines of code, and there are no varargs, so it's (relatively!) easy to make it typesafe and leak-free. |
Beta Was this translation helpful? Give feedback.
-
|
... for example, these lines in the C++ binding let you call any libvips operation via introspection: https://github.com/libvips/libvips/blob/master/cplusplus/VImage.cpp#L423-L547 Then tiny wrappers generated by python give a typesafe interface, eg.: VImage
VImage::invert(VOption *options) const
{
VImage out;
call("invert", (options ? options : VImage::option())
->set("in", *this)
->set("out", &out));
return out;
}Generator code here: https://github.com/libvips/libvips/blob/master/cplusplus/gen-operators.py You can generate things like enums as well. |
Beta Was this translation helpful? Give feedback.
-
|
I added a link to the libvips README. Thanks again for doing this work, nice job! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey guys, the missing Nim bindings library for libvips is now available on GitHub and Nimble (Nim's package manager) https://github.com/openpeeps/libvips-nim or
nimble install libvips.Check
/testsfor usage examples.Beta Was this translation helpful? Give feedback.
All reactions