forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Mojo: separate generation of MojoLPM and JS fuzzing bindings.
This CL replaces the enable_fuzzing mojom buildrule parameter with two flags, enable_js_fuzzing and enable_mojolpm_fuzzing, which allow independently controlling the generation of the MojoLPM and JS fuzzing bindings. This means that MojoLPM fuzzers don't need to require the generation of legacy JS bindings, and allows cleaning up some of the WebUI and ChromeOS specific interfaces which currently need to generate unused legacy bindings. Bug: 1413182 Change-Id: I426f40a96c8ba15898c78a30d235d26e0c23fc4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4225396 Reviewed-by: Rebekah Potter <rbpotter@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Reviewed-by: Jack Hsieh <chengweih@chromium.org> Reviewed-by: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Reviewed-by: Austin Sullivan <asully@chromium.org> Commit-Queue: Mark Brand <markbrand@google.com> Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Reviewed-by: Roland Bock <rbock@google.com> Cr-Commit-Position: refs/heads/main@{#1111488}
- Loading branch information
Showing
9 changed files
with
50 additions
and
38 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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