Description of the problem / feature requests
I am trying to build a c++ library using bazel under windows. I am using the following command:
bazel build <target> --compilation_mode=opt --crosstool_top=@androidndk//:default_crosstool --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --cpu=armeabi-v7a
I am getting the following error message:
Action failed to execute: java.io.IOException: ERROR: src/main/native/windows/processes-jni.cc(429): CreateProcessWithExplicitHandles("<user>\_bazel_exb_a\kkszmrzt\execroot\dbsdk\external\androidndk\ndk\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64\bin\arm-linux-androideabi-ar" rcsD bazel-out/armeabi-v7a-(...)): command is longer than CreateProcessW's limit (32767 characters)
Unlike Linux/windows build that are using a linker input file for commands the ndk version passes all parameters via command line
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
- create a cc_binary for android
- add as much as possible files to exceed 32K of characters in command line
- see failing build
What operating system are you running Bazel on?
What's the output of bazel info release?
Have you found anything relevant by searching the web?
Description of the problem / feature requests
I am trying to build a c++ library using bazel under windows. I am using the following command:
bazel build <target> --compilation_mode=opt --crosstool_top=@androidndk//:default_crosstool --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --cpu=armeabi-v7aI am getting the following error message:
Action failed to execute: java.io.IOException: ERROR: src/main/native/windows/processes-jni.cc(429): CreateProcessWithExplicitHandles("<user>\_bazel_exb_a\kkszmrzt\execroot\dbsdk\external\androidndk\ndk\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64\bin\arm-linux-androideabi-ar" rcsD bazel-out/armeabi-v7a-(...)): command is longer than CreateProcessW's limit (32767 characters)Unlike Linux/windows build that are using a linker input file for commands the ndk version passes all parameters via command line
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
What's the output of
bazel info release?Have you found anything relevant by searching the web?