Enable exception handing for built-in windows headers

INFO: From Executing genrule //src/main/native:windows_jni:

C:\tools\msys64\tmp\bazel_7uQBlyR9\out\execroot\bazel>call "C:/Program
Files (x86)/Microsoft Visual Studio 14.0/VC/VCVARSALL.BAT" amd64
windows_error_handling.cc
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\INCLUDE\xlocale(341): warning C4530: C++ exception handler used,
but unwind semantics are not enabled. Specify /EHsc
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\INCLUDE\exception(359): warning C4577: 'noexcept' used with no
exception handling mode specified; termination on exception is not
guaranteed. Specify /EHsc
windows_file_operations.cc
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\INCLUDE\xlocale(341): warning C4530: C++ exception handler used,
but unwind semantics are not enabled. Specify /EHsc
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\INCLUDE\exception(359): warning C4577: 'noexcept' used with no
exception handling mode specified; termination on exception is not
guaranteed. Specify /EHsc
windows_processes.cc
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\INCLUDE\xlocale(341): warning C4530: C++ exception handler used,
but unwind semantics are not enabled. Specify /EHsc
C:\Program Files (x86)\Microsoft Visual Studio
14.0\VC\INCLUDE\iosfwd(343): warning C4577: 'noexcept' used with no
exception handling mode specified; termination on exception is not
guaranteed. Specify /EHsc

--
Change-Id: I6f93a4dbb1be42fa5bea221402fb71a830960cf6
Reviewed-on: https://bazel-review.googlesource.com/#/c/6130
MOS_MIGRATED_REVID=135458066
1 file changed
tree: c330cd47f8e3e06900809fbc6ba3d28291dd0a4d
  1. examples/
  2. scripts/
  3. site/
  4. src/
  5. third_party/
  6. tools/
  7. .gitattributes
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CHANGELOG.md
  12. compile.sh
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. LICENSE.txt
  16. README.md
  17. WORKSPACE
README.md

Bazel (Beta)

{Fast, Correct} - Choose two

Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:

  • A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.

  • An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.

  • Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.

Find more background about Bazel in our FAQ.

Getting Started

About the Bazel project: