commit | 6933b7349b5d9ea1a51ee6f13144066183043d76 | [log] [tgz] |
---|---|---|
author | Tom de Goede <tom.degoede@afas.nl> | Fri May 08 06:31:01 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri May 08 06:32:09 2020 -0700 |
tree | a6142dc78c3f01a8470160dc70b869cc3d07b303 | |
parent | 4a997745eede9fb66d46d1f5e65fd1df26793a13 [diff] |
Allow bazel run on windows to handle Ctrl+C signals Currently bazel run on windows prevents the process it's running from receiving Ctrl+C events. This is because the windows implementation (unlike posix execv) runs the target as a subprocess of the bazel cli maintaining it's Ctrl+C interceptor which tries to interrupt the (no longer running) server instead of the spawned process (three times and then kills). Not specifying CREATE_NEW_PROCESS_GROUP during CreateProcessW for this case resolves that issue. Potentially a de-register of the bazel cli Ctrl+C handler is desired since it still prints "Bazel Ctrl+C handler; shutting down.". Closes #11144. PiperOrigin-RevId: 310547476
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md