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
Gradle/AGP brings in inconsistent builds which prevents androidaudioplugin-manager.aar from MavenLocal #174
Comments
I have created a reverting branch that uses Gradle 7.6 and AGP 7.4.2, and the problem still persists. There are workaround builds that resolves aap-core and aap-lv2 modules from git submodules, and they successfully builds. But aap-lv2-mda on GitHub Actions (e.g. this), unlike local builds on Android Studio, resulted in missing |
The same workaround is added in We keep this issue open until then. |
The MavenLocal problem also seems to affect the new realtime preset setter implementation. It works well if androidaudioplugin-manager is resolved via |
When I tried to build the release version 0.2.8 (with aap-core 0.7.8, both without Gradle and/or AGP with NDK support is such a wild field. Fortunately, aap-lv2-mda effect plugins generate valid audio outputs from those MavenLocal .aars this time, I decided to go with MavenLocal for this release. The same issue would come back at any time so I leave this issue open. |
…heme. regarding build structure changes (going back to MavenLocal), see: atsushieno/aap-core#174 (comment)
Actually the observation ^ was wrong, the audio resource resolution failure issue that occurs only with MavenLocal was never gone. We have to revert the change and find some viable solution (but how?? I have no idea at all). |
…ution scheme." This reverts commit aa5d7cb. context: atsushieno/aap-core#174 (comment)
It also prevents aap-lv2 package releases because Maven |
Now the same problem occurs in aap-juce apps. Sigh. |
…e issue. Gradle/AGP context: atsushieno/aap-core#174 (comment)
This also affects |
JavaCPP is a maintained native-interop technology that we can resort to in 2023. Due to weird build breakage on Maven package solution, rtmidi-javacpp is submoduled and referenced as a local project module. (I guess it is equivalent to atsushieno/aap-core#174)
After facing the same issue at ktmidi, I figured that it's not going to work because we cannot "publish" the dependency modules. Either we need to figure out how to exclude them or we need to fix this issue. |
JavaCPP is a maintained native-interop technology that we can resort to in 2023. Due to weird build breakage on Maven package solution, rtmidi-javacpp is submoduled and referenced as a local project module. (I guess it is equivalent to atsushieno/aap-core#174)
See if atsushieno/aap-core#174 is finally gone.
I have bumped Gradle to 8.5 and AGP to 8.2.2, and the problem still persists. |
Same for Gradle 8.6-rc1 and AGP 8.4.0-alpha07. |
Comparing
Since they are already different at
|
Here are what I found so far:
|
We can go without |
context: #174 Before we decide to "disable NDEBUG" (removing -DNDEBUG from cmake options) we should make sure that it is not our end that those removed assertions were the cause of the issues.
from #172 (comment):
The text was updated successfully, but these errors were encountered: