-
Notifications
You must be signed in to change notification settings - Fork 265
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
Add Android testing setup #912
Comments
Interim reportThe main problem is that the include and library paths are hardcoded in the CMakeLists.txt: fluidsynth/test-android/app/src/main/cpp/CMakeLists.txt Lines 66 to 70 in 92089e0
When we build in Azure, the paths are different. To circumvent this, we could use the build-scripts in test-android/build-scripts/. Although this would work, it would still mean to have hard-coded paths and increased maintenance effort, as they always need to be kept in sync with the rest of the build. Instead, I would like to integrate the android CMake part into our main CMake build system. I've already started this on the I'll keep working on this from time to time. But it will take some... |
context: #875 (comment) / #897 (comment)
Current Android build setup on Azure DevOps misses testing on Android:
fluidsynth/.azure/azure-pipelines-android.yml
Line 586 in f81caf3
Since the tests that are based on ctest are not simply runnable on Android, we first have to convert existing tests into runnable style in Android manner. A dedicated test runner application would suffice.
As commented on the issue linked above, I came up with such a solution (test generator + runnable setup). A PR will follow and be linked here. So far it lacks the actual Azure DevOps setup, but having a locally runnable test app would be a good starter.
The text was updated successfully, but these errors were encountered: