Specify /CETCOMPAT in Bazel Windows build
#1164
Merged
+5
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Win32 x64/x86 executables built with GYP are already declared to be Intel CET compatible (google#835). With this commit those executables built with Bazel also become Intel CET compatible. Closes google#1113.
|
We have merged your PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Win32 x64/x86 executables built with GYP are already declared to be Intel CET compatible (#835).
With this commit those executables built with Bazel also become Intel CET compatible.
Closes #1113.
Issue IDs
/CETCOMPATlinker option is not set in Bazel build #1113Steps to test new behaviors (if any)
Mozc64.msiwith Bazel.Mozc64.msidumpbin /HEADERS mozc_tip64.dll | findstr compatible-> ConfirmCET compatibledumpbin /HEADERS mozc_server.exe | findstr compatible-> ConfirmCET compatible