aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/launcher
Commit message (Collapse)AuthorAge
* Clean up Windows config_settingsGravatar Yun Peng2018-01-12
| | | | | | | | | | | | | | 1.Deleted config_setting for --cpu=x64_windows_msys, because we don't build Bazel with MSYS gcc anymore. 2.Deleted config_setting for --cpu=x64_windows_msvc, because it uses exactly the same toolchain as --cpu=x64_windows, it'll be removed in the future. This change reduces the complexity of our BUILD files and make them less confusing. Change-Id: I939831a6861413b0f745fb1be98aacd4fb780e0a PiperOrigin-RevId: 181751853
* Move bazel conditions into src/conditions.Gravatar tomlu2017-11-30
| | | | | | | This will enable an easier transition from checked-in BUILD files to ones generated by copybara. RELNOTES: None PiperOrigin-RevId: 177514519
* Enable switching launcher's Windows target for remote execution.Gravatar xingao2017-10-06
| | | | | | | When --define EXECUTOR=remote is specified in bazel command, embedded tools 'launcher' will be compiled remotely from source. PiperOrigin-RevId: 171172084
* Apply native binary launcher to sh_binaryGravatar Yun Peng2017-07-31
This change: 1. Added launcher to @bazel_tools If the host platform is Windows, we use a prebuilt launcher.exe , otherwise the launcher needs to be built with MSVC first. 2. Launching sh_binary using native launcher. Change-Id: I5a63135455057fbfe04ff0cce7ec7994ef0c347a PiperOrigin-RevId: 163442540
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-19 20:14:37 +0000