mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-13 05:40:42 +01:00
![]() This adds Perfetto support to WebRTC with a GN flag rtc_use_perfetto. The configuration of perfetto depends on whether or not webrtc is build within Chrome or not. When in Chrome, WebRTC will depend on //third_party/perfetto:libperfetto. When building standalone, specific includes required for Perfetto are exposed with the library webrtc_libperfetto. The perfetto trace API is exposed with a header export in trace_event.h which is used instead of the legacy API. The addition of Perfetto means there are 4 compilation modes for tracing in WebRTC, 1. No tracing implementation. 2. Legacy tracing (AddTraceEvent/GetCategoryEnabled). 3.a. Perfetto statically linked (webrtc_libperfetto). 3.b. Perfetto in Chrome (Chrome's libperfetto). This CL removes the tracing expectations from rtc_stats_integrationtest.cc because those directly used the old API. Integration into Chrome is a follow up CL which depends on https://chromium-review.googlesource.com/c/chromium/src/+/5471691. Tested: Ran Chrome with Perfetto and traces appear. WebRTC Unit test tracing working: https://ui.perfetto.dev/#!?s=04ea2613ea36b814394639a1ec4b60be5b5097527f1a485995ecc13469885468 Bug: webrtc:15917 Change-Id: I537d79dc247c2b759689910c621087286a4d8fdc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/347880 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Auto-Submit: Evan Shrubsole <eshr@google.com> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/main@{#42166} |
||
---|---|---|
.. | ||
docs | ||
mb | ||
mb.bat | ||
mb.py | ||
mb_config.pyl | ||
mb_unittest.py | ||
OWNERS | ||
PRESUBMIT.py | ||
README.md |
MB - The Meta-Build wrapper
MB is a simple wrapper intended to provide a uniform interface to either GYP or GN, such that users and bots can call one script and not need to worry about whether a given bot is meant to use GN or GYP.
It supports two main functions:
-
"gen" - the main
gyp_chromium
/gn gen
invocation that generates the Ninja files needed for the build. -
"analyze" - the step that takes a list of modified files and a list of desired targets and reports which targets will need to be rebuilt.
We also use MB as a forcing function to collect all of the different
build configurations that we actually support for Chromium builds into
one place, in //tools/mb/mb_config.pyl
.
For more information, see: