Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
# Copyright (c) 2016 The WebRTC project authors. All Rights Reserved.
|
|
|
|
|
#
|
|
|
|
|
# Use of this source code is governed by a BSD-style license
|
|
|
|
|
# that can be found in the LICENSE file in the root of the source
|
|
|
|
|
# tree. An additional intellectual property rights grant can be found
|
|
|
|
|
# in the file PATENTS. All contributing project authors may
|
|
|
|
|
# be found in the AUTHORS file in the root of the source tree.
|
|
|
|
|
|
2017-01-24 06:58:22 -08:00
|
|
|
import("../webrtc.gni")
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
import("//third_party/protobuf/proto_library.gni")
|
|
|
|
|
if (is_android) {
|
|
|
|
|
import("//build/config/android/config.gni")
|
|
|
|
|
import("//build/config/android/rules.gni")
|
|
|
|
|
}
|
|
|
|
|
|
2016-10-28 05:44:03 -07:00
|
|
|
group("logging") {
|
|
|
|
|
public_deps = [
|
|
|
|
|
":rtc_event_log_impl",
|
|
|
|
|
]
|
|
|
|
|
if (rtc_enable_protobuf) {
|
|
|
|
|
public_deps += [ ":rtc_event_log_parser" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
rtc_source_set("rtc_event_log_api") {
|
|
|
|
|
sources = [
|
2017-10-02 11:27:52 +02:00
|
|
|
"rtc_event_log/events/rtc_event.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_network_adaptation.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_network_adaptation.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_playout.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_playout.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_receive_stream_config.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_receive_stream_config.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_send_stream_config.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_audio_send_stream_config.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_bwe_update_delay_based.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_bwe_update_delay_based.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_bwe_update_loss_based.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_bwe_update_loss_based.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_logging_started.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_logging_started.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_logging_stopped.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_logging_stopped.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_probe_cluster_created.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_probe_cluster_created.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_probe_result_failure.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_probe_result_failure.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_probe_result_success.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_probe_result_success.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtcp_packet_incoming.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtcp_packet_incoming.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtcp_packet_outgoing.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtcp_packet_outgoing.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtp_packet_incoming.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtp_packet_incoming.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtp_packet_outgoing.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_rtp_packet_outgoing.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_video_receive_stream_config.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_video_receive_stream_config.h",
|
|
|
|
|
"rtc_event_log/events/rtc_event_video_send_stream_config.cc",
|
|
|
|
|
"rtc_event_log/events/rtc_event_video_send_stream_config.h",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
"rtc_event_log/rtc_event_log.h",
|
2017-06-15 12:52:32 -07:00
|
|
|
"rtc_event_log/rtc_event_log_factory_interface.h",
|
2017-09-11 07:25:26 -07:00
|
|
|
"rtc_event_log/rtc_stream_config.cc",
|
|
|
|
|
"rtc_event_log/rtc_stream_config.h",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
]
|
2017-03-08 02:12:11 -08:00
|
|
|
deps = [
|
2017-05-30 03:52:10 -07:00
|
|
|
"..:webrtc_common",
|
2017-09-29 21:01:42 +02:00
|
|
|
"../api:array_view",
|
2017-09-01 15:29:28 +02:00
|
|
|
"../api:libjingle_peerconnection_api",
|
2017-08-22 05:43:23 -07:00
|
|
|
"../call:video_stream_api",
|
2017-10-02 13:33:31 +02:00
|
|
|
"../modules/audio_coding:audio_network_adaptor_config",
|
|
|
|
|
"../modules/remote_bitrate_estimator:remote_bitrate_estimator",
|
|
|
|
|
"../modules/rtp_rtcp:rtp_rtcp_format",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:rtc_base_approved",
|
2017-03-08 02:12:11 -08:00
|
|
|
]
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
rtc_static_library("rtc_event_log_impl") {
|
|
|
|
|
sources = [
|
2017-10-03 15:01:03 +02:00
|
|
|
"rtc_event_log/encoder/rtc_event_log_encoder.h",
|
|
|
|
|
"rtc_event_log/encoder/rtc_event_log_encoder_legacy.cc",
|
|
|
|
|
"rtc_event_log/encoder/rtc_event_log_encoder_legacy.h",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
"rtc_event_log/rtc_event_log.cc",
|
2017-06-15 12:52:32 -07:00
|
|
|
"rtc_event_log/rtc_event_log_factory.cc",
|
|
|
|
|
"rtc_event_log/rtc_event_log_factory.h",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
defines = []
|
|
|
|
|
|
|
|
|
|
deps = [
|
|
|
|
|
":rtc_event_log_api",
|
|
|
|
|
"..:webrtc_common",
|
2017-01-24 04:54:59 -08:00
|
|
|
"../modules/audio_coding:audio_network_adaptor",
|
2017-04-11 00:49:44 -07:00
|
|
|
"../modules/remote_bitrate_estimator:remote_bitrate_estimator",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
"../modules/rtp_rtcp",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:protobuf_utils",
|
|
|
|
|
"../rtc_base:rtc_base_approved",
|
2017-09-06 05:18:15 -07:00
|
|
|
"../rtc_base:rtc_task_queue",
|
|
|
|
|
"../rtc_base:sequenced_task_checker",
|
2017-03-08 02:12:11 -08:00
|
|
|
"../system_wrappers",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
if (rtc_enable_protobuf) {
|
|
|
|
|
defines += [ "ENABLE_RTC_EVENT_LOG" ]
|
|
|
|
|
deps += [ ":rtc_event_log_proto" ]
|
|
|
|
|
}
|
2016-10-16 23:56:12 -07:00
|
|
|
if (!build_with_chromium && is_clang) {
|
|
|
|
|
# Suppress warnings from the Chromium Clang plugin (bugs.webrtc.org/163).
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
suppressed_configs += [ "//build/config/clang:find_bad_constructs" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (rtc_enable_protobuf) {
|
|
|
|
|
proto_library("rtc_event_log_proto") {
|
|
|
|
|
sources = [
|
|
|
|
|
"rtc_event_log/rtc_event_log.proto",
|
|
|
|
|
]
|
2017-09-15 06:47:31 +02:00
|
|
|
proto_out_dir = "logging/rtc_event_log"
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
rtc_static_library("rtc_event_log_parser") {
|
|
|
|
|
sources = [
|
|
|
|
|
"rtc_event_log/rtc_event_log_parser.cc",
|
|
|
|
|
"rtc_event_log/rtc_event_log_parser.h",
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
public_deps = [
|
2017-03-08 02:12:11 -08:00
|
|
|
":rtc_event_log_api",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
":rtc_event_log_proto",
|
|
|
|
|
"..:webrtc_common",
|
2017-04-06 05:59:10 -07:00
|
|
|
"../modules/audio_coding:audio_network_adaptor",
|
2017-04-11 00:49:44 -07:00
|
|
|
"../modules/remote_bitrate_estimator:remote_bitrate_estimator",
|
2017-03-08 02:12:11 -08:00
|
|
|
"../modules/rtp_rtcp:rtp_rtcp",
|
|
|
|
|
"../system_wrappers",
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
]
|
|
|
|
|
|
2016-10-16 23:56:12 -07:00
|
|
|
if (!build_with_chromium && is_clang) {
|
|
|
|
|
# Suppress warnings from the Chromium Clang plugin (bugs.webrtc.org/163).
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
suppressed_configs += [ "//build/config/clang:find_bad_constructs" ]
|
|
|
|
|
}
|
2017-03-08 02:12:11 -08:00
|
|
|
deps = [
|
2017-08-22 05:43:23 -07:00
|
|
|
"../call:video_stream_api",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:protobuf_utils",
|
|
|
|
|
"../rtc_base:rtc_base_approved",
|
2017-03-08 02:12:11 -08:00
|
|
|
]
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
}
|
2017-01-17 02:37:34 -08:00
|
|
|
|
|
|
|
|
if (rtc_include_tests) {
|
|
|
|
|
rtc_source_set("rtc_event_log_tests") {
|
|
|
|
|
testonly = true
|
2017-10-03 15:01:03 +02:00
|
|
|
assert(rtc_enable_protobuf)
|
|
|
|
|
defines = [ "ENABLE_RTC_EVENT_LOG" ]
|
2017-01-17 02:37:34 -08:00
|
|
|
sources = [
|
2017-10-03 15:01:03 +02:00
|
|
|
"rtc_event_log/encoder/rtc_event_log_encoder_unittest.cc",
|
2017-01-17 02:37:34 -08:00
|
|
|
"rtc_event_log/rtc_event_log_unittest.cc",
|
|
|
|
|
"rtc_event_log/rtc_event_log_unittest_helper.cc",
|
2017-08-17 08:32:39 -07:00
|
|
|
"rtc_event_log/rtc_event_log_unittest_helper.h",
|
2017-01-17 02:37:34 -08:00
|
|
|
]
|
|
|
|
|
deps = [
|
|
|
|
|
":rtc_event_log_impl",
|
|
|
|
|
":rtc_event_log_parser",
|
|
|
|
|
"../call",
|
2017-04-06 05:59:10 -07:00
|
|
|
"../modules/audio_coding:audio_network_adaptor",
|
2017-04-11 00:49:44 -07:00
|
|
|
"../modules/remote_bitrate_estimator:remote_bitrate_estimator",
|
2017-01-17 02:37:34 -08:00
|
|
|
"../modules/rtp_rtcp",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:rtc_base_approved",
|
|
|
|
|
"../rtc_base:rtc_base_tests_utils",
|
2017-01-17 02:37:34 -08:00
|
|
|
"../system_wrappers:metrics_default",
|
2017-03-08 02:12:11 -08:00
|
|
|
"../test:test_support",
|
2017-01-17 02:37:34 -08:00
|
|
|
"//testing/gmock",
|
|
|
|
|
"//testing/gtest",
|
|
|
|
|
]
|
|
|
|
|
if (!build_with_chromium && is_clang) {
|
|
|
|
|
# Suppress warnings from the Chromium Clang plugin (bugs.webrtc.org/163).
|
|
|
|
|
suppressed_configs += [ "//build/config/clang:find_bad_constructs" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
2017-02-08 00:28:09 -08:00
|
|
|
rtc_test("rtc_event_log2rtp_dump") {
|
|
|
|
|
testonly = true
|
|
|
|
|
sources = [
|
|
|
|
|
"rtc_event_log/rtc_event_log2rtp_dump.cc",
|
|
|
|
|
]
|
|
|
|
|
deps = [
|
|
|
|
|
":rtc_event_log_api",
|
|
|
|
|
":rtc_event_log_impl",
|
|
|
|
|
":rtc_event_log_parser",
|
|
|
|
|
"../modules/rtp_rtcp:rtp_rtcp",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:rtc_base_approved",
|
2017-02-08 00:28:09 -08:00
|
|
|
"../system_wrappers:field_trial_default",
|
|
|
|
|
"../system_wrappers:metrics_default",
|
|
|
|
|
"../test:rtp_test_utils",
|
|
|
|
|
]
|
|
|
|
|
if (!build_with_chromium && is_clang) {
|
|
|
|
|
# Suppress warnings from the Chromium Clang plugin (bugs.webrtc.org/163).
|
|
|
|
|
suppressed_configs += [ "//build/config/clang:find_bad_constructs" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
2017-01-17 02:37:34 -08:00
|
|
|
}
|
2017-02-08 04:22:53 -08:00
|
|
|
if (rtc_include_tests) {
|
|
|
|
|
rtc_executable("rtc_event_log2text") {
|
|
|
|
|
testonly = true
|
|
|
|
|
sources = [
|
|
|
|
|
"rtc_event_log/rtc_event_log2text.cc",
|
|
|
|
|
]
|
|
|
|
|
deps = [
|
|
|
|
|
":rtc_event_log_api",
|
|
|
|
|
":rtc_event_log_impl",
|
|
|
|
|
":rtc_event_log_parser",
|
2017-09-01 15:29:28 +02:00
|
|
|
"../call:video_stream_api",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:rtc_base_approved",
|
2017-02-08 09:37:30 -08:00
|
|
|
|
|
|
|
|
# TODO(kwiberg): Remove this dependency.
|
2017-02-10 08:15:44 -08:00
|
|
|
"../api/audio_codecs:audio_codecs_api",
|
2017-09-15 16:13:21 +02:00
|
|
|
"../modules/audio_coding:audio_network_adaptor_config",
|
2017-02-08 04:22:53 -08:00
|
|
|
"../modules/rtp_rtcp:rtp_rtcp",
|
|
|
|
|
]
|
|
|
|
|
if (!build_with_chromium && is_clang) {
|
|
|
|
|
# Suppress warnings from the Chromium Clang plugin (bugs.webrtc.org/163).
|
|
|
|
|
suppressed_configs += [ "//build/config/clang:find_bad_constructs" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
2017-04-28 07:48:17 -07:00
|
|
|
if (rtc_include_tests) {
|
|
|
|
|
rtc_executable("rtc_event_log2stats") {
|
|
|
|
|
testonly = true
|
|
|
|
|
sources = [
|
|
|
|
|
"rtc_event_log/rtc_event_log2stats.cc",
|
|
|
|
|
]
|
|
|
|
|
deps = [
|
|
|
|
|
":rtc_event_log_api",
|
|
|
|
|
":rtc_event_log_impl",
|
|
|
|
|
":rtc_event_log_proto",
|
2017-07-19 10:40:47 -07:00
|
|
|
"../rtc_base:rtc_base_approved",
|
2017-04-28 07:48:17 -07:00
|
|
|
]
|
|
|
|
|
if (!build_with_chromium && is_clang) {
|
|
|
|
|
# Suppress warnings from the Chromium Clang plugin (bugs.webrtc.org/163).
|
|
|
|
|
suppressed_configs += [ "//build/config/clang:find_bad_constructs" ]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
Moved RtcEventLog files from call/ to logging/
The RtcEventLog headers need to be accessible from any place which needs
logging, and the implementation needs access to data structures that are
logged.
After a discussion in the code review, we all agreed to move the RtcEventLog implementation into its own top level directory - which I called "logging/" in expectation that other types of logging may have similar requirements. The directory contains two main build targets - "rtc_event_log_api", which is just rtc_event_log.h, that has no external dependencies and can be used from anywhere, and "rtc_event_log_impl" which contains the rest of the implementation and has many dependencies (more in the future).
The "api" target can be referenced from anywhere, while the "impl" target is only needed at the place of instantiation (currently Call, soon to be moved to PeerConnection by https://codereview.webrtc.org/2353033005/).
This change allows using RtcEventLog in the p2p/ directory, so that we
can log STUN pings and ICE state transitions.
BUG=webrtc:6393
R=kjellander@webrtc.org, kwiberg@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, terelius@webrtc.org
Review URL: https://codereview.webrtc.org/2380683005 .
Cr-Commit-Position: refs/heads/master@{#14485}
2016-10-03 18:31:22 -07:00
|
|
|
}
|