You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am generating bindings for Go using SWIG. A bit challenging for me tbh.
I do not know if it is a convention or not, but SWIG failed throwing a syntax error when parsing lines from the single header containing:
static unsigned const
I figured out that just changing the order to this, fixed the problem.
static const unsigned
Yes, this is funny, but it made SWIG accept the Kompute.hpp header. lol.
I'm not familiar with quom at all. I'll try opening a PR
The text was updated successfully, but these errors were encountered:
Oh wow, that seems like a pretty nasty bug, thanks for the heads up, I think having SWIG interoperability would be important - currently the Python bindings are built using Cython and Pybind11, but SWIG is always a common tool for these. I would be interested to learn more about your implementation, if you publish it I'd be keen to try it and link it as I do quite a lot of work in Go as well.
Just tried this morning to make SWIG generate the wrapper. Works, assumes kompute is installed in /usr/local/lib . Only thing is that the types and methods are kinda messed up. I would really like to implement kompute for go. HMU by mail!
I am generating bindings for Go using SWIG. A bit challenging for me tbh.
I do not know if it is a convention or not, but SWIG failed throwing a syntax error when parsing lines from the single header containing:
I figured out that just changing the order to this, fixed the problem.
Yes, this is funny, but it made SWIG accept the
Kompute.hpp
header. lol.I'm not familiar with quom at all. I'll try opening a PR
The text was updated successfully, but these errors were encountered: