Introduce a stub bazel wrapper for Windows #1201
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a preparation before starting using
clang-cl
to build Mozc for for Windows with Bazel (#1179).In order to make the build process reliable and reproducible, we would like to download a specific version of LLVM with
update_deps.py
then deploy it underthird_party/llvm/
and letrules_cc
use it by specifyingBAZEL_LLVM
environment variable.To automate this process, one idea is to use
tools/bazel
wrapper script.Luckily the wrapper script directory is also customizable since bazelisk v1.21.0.
With above this commit introduces a stub
bazel.bat
so that we can use it to set various environment variables for Windows bazel build in subsequent commits. At this moment there must be no difference in the final artifacts. There should be no impact on non-Windows bazel build asbazel.bat
is searched only on Windows.Issue IDs
clang-cl
to build Mozc for Windows with Bazel #1179Steps to test new behaviors (if any)
bazelisk --bazelrc=windows.bazelrc build package --config oss_windows --config release_build