You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like #2722 is somehow back in bazel v5.0.0.
Was not happening for me on bazel v4.x.x.
In a macro file included from my WORKSPACE I have the following defines (without loss of generality):
native.android_sdk_repository(
name = "androidsdk",
api_level = 28,
build_tools_version = "30.0.3",
)
native.android_ndk_repository(
name = "androidndk",
api_level = 29,
)
No special flags on the command line (no extra_toolchains, crosstool_top, cpu or such).
And yet, the outcome is build failing:
bazel build -s my-target
ERROR:WORKSPACE:37:8: fetching android_ndk_repository rule //external:androidndk: Either the path attribute of android_ndk_repository or the ANDROID_NDK_HOME environment variable must be set.
ERROR: Analysis of target '//my-target' failed; build aborted: Either the path attribute of android_ndk_repository or the ANDROID_NDK_HOME environment variable must be set.
INFO: Elapsed time: 0.081s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 0 targets conf
igured)
Fetching @go_sdk; fetching
Fetching @local_jdk; Restarting.
The text was updated successfully, but these errors were encountered:
Seems like #2722 is somehow back in bazel v5.0.0.
Was not happening for me on bazel v4.x.x.
In a macro file included from my WORKSPACE I have the following defines (without loss of generality):
No special flags on the command line (no extra_toolchains, crosstool_top, cpu or such).
And yet, the outcome is build failing:
The text was updated successfully, but these errors were encountered: