v6.0.0 fails to build

[IzzySoft]

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:configureCMakeRelWithDebInfo[arm64-v8a]'.
> [CXX1300] CMake '4.1.2' was not found in SDK, PATH, or by cmake.dir property.

cmdline_tools 19 support max 4.0.2. Debian trixie has 3.31.6-2 – Ubuntu noble 3.28.3-1build7, so we cannot build the app. Which means, this version will get a yellow shield (RB failed). Could you please switch to a supported version with the next release – or is there anything you need which those do not support?

Here's what sdkmanager --list gives for cmdline_tools 19:

  cmake;3.10.2.4988404          | 3.10.2            | CMake 3.10.2.4988404
  cmake;3.18.1                  | 3.18.1            | CMake 3.18.1
  cmake;3.22.1                  | 3.22.1            | CMake 3.22.1
  cmake;3.30.3                  | 3.30.3            | CMake 3.30.3
  cmake;3.30.4                  | 3.30.4            | CMake 3.30.4
  cmake;3.30.5                  | 3.30.5            | CMake 3.30.5
  cmake;3.31.0                  | 3.31.0            | CMake 3.31.0
  cmake;3.31.1                  | 3.31.1            | CMake 3.31.1
  cmake;3.31.4                  | 3.31.4            | CMake 3.31.4
  cmake;3.31.5                  | 3.31.5            | CMake 3.31.5
  cmake;3.31.6                  | 3.31.6            | CMake 3.31.6
  cmake;3.6.4111459             | 3.6.4111459       | CMake 3.6.4111459
  cmake;4.0.2                   | 4.0.2             | CMake 4.0.2

[patzly]

No I don't need any specific features, just wanted to be on the newest updates. So which version do I have to use exactly now?

[IzzySoft]

Which one did you use with the last release, as that worked fine here? Otherwise, any of above list should do, as they are supported by sdkmanager with cmdline_tools 19 (which is the currently latest version of cmdline_tools).

[patzly]

Okay thanks! In previous versions I didn't use any native code, it's new in this version because I needed low-latency audio.

[patzly]

I downgraded to 4.0.2, hope this solves the problem for the next minor version I will hopefully release very soon.

[tippfehlr]

Is this supposed to be strict? I cannot build it with cmake 4.1.2 now:

[CXX1300] CMake '4.0.2' was not found in SDK, PATH, or by cmake.dir property.

It works when I downgrade cmake to 4.0.2

[IzzySoft]

I'm no Android dev, so I cannot tell that in depth, sorry. But if you define a specific cmake version, that must be available (or gradle must make it available). And for RB to succeed, AFAIK we both must use the same version.

[patzly]

Is this supposed to be strict? I cannot build it with cmake 4.1.2 now:

[CXX1300] CMake '4.0.2' was not found in SDK, PATH, or by cmake.dir property.

It works when I downgrade cmake to 4.0.2

Maybe I can remove the specific version in build.gradle to be version-unspecific.

[IzzySoft]

Maybe. But if then you use a different version as we do, RB is prone to fail – so nothing really won. Just "to be on the newest updates" is not always the best, "the latest supported version" however commendable 😉 Which then, currently, would be 4.0.2, as shown.

[IzzySoft]

Hm, I was afraid of something like that. Native libs often require to match build path; so while I could successfully build v6.0.1 now by giving it cmake 4.0.2, it was not RB: diff.zip

We can give this another try, if you can let me know the exact path you've checked the repo out to, to build from /e.g. /home/patzly/github/tack-android), so I can tell our builder to match this. Chances are this might do the trick.

[patzly]

I think I managed it, diff shows no output for me now! Do I have to make a new version for it to take effect?

[IzzySoft]

That sounds great! 🤗 As the APK has already been distributed via our repo: yes, we'd need a new release (and the APK must have its versionCode increased for that). Do you want me to run a check beforehand, to make sure? I'd just need the APK and the commit it was built from then. And also what I'd need to adjust for our build – like the build path, for example.

[IzzySoft]

For now, we've had to the the "RB failed" pass again, as the 24h window has passed, sorry. But with some luck, the next release will solve this – you sound like you might have nailed the culprit though I do not now details 🤞