toolchain_aarch64-linux-android does not have mandatory providers: 'TemplateVariableInfo' when build android command line programs

[Ice3Inch]

I'm building an android command line executable which could be run on Android arm64 platform with bazel 8.0 bzlmod method.
But I met below errors with build command "bazelisk-windows-amd64.exe build //native_hello:native_hello --platforms=//build:android_arm64_platform --verbose_failures"

ERROR: D:/bazel/bazel_android_native_demos/native_hello/BUILD:1:10: in toolchains attribute of cc_binary rule //native_hello:native_hello: '@@rules_android_ndk++android_ndk_repository_extension+androidndk//:toolchain_aarch64-linux-android' does not have mandatory providers: 'TemplateVariableInfo'
ERROR: D:/bazel/bazel_android_native_demos/native_hello/BUILD:1:10: Analysis of target '//native_hello:native_hello' failed
ERROR: Analysis of target '//native_hello:native_hello' failed; build aborted
INFO: Elapsed time: 18.648s, Critical Path: 0.15s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully

Are there any compatible issues with cc_binary and bzlmod?
I have searched Google and asked AI tools, but still have no clue.
Please help take a look at this issue.

---

My test project structure is as following

bazel_android_native_demos
- build/BUILD
- native_hello/
	-- BUILD
	-- main.cpp
- MODULE.bazel

Contents of MODULE.bazel

module(
    name = "bazel_android_native_demos",
    version = "1.0",
)

bazel_dep(name = "rules_cc", version = "0.1.0")
bazel_dep(name = "platforms", version = "0.0.10")
bazel_dep(name = "rules_android_ndk", version = "0.1.3")

android_ndk_repository_extension = use_extension(
    "@rules_android_ndk//:extension.bzl",
    "android_ndk_repository_extension",
)

android_ndk_repository_extension.configure(
    path = "C:/Users/Ice3Inch/AppData/Local/Android/Sdk/ndk/25.1.8937393",
    api_level = 21,
)

use_repo(android_ndk_repository_extension, "androidndk")

register_toolchains("@androidndk//:all")

Contents of native_hello/BUILD

cc_binary(
    name = "native_hello",
    srcs = ["main.cpp"],
    linkopts = [
        "-llog",
    ],
    toolchains = [
        "@androidndk//:toolchain_aarch64-linux-android",  
    ],
    target_compatible_with = [
        "@platforms//cpu:arm64",
        "@platforms//os:android",
    ],
    visibility = ["//visibility:public"],
)

Contents of native_hello/main.cpp

#include <android/log.h>

int main(int argc, char** argv) {
    __android_log_print(ANDROID_LOG_INFO, "NativeHello", "Hello from native code!");
    return 0;
}

Contents of build/BUILD

package(default_visibility = ["//visibility:public"])

platform(
    name = "android_arm64_platform",
    constraint_values = [
        "@platforms//cpu:arm64",
        "@platforms//os:android",
    ],
)

[ted-xie]

It looks like you're trying to use Windows with a Linux toolchain, which seems incorrect. It also looks like you're trying to build a cc_binary rather than cc_library + android_binary, which is what rules_android_ndk was designed to do.

[Ice3Inch]

It looks like you're trying to use Windows with a Linux toolchain, which seems incorrect. It also looks like you're trying to build a cc_binary rather than cc_library + android_binary, which is what rules_android_ndk was designed to do.

Thanks for your reply.
I'm trying to cross build a android aarch64 executable binary on Windows host.
The program is written in pure C++ based on android NDK prebuilt native libraries, this why I'm using cc_binary rather than cc_library + android_binary. I don't need the Java parts.

from rules_android_ndk, I could query 4 toolchains available

bazelisk-windows-amd64.exe query @androidndk//:all
Starting local Bazel server (8.0.1) and connecting to it...
@androidndk//:cpufeatures
@androidndk//:native_app_glue
@androidndk//:toolchain
@androidndk//:toolchain_aarch64-linux-android
@androidndk//:toolchain_arm-linux-androideabi
@androidndk//:toolchain_i686-linux-android
@androidndk//:toolchain_x86_64-linux-android

My original understanding was that aarch64_linux-android refers to the target platform, and 'linux' string in it might not have actual significance, am I right?

I printed the CcToolchainConfigInfo.proto in function ndk_cc_toolchain_config_rule_implementation.
The tool_paths seem right.

host_system_name: ""
target_system_name: "aarch64-linux-android"
target_cpu: "arm64-v8a"
target_libc: "bionic"
compiler: "llvm-c++"
abi_version: "aarch64-linux-android"
abi_libc_version: "18"
tool_path {
name: "clang"
path: "bin/clang.exe"
}
tool_path {
name: "ar"
path: "bin/llvm-ar.exe"
}
tool_path {
name: "cpp"
path: "bin/clang++.exe"
}
tool_path {
name: "dwp"
path: "bin/llvm-dwp.exe"
}
tool_path {
name: "gcc"
path: "bin/clang.exe"
}
tool_path {
name: "gcov"
path: "bin/gcov.exe"
}
tool_path {
name: "ld"
path: "bin/ld.exe"
}
tool_path {
name: "nm"
path: "bin/llvm-nm.exe"
}
tool_path {
name: "objcopy"
path: "bin/llvm-objcopy.exe"
}
tool_path {
name: "objdump"
path: "bin/llvm-objdump.exe"
}
tool_path {
name: "strip"
path: "bin/llvm-strip.exe"
}
cxx_builtin_include_directory: "sysroot/usr/include/c++/v1"
cxx_builtin_include_directory: "sysroot/usr/local/include"
cxx_builtin_include_directory: "lib64/clang/14.0.6"
cxx_builtin_include_directory: "sysroot/usr/include/aarch64-linux-android"
cxx_builtin_include_directory: "sysroot/usr/include"