Convert DISABLE_NACL macro to a buildflag header.
This way, DISABLE_NACL isn't defined globally, but only where
it's needed (chrome, some extensions, some content/). This also means
toggling nacl on and off doesn't require rebuilding the world (in
particular, blink. On my linux build, toggling the flag now reruns
697 build steps, compared to 56274 before). It also gets rid of a ton
of confusing `if !DISABLED` double negation.
No intended behavior change.
Bug: none
Change-Id: Iaad97b4590524a15f7be8565d5722cb2b1b81845
Reviewed-on: https://chromium-review.googlesource.com/659241
Reviewed-by: Brett Wilson <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Commit-Queue: Daniel Cheng <[email protected]>
Cr-Commit-Position: refs/heads/master@{#500971}diff --git a/chrome/browser/flag_descriptions.cc b/chrome/browser/flag_descriptions.cc
index 080538c..16683da 100644
--- a/chrome/browser/flag_descriptions.cc
+++ b/chrome/browser/flag_descriptions.cc
@@ -2623,7 +2623,7 @@
#endif // ENABLE_VR
-#if !defined(DISABLE_NACL)
+#if BUILDFLAG(ENABLE_NACL)
const char kNaclDebugMaskName[] =
"Restrict Native Client GDB-based debugging by pattern";
@@ -2651,7 +2651,7 @@
const char kPnaclSubzeroDescription[] =
"Force the use of PNaCl's fast Subzero translator for all pexe files.";
-#endif // !defined(DISABLE_NACL)
+#endif // BUILDFLAG(ENABLE_NACL)
#if BUILDFLAG(ENABLE_WEBRTC)
