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 think this could work, but I'm not sure if it's what you want? It seems a bit weird since there are two meson options (utils and libutils). libutils is responsible for defining HAS_KMSXXUTIL which is what causes pykms to try to call init_pykmsutils, but pykmsutil.cpp is only included based on the utils option. I think what you want is to change pykms/meson.build so that pykmsutil.cpp is included based on the libutils options instead of the utils option?
Ah, I was hasty, and didn't notice that the current meson.build uses 'utils'. That's obviously wrong. I'll look at this again later. And I see #69, so I should perhaps split the py bindings to two separate py modules, the core (depends on kms++) and the rest (depends on kms++utils).
Hi, I'm building with python bindings turned on, but the utils option is turned off. This seems to lead to an undefined symbol in pykms.so:
Looking at the code,
init_pykmstest
is called no matter what:kmsxx/py/pykms/pykms.cpp
Line 21 in 9c3df5f
But the implementation of the function in pykmsutil.cpp is only included in the build if the tests option is enabled:
kmsxx/py/pykms/meson.build
Lines 19 to 23 in 9c3df5f
The text was updated successfully, but these errors were encountered: