M1 Ninja

[DanAlbert]

Subtask for #1299

[DanAlbert]

(removing from the project because this isn't tied to an NDK release, it's in the SDK)

[enh-google]

did this go out in this week's Studio update?

[DanAlbert]

No, we were two weeks faster :) #1545 (comment)

It's still in canary, which is why the bugs remain open.

[rprichard]

The Android SDK's ninja binary is distributed as part of the cmake package.

[enh-google]

do we know (roughly?) the timeline when that'll go from canary to stable?

[DanAlbert]

We could ambitiously do that any time, but I think it'd be wise to flip the Studio default version before we do that. We don't have any way to know if it's been used by anyone but @rprichard yet.

[DanAlbert]

(I'm planning to move the Studio default Soon, once I'm done doing fixing their default NDK)

[enh-google]

sgtm. i'm just very confused this week about what "released" even means in Studio land :-)

[DanAlbert]

aiui cmake/ninja being in canary means that anyone can use it as long as they enable the canary channel. No updates there are forced so it's safe to do, but it'll recommend canary updates for other packages so it might be annoying. I think you can enable the canary channel, install cmake, then go back to stable though?

[rprichard]

I think you can enable the canary channel, install cmake, then go back to stable though?

I believe this is the case. It'll also be necessary to set the cmake version in gradle, e.g.:

    externalNativeBuild {
        cmake {
            path file('src/main/cpp/CMakeLists.txt')
            version '3.22.1'
        }
    }

[vmilea]

I'm planning to move the Studio default Soon

What will be the new default?

FWIW - I've been using CMake 3.22.1 from canary with NDK r23b and r24 RC1. No issues so far, and build times on my M1 mac have almost halved with the arm64 Clang. Thank you!