Reword 'how to depend on Abseil' section No-Try: true Bug: b/496863306 Change-Id: I838f224b39b41a12f81e029eb37463ed2861fff1 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/461580 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Auto-Submit: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/main@{#47321}
diff --git a/g3doc/abseil-in-webrtc.md b/g3doc/abseil-in-webrtc.md index 7a2f8de..ee790f3 100644 --- a/g3doc/abseil-in-webrtc.md +++ b/g3doc/abseil-in-webrtc.md
@@ -1,5 +1,5 @@ <!-- go/cmark --> -<!--* freshness: {owner: 'danilchap' reviewed: '2025-09-24'} *--> +<!--* freshness: {owner: 'danilchap' reviewed: '2026-04-02'} *--> # Using Abseil in WebRTC @@ -15,12 +15,13 @@ ## How to depend on Abseil -For build targets of type `rtc_library`, `rtc_source_set` and -`rtc_static_library`, dependencies on Abseil need to be listed in `deps`. +Dependencies on Abseil need to be listed in `deps` using absolute path, +for example `"//third_party/abseil-cpp/absl/base:core_headers"` -The GN templates will take care of generating the proper dependency when -used within Chromium or standalone. In that build mode, WebRTC will depend -on a monolithic Abseil build target that will generate a shared library. +The rtc GN templates will take care of generating the proper dependency when +used within Chromium or standalone. In the `build_with_chromium` mode, WebRTC +will depend on the monolithic Abseil build target that will generate a shared +library. ## **Allowed**