base: don't enable DCHECKs in SDK builds

Until now DCHECKs were linked to the NDEBUG
symbols. This CL restricts this to: (1) standalone;
(2) chromium-tree; (3) android-tree builds.
In all other cases (in particular, for SDK/amalgamated
builds) DCHECKs are off by default, regardless of NDEBUG.
The old behavior turned out to be problematic for amalgamated
SDK users for two reasons:
1. Some of them reportedly build perfetto.cc once as
   a static library and then build perfetto.h as part
   of various .so(s). The NDEBUG flag might not match
   in all cases.
2. In general when projects that embed perfetto build in
   debug mode, they likely want to debug their own code,
   not perfetto's.

Bug: 197340286
Change-Id: Idcc94b300715c88fb578b679fb1d54f354c54adb
6 files changed
tree: 9d2ecb0686a142edad35d56467b1e470debe6c9b
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. src/
  13. test/
  14. tools/
  15. ui/
  16. .clang-format
  17. .clang-tidy
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .style.yapf
  22. Android.bp
  23. Android.bp.extras
  24. BUILD
  25. BUILD.extras
  26. BUILD.gn
  27. CHANGELOG
  28. codereview.settings
  29. DIR_METADATA
  30. heapprofd.rc
  31. LICENSE
  32. meson.build
  33. METADATA
  34. MODULE_LICENSE_APACHE2
  35. OWNERS
  36. perfetto.rc
  37. PerfettoIntegrationTests.xml
  38. PRESUBMIT.py
  39. README.chromium
  40. README.md
  41. TEST_MAPPING
  42. traced_perf.rc
  43. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.