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 ran into this issue, possibly related to my build process, when I build some code using android_ndk. When I add android_ndk My .so file now has the symbol AConfiguration_getScreenRound. Which makes sense because you create the bindings for android/configuration. But Android can't seem to find the thing to link it to!
I also get this issue when adding AConfiguration_getScreenRound(state->config) to the native-activity sample in ndk-samples.
Maybe I didn't link some library? I looked at the symbols in all of the lib*.so in the ndk and I didn't see a symbol for AConfiguration_getScreenRound either (but I see symbols for AConfiguration_getScreenLong). So I don't think I'm forgetting to link something.
Maybe if you too can't get it working, then AConfiguration_getScreenRound should be behind a cargo feature?
Or am I missing something really obvious?
The text was updated successfully, but these errors were encountered:
Hey there! thanks for this library!
I ran into this issue, possibly related to my build process, when I build some code using
android_ndk
. When I addandroid_ndk
My.so
file now has the symbolAConfiguration_getScreenRound.
Which makes sense because you create the bindings for android/configuration. But Android can't seem to find the thing to link it to!I also get this issue when adding
AConfiguration_getScreenRound(state->config)
to the native-activity sample in ndk-samples.Maybe I didn't link some library? I looked at the symbols in all of the lib*.so in the ndk and I didn't see a symbol for
AConfiguration_getScreenRound
either (but I see symbols forAConfiguration_getScreenLong
). So I don't think I'm forgetting to link something.Maybe if you too can't get it working, then
AConfiguration_getScreenRound
should be behind a cargo feature?Or am I missing something really obvious?
The text was updated successfully, but these errors were encountered: