bazelbuild / bazelbuild/rules_java

Windows: statically link msvcrt into Java Tools

未关闭
#316 0 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看
P4
主要语言
Starlark
星标
103
派生
102
PR 合并指标
30 天内没有已合并 PR

描述

Hi!

On Windows, the prebuilt tools in `remote_java_tools_windows` require the Microsoft VC++ Redistributable, for example:
```
external\rules_java++toolchains+remote_java_tools_windows\java_tools\ijar\ijar.exe
external\rules_java++toolchains+remote_java_tools_windows\java_tools\src\tools\singlejar\singlejar_local.exe
external\rules_java++toolchains+remote_java_tools_windows\java_tools\turbine_direct_graal.exe
```

Without the redist installed, these fail due to missing `msvcp140.dll`, `vcruntime140.dll`, `vcruntime140_1.dll` (exit code `-1073741515`).

Would it be possible link the MSVC runtime statically (i.e., `--features=static_link_msvcrt`) for these binaries, or ship the required VC++ runtime DLLs app‑local alongside the executables?

Related issue: https://github.com/bazelbuild/bazel/issues/8328.

贡献指南

打开贡献指南

调研方向

Start by examining how the Windows binaries under remote_java_tools_windows are produced, especially ijar.exe, singlejar_local.exe, and turbine_direct_graal.exe. Reproduce the failure on a Windows machine without the Microsoft VC++ Redistributable, then verify that the chosen packaging or linking change lets all three tools run without those missing DLLs.

由索引模型根据 Issue 内容生成。

评估

技术栈
java
领域
build-system
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。