-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows and Android Studio - issue with libgg.so and libxp.so #29
Comments
Side note: On Linux it is the same issue. I had the hope it is a Windows issue initially. Build command failed. ninja: error: '../../../../../../../../xp/build/cmake/android/armeabi-v7a/libgg.so', needed by '../../../../build/intermediates/cmake/debug/obj/armeabi-v7a/libxp.so', missing and no known rule to make it |
Having the same issue on MacOS with Android Studio 4.2 |
It was able to solve my issues above. The Android documentation lacks the hint that the library libgg.so must be compiled externally and cannot be compiled (as expected) by the Android NDK and Android Studio itself. Therefore, one is required to follow the "getting started"-guide and setup the build system on the host along with inv, conda, python etc. to be able to run "inv android.build", which compiles the required libgg.so |
Yes, sorry about that. I will update the documentation to avoid the confusion in the future. |
Hi development team,
I'm unsure if my issue is related to the missing support of Windows. Nevertheless, I'd like to notify you about it.
After downloading the project and importing it to Android Studio for APK compilation, I received the following error about a missing library:
Task :GoldenGateBindings:externalNativeBuildDebug FAILED
Build xp_x86
ninja: Entering directory `C:\tmp\gg\golden-gate\platform\android\goldengate\GoldenGateBindings.cxx\cmake\debug\x86'
ninja: error: '../../../../../../../../xp/build/cmake/android/x86/libgg.so', needed by '../../../../build/intermediates/cmake/debug/obj/x86/libxp.so', missing and no known rule to make it
Any idea on how to fix that?
The text was updated successfully, but these errors were encountered: