You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 25, 2024. It is now read-only.
@@ -67,7 +67,8 @@ Common build options shared by Windows and Linux:
67
67
- The built binary will be under path specified by `--output_path`. If `--output_path` is not set, the built binary will be under `src/out` directory.
68
68
- The optional `--ssl_root` should be set to the root directory of lastest OpenSSL 1.1.1 binary. If specified, SDK will link to external openssl library instead of boringssl.
69
69
- Use `--gn_gen` to generate args.gn during the first build or when you change either `ssl_root`/`msdk_root`/`quic_root` options.
70
-
- The optional `--quic_root` should point to the directory containing QUIC library pre-built from owt-sdk-quic repo. This will build the SDK with QUIC enabled for conference mode.
70
+
- The optional `--quic_root` should point to the directory containing WebTransport library pre-built from owt-sdk-quic repo. This will build the SDK with WebTransport enabled for
71
+
conference mode. Refer to [README.webtransport](https://github.com/open-webrtc-toolkit/owt-client-native/blob/main/README.webtransport) for the version of webtransport library to be used.
71
72
- The optional `--tests` will trigger unit tests after build.
Copy file name to clipboardExpand all lines: talk/owt/docs/cpp/cpp.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,14 +7,14 @@ This SDK is interoperable with Open WebRTC Toolkit Client SDK for JavaScript\*,
7
7
Refer to the Release Notes for the latest information in the SDK release package, including features,
8
8
bug fixes and known issues.
9
9
# 2 Supported platforms {#section2}
10
-
Open WebRTC Toolkit Client SDK for Windows supports Windows 7 and later versions.
10
+
Open WebRTC Toolkit Client SDK for Windows supports Windows 8 and later versions.
11
11
# 3 Getting started {#section3}
12
12
Application on Open WebRTC Toolkit Client SDK for Windows should be built with Microsoft Visual Studio\* 2017 or 2019. Running time library for linking should be `Multi-threaded Debug (/MTd)` for debug version or `Multi-threaded (/MT)` for release version. Supported platform is x64.
13
13
The release package includes one sample application to get you started quickly with the SDK. The following two static libraries are provided in the SDK for only x64, along with their headers:
14
14
- owt-debug.lib - this library includes all the WebRTC features for debug usages.
15
15
- owt-release.lib - this library includes all the WebRTC features for release usages.
16
16
owt-debug.lib|owt-release references libraries in Windows SDK for DXVA support. Your application must statically link
17
-
mfuuid.lib, mf.lib, mfplat.lib, d3d9.lib, dxgi.lib, d3d11.lib and dxva2.lib to build. Depending on your signaling
17
+
mfuuid.lib, mf.lib, mfplat.lib, d3d9.lib, dxgi.lib, d3d11.lib, dcomp.lib and dxva2.lib to build. Depending on your signaling
18
18
channel implementation, you can optionally link sioclient.lib or sioclient_tls.lib if neccessary.
19
19
# 4 Socket.IO {#section4}
20
20
Socket.IO cpp client is an open source project hosted on [Github](https://github.com/socketio/socket.io-client-cpp). Please follow official guide on GitHub to build and link it. The version works with OWT is b1216ee428dd7d1e72368da9b12aa43bfc487c93.
@@ -29,8 +29,8 @@ for P2P sessions can be customized by implementing `P2PSignalingChannelInterface
29
29
can invoke its methods to notify `PeerClient` during your customized signaling channel implementation when a new
30
30
message is coming or connection is lost.
31
31
# 7 Video codecs {#section7}
32
-
For the decoder, if hardware acceleration is not enabled, only VP8/VP9 is supported. If hardware acceleration is enabled, VP8,
33
-
VP9, H.264and HEVC are supported, but it will fallback to VP8 software decoder if GPU does not supports VP8 hardware decoding.
32
+
For the decoder, if hardware acceleration is not enabled, only VP8/VP9/AV1 is supported. If hardware acceleration is enabled, VP8,
33
+
VP9, H.264, HEVC and AV1 are supported, but it will fallback to VP8 software decoder if GPU does not supports VP8 hardware decoding.
34
34
Most of the 5th-11th Generation Intel<sup>®</sup> Core(TM) Processor platforms support VP8 hardware decoding, refer to their specific documentation for details.
35
35
Starting from 6th Generation Intel<sup>®</sup> Core(TM) Processor platforms, hardware encoding and decoding of HEVC is supported.
36
36
You can turn off video encoding/decoding hardware acceleration via {@link owt.base.GlobalConfiguration GlobalConfiguration} API,
0 commit comments