ntgcalls 2.0.6__cp314-cp314-win_amd64.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,172 @@
1
+ Metadata-Version: 2.4
2
+ Name: ntgcalls
3
+ Version: 2.0.6
4
+ Summary: A Native Implementation of Telegram Calls in a seamless way.
5
+ Author-email: Laky-64 <iraci.matteo@gmail.com>
6
+ Project-URL: Homepage, https://pytgcalls.github.io/
7
+ Project-URL: Repository, https://github.com/pytgcalls/ntgcalls.git
8
+ Project-URL: Documentation, https://pytgcalls.github.io/NTgCalls
9
+ Project-URL: Changelog, https://pytgcalls.github.io/PyTgCalls/Changelogs
10
+ Keywords: audio,python,library,video,telegram,stream,ffmpeg,cpp,webrtc,voice-chat,voip,group-chat,video-calls,calls,video-chat,pytgcalls,ntgcalls,tgcalls,py-tgcalls
11
+ Classifier: Programming Language :: Python :: 3
12
+ Classifier: Programming Language :: Python :: 3 :: Only
13
+ Classifier: Programming Language :: Python :: 3.9
14
+ Classifier: Programming Language :: Python :: 3.10
15
+ Classifier: Programming Language :: Python :: 3.11
16
+ Classifier: Programming Language :: Python :: 3.12
17
+ Classifier: Programming Language :: Python :: 3.13
18
+ Classifier: Programming Language :: Python :: Implementation :: CPython
19
+ Requires-Python: >=3.9
20
+ Description-Content-Type: text/markdown
21
+ License-File: LICENSE
22
+ Provides-Extra: test
23
+ Requires-Dist: pytest>=6.0; extra == "test"
24
+ Dynamic: license-file
25
+
26
+ <img src="https://raw.githubusercontent.com/pytgcalls/ntgcalls/master/.github/images/banner.png" alt="pytgcalls logo" />
27
+ <p align="center">
28
+ <b>A Native Implementation of Telegram Calls in a seamless way.</b>
29
+ <br>
30
+ <a href="https://github.com/pytgcalls/ntgcalls/tree/master/examples">
31
+ Examples
32
+ </a>
33
+
34
+ <a href="https://pytgcalls.github.io/">
35
+ Documentation
36
+ </a>
37
+
38
+ <a href="https://pypi.org/project/ntgcalls/">
39
+ PyPi
40
+ </a>
41
+
42
+ <a href="https://github.com/pytgcalls/ntgcalls/releases">
43
+ Releases
44
+ </a>
45
+
46
+ <a href="https://t.me/pytgcallsnews">
47
+ Channel
48
+ </a>
49
+
50
+ <a href="https://t.me/pytgcallschat">
51
+ Chat
52
+ </a>
53
+ </p>
54
+
55
+ # NTgCalls [![PyPI - Version](https://img.shields.io/pypi/v/ntgcalls?logo=python&logoColor=%23959DA5&label=pypi&labelColor=%23282f37)](https://pypi.org/project/ntgcalls/) [![Downloads](https://img.shields.io/pepy/dt/ntgcalls?logoColor=%23959DA5&labelColor=%23282f37&color=%2328A745)](https://pepy.tech/project/ntgcalls)
56
+ NTgCalls is a lightweight open-source library for media streaming in Telegram calls. Built from scratch in C++ with WebRTC & Boost, it prioritizes accessibility to developers and resource efficiency.
57
+
58
+ | Powerful | Simple | Light |
59
+ |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
60
+ | <img src="https://raw.githubusercontent.com/pytgcalls/ntgcalls/master/.github/images/fast.gif" width=150 alt="Fast Logo"/><br>Built from scratch in C++ using Boost and libwebrtc | <img src="https://raw.githubusercontent.com/pytgcalls/ntgcalls/master/.github/images/simple.gif" width=150 alt="Simple Logo"/><br>Simple Python, GO, C Bindings and Java for Android SDK<br> | <img src="https://raw.githubusercontent.com/pytgcalls/ntgcalls/master/.github/images/light.gif" width=150 alt="Light logo"/><br>We removed anything that could burden the library, including <b>NodeJS</b> |
61
+
62
+ ## Build Status
63
+ | Architecture | Windows | Linux | MacOS |
64
+ |:------------:|:-------------------------------------------------------------------------------------------------------------------------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------:|
65
+ | x86_64 | ![BUILD](https://img.shields.io/badge/build-passing-dark_green?logo=windows11&logoColor=%23959DA5&labelColor=%23282f37&color=%2328A745) | ![BUILD](https://img.shields.io/badge/build-passing-dark_green?logo=linux&logoColor=%23959DA5&labelColor=%23282f37&color=%2328A745) | ![BUILD](https://img.shields.io/badge/build-unsupported-dark_green?logo=apple&logoColor=%23959DA5&labelColor=%23282f37&color=%23959DA5) |
66
+ | ARM64 | ![BUILD](https://img.shields.io/badge/build-unsupported-dark_green?logo=windows11&logoColor=%23959DA5&labelColor=%23282f37&color=%23959DA5) | ![BUILD](https://img.shields.io/badge/build-passing-dark_green?logo=linux&logoColor=%23959DA5&labelColor=%23282f37&color=%2328A745) | ![BUILD](https://img.shields.io/badge/build-passing-dark_green?logo=apple&logoColor=%23959DA5&labelColor=%23282f37&color=%2328A745) |
67
+
68
+ ## Features
69
+ - Pre-built binaries for macOS (arm64-v8a), Linux (x86_64, arm64-v8a), Windows (x86_64), and Android (x86, 86_64, arm64-v8a, armv7)
70
+ - Call flexibility: Group and private call support
71
+ - Media controls: pause/resume and mute/unmute
72
+ - Codec compatibility: H.264, HEVC (H.265), VP8, VP9, AV1, AAC, MP3, Opus
73
+ - Content sharing: Screen streaming, Microphone and Camera streaming
74
+ - Pre-built wheels for Python & AAR SDK library for Android
75
+
76
+ ## Compiling
77
+
78
+ ### Python Bindings
79
+ NTgCalls includes Python bindings for seamless integration. Follow these steps to compile it with Python Bindings:
80
+ 1. Ensure you are in the root directory of the NTgCalls project.
81
+ 2. Run the following command to install the Py Bindings:
82
+
83
+ ```shell
84
+ python3 setup.py install
85
+ ```
86
+ ### Go Bindings
87
+ > [!WARNING]
88
+ > Static linking for Windows is not supported yet since our library is built with MSVC and Go uses MinGW for static linking.
89
+ > More info can be found [here](https://github.com/golang/go/issues/63903)
90
+
91
+ NTgCalls includes Go Bindings, enabling seamless integration with Go. Follow these steps to compile it with Go Bindings:
92
+ 1. There is an example project for Go in `./examples/go/` directory, ensure you are in that directory
93
+ 2. Prerequisites for building are the same as for building a library itself and can be found [here](https://pytgcalls.github.io/NTgCalls/Build%20Guide#Installing=Prerequisites)
94
+ 3. Download **shared** or **static** release of the library from https://github.com/pytgcalls/ntgcalls/releases
95
+ 4. Copy `ntgcalls.h` file into `./examples/go/ntgcalls/` directory
96
+ 5. The rest of the files should be copied to `./examples/go/` directory
97
+ * `ntgcalls.dll` or `ntgcalls.lib` files in case of Windows amd64
98
+ * `libntgcalls.so` or `libntgcalls.a` files in case of Linux amd64
99
+ * `libntgcalls.dylib` or `libntgcalls.a` files in case of macOS
100
+ 6. Then in `./examples/go/` directory run `go build` or `go run .` with CGO_ENABLED=1 env variable set
101
+ * `$env:CGO_ENABLED=1; go run .` for Windows PowerShell
102
+ * `CGO_ENABLED=1 go run .` for UNIX
103
+
104
+
105
+ ### C Bindings
106
+ For developers looking to use NTgCalls with C and C++, we provide C Bindings. Follow these steps to compile it with C Bindings:
107
+ 1. Ensure you are in the root directory of the NTgCalls project.
108
+ 2. Run the following command to generate the library:
109
+ ```shell
110
+ # Static library
111
+ python3 setup.py build_lib --static
112
+
113
+ # Shared library
114
+ python3 setup.py build_lib --shared
115
+ ```
116
+ 3. Upon successful execution, a library will be generated in the "shared-output" or "static-output" directory, depending on the chosen option.
117
+ Now you can use this library to develop applications with NTgCalls.
118
+ 4. To include the necessary headers in your C/C++ projects, you will find the "include" folder in the "shared-output" or "static-output" directory.
119
+ Use this folder by including the required header files.
120
+
121
+ ## Key Contributors
122
+ * <b><a href="https://github.com/Laky-64">@Laky-64</a> (DevOps Engineer, Software Architect, Porting Engineer):</b>
123
+ * Played a crucial role in developing NTgCalls.
124
+ * Created the Python Bindings that made the library accessible to Python developers.
125
+ * Developed the C Bindings, enabling the library's use in various environments.
126
+ * <b><a href="https://github.com/dadadani">@dadadani</a> (Senior C++ Developer, Performance engineer):</b>
127
+ * Contributed to setting up CMakeLists and integrating with pybind11,
128
+ greatly simplifying the library's usage for C++ developers.
129
+ * <b><a href="https://github.com/kuogi">@kuogi</a> (Senior UI/UX designer, Documenter):</b>
130
+ * As a Senior UI/UX Designer, Kuogi has significantly improved the user interface of our documentation,
131
+ making it more visually appealing and user-friendly.
132
+ * It Has also played a key role in writing and structuring our documentation, ensuring that it is clear,
133
+ informative, and accessible to all users.
134
+ * <b><a href="https://github.com/vrumger">@vrumger</a> (Mid-level NodeJS Developer):</b>
135
+ * Avrumy has made important fixes and enhancements to the WebRTC component of the library,
136
+ improving its stability and performance.
137
+
138
+ ## Junior Developers
139
+ * <b><a href="https://github.com/TuriOG">@TuriOG</a> (Junior Python Developer):</b>
140
+ * Currently working on integrating NTgCalls into <a href="//github.com/pytgcalls/pytgcalls">PyTgCalls</a>, an important step
141
+ in expanding the functionality and usability of the library.
142
+ * <b><a href="https://github.com/doggyhaha">@doggyhaha</a> (Junior DevOps, Tester):</b>
143
+ * Performs testing of NTgCalls on Linux to ensure its reliability and compatibility.
144
+ * Specializes in creating and maintaining GitHub Actions, focusing on automation tasks.
145
+ * <b><a href="https://github.com/tappo03">@tappo03</a> (Junior Go Developer, Tester):</b>
146
+ * Performs testing of NTgCalls on Windows to ensure its reliability and compatibility.
147
+ * It Is in the process of integrating NTgCalls into a Go wrapper, further enhancing the library's
148
+ versatility and accessibility.
149
+
150
+ ## Special Thanks
151
+ * <b><a href="https://github.com/shiguredo">@shiguredo</a>:</b>
152
+ We extend our special thanks to 時雨堂 (shiguredo) for their invaluable assistance in integrating the WebRTC component. Their contributions,
153
+ using the Sora C++ SDK, have been instrumental in enhancing the functionality of our library.
154
+
155
+ * <b><a href="https://github.com/evgeny-nadymov">@evgeny-nadymov</a>:</b>
156
+ A heartfelt thank you to Evgeny Nadymov for graciously allowing us to use their code from telegram-react.
157
+ His contribution has been pivotal to the success of this project.
158
+
159
+ * <b><a href="https://github.com/morethanwords">@morethanwords</a>:</b>
160
+ We extend our special thanks to morethanwords for their invaluable help in integrating the connection to WebRTC with Telegram Web K.
161
+ Their assistance has been instrumental in enhancing the functionality of our library.
162
+
163
+ * <b><a href="https://github.com/MarshalX">@MarshalX</a>:</b> for their generous assistance in answering questions and providing insights regarding WebRTC.
164
+
165
+ * <b><a href="https://github.com/LyzCoote">@LyzCoote</a>:</b> for providing an ARM64 Server and allowing us to build an image with clang-18 preinstalled on manylinux2014 arm64.
166
+
167
+ _We would like to extend a special thanks to <b><a href='https://github.com/null-nick'>@null-nick</a></b>
168
+ and <b><a href='https://github.com/branchscope'>@branchscope</a></b> for their valuable contributions to the testing phase of the library and to
169
+ <b><a href='https://github.com/SadLuffy'>@SadLuffy</a></b> for his assistance as a copywriter.
170
+ Their dedication to testing and optimizing the library has been instrumental in its success._
171
+
172
+ _Additionally, we extend our gratitude to all contributors for their exceptional work in making this project a reality._
@@ -0,0 +1,6 @@
1
+ ntgcalls.cp314-win_amd64.pyd,sha256=Pbb5kUhyQ_jLe_FYdHS81ntxYw6HOyIfOLmhGM6iWTg,25858560
2
+ ntgcalls-2.0.6.dist-info/licenses/LICENSE,sha256=fTqV5eBpeAZO0_jit8j4Ref9ikBSlHJ8xwj5TLg7gFk,7817
3
+ ntgcalls-2.0.6.dist-info/METADATA,sha256=nVXmUCQ1XoEfpVsBAEtH7kEA6b5WV2TnYZfIuKxGiOs,12897
4
+ ntgcalls-2.0.6.dist-info/WHEEL,sha256=7k6Wcy588iJYe5lf5K095NLg-uoBTnE-T8eHJ92G4_4,101
5
+ ntgcalls-2.0.6.dist-info/top_level.txt,sha256=LCk4_cz4kC2dLieFf0R1iYJue6L794TLK9To903MEVg,9
6
+ ntgcalls-2.0.6.dist-info/RECORD,,
@@ -0,0 +1,5 @@
1
+ Wheel-Version: 1.0
2
+ Generator: setuptools (80.9.0)
3
+ Root-Is-Purelib: false
4
+ Tag: cp314-cp314-win_amd64
5
+
@@ -0,0 +1,165 @@
1
+ GNU LESSER GENERAL PUBLIC LICENSE
2
+ Version 3, 29 June 2007
3
+
4
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
5
+ Everyone is permitted to copy and distribute verbatim copies
6
+ of this license document, but changing it is not allowed.
7
+
8
+
9
+ This version of the GNU Lesser General Public License incorporates
10
+ the terms and conditions of version 3 of the GNU General Public
11
+ License, supplemented by the additional permissions listed below.
12
+
13
+ 0. Additional Definitions.
14
+
15
+ As used herein, "this License" refers to version 3 of the GNU Lesser
16
+ General Public License, and the "GNU GPL" refers to version 3 of the GNU
17
+ General Public License.
18
+
19
+ "The Library" refers to a covered work governed by this License,
20
+ other than an Application or a Combined Work as defined below.
21
+
22
+ An "Application" is any work that makes use of an interface provided
23
+ by the Library, but which is not otherwise based on the Library.
24
+ Defining a subclass of a class defined by the Library is deemed a mode
25
+ of using an interface provided by the Library.
26
+
27
+ A "Combined Work" is a work produced by combining or linking an
28
+ Application with the Library. The particular version of the Library
29
+ with which the Combined Work was made is also called the "Linked
30
+ Version".
31
+
32
+ The "Minimal Corresponding Source" for a Combined Work means the
33
+ Corresponding Source for the Combined Work, excluding any source code
34
+ for portions of the Combined Work that, considered in isolation, are
35
+ based on the Application, and not on the Linked Version.
36
+
37
+ The "Corresponding Application Code" for a Combined Work means the
38
+ object code and/or source code for the Application, including any data
39
+ and utility programs needed for reproducing the Combined Work from the
40
+ Application, but excluding the System Libraries of the Combined Work.
41
+
42
+ 1. Exception to Section 3 of the GNU GPL.
43
+
44
+ You may convey a covered work under sections 3 and 4 of this License
45
+ without being bound by section 3 of the GNU GPL.
46
+
47
+ 2. Conveying Modified Versions.
48
+
49
+ If you modify a copy of the Library, and, in your modifications, a
50
+ facility refers to a function or data to be supplied by an Application
51
+ that uses the facility (other than as an argument passed when the
52
+ facility is invoked), then you may convey a copy of the modified
53
+ version:
54
+
55
+ a) under this License, provided that you make a good faith effort to
56
+ ensure that, in the event an Application does not supply the
57
+ function or data, the facility still operates, and performs
58
+ whatever part of its purpose remains meaningful, or
59
+
60
+ b) under the GNU GPL, with none of the additional permissions of
61
+ this License applicable to that copy.
62
+
63
+ 3. Object Code Incorporating Material from Library Header Files.
64
+
65
+ The object code form of an Application may incorporate material from
66
+ a header file that is part of the Library. You may convey such object
67
+ code under terms of your choice, provided that, if the incorporated
68
+ material is not limited to numerical parameters, data structure
69
+ layouts and accessors, or small macros, inline functions and templates
70
+ (ten or fewer lines in length), you do both of the following:
71
+
72
+ a) Give prominent notice with each copy of the object code that the
73
+ Library is used in it and that the Library and its use are
74
+ covered by this License.
75
+
76
+ b) Accompany the object code with a copy of the GNU GPL and this license
77
+ document.
78
+
79
+ 4. Combined Works.
80
+
81
+ You may convey a Combined Work under terms of your choice that,
82
+ taken together, effectively do not restrict modification of the
83
+ portions of the Library contained in the Combined Work and reverse
84
+ engineering for debugging such modifications, if you also do each of
85
+ the following:
86
+
87
+ a) Give prominent notice with each copy of the Combined Work that
88
+ the Library is used in it and that the Library and its use are
89
+ covered by this License.
90
+
91
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
92
+ document.
93
+
94
+ c) For a Combined Work that displays copyright notices during
95
+ execution, include the copyright notice for the Library among
96
+ these notices, as well as a reference directing the user to the
97
+ copies of the GNU GPL and this license document.
98
+
99
+ d) Do one of the following:
100
+
101
+ 0) Convey the Minimal Corresponding Source under the terms of this
102
+ License, and the Corresponding Application Code in a form
103
+ suitable for, and under terms that permit, the user to
104
+ recombine or relink the Application with a modified version of
105
+ the Linked Version to produce a modified Combined Work, in the
106
+ manner specified by section 6 of the GNU GPL for conveying
107
+ Corresponding Source.
108
+
109
+ 1) Use a suitable shared library mechanism for linking with the
110
+ Library. A suitable mechanism is one that (a) uses at run time
111
+ a copy of the Library already present on the user's computer
112
+ system, and (b) will operate properly with a modified version
113
+ of the Library that is interface-compatible with the Linked
114
+ Version.
115
+
116
+ e) Provide Installation Information, but only if you would otherwise
117
+ be required to provide such information under section 6 of the
118
+ GNU GPL, and only to the extent that such information is
119
+ necessary to install and execute a modified version of the
120
+ Combined Work produced by recombining or relinking the
121
+ Application with a modified version of the Linked Version. (If
122
+ you use option 4d0, the Installation Information must accompany
123
+ the Minimal Corresponding Source and Corresponding Application
124
+ Code. If you use option 4d1, you must provide the Installation
125
+ Information in the manner specified by section 6 of the GNU GPL
126
+ for conveying Corresponding Source.)
127
+
128
+ 5. Combined Libraries.
129
+
130
+ You may place library facilities that are a work based on the
131
+ Library side by side in a single library together with other library
132
+ facilities that are not Applications and are not covered by this
133
+ License, and convey such a combined library under terms of your
134
+ choice, if you do both of the following:
135
+
136
+ a) Accompany the combined library with a copy of the same work based
137
+ on the Library, uncombined with any other library facilities,
138
+ conveyed under the terms of this License.
139
+
140
+ b) Give prominent notice with the combined library that part of it
141
+ is a work based on the Library, and explaining where to find the
142
+ accompanying uncombined form of the same work.
143
+
144
+ 6. Revised Versions of the GNU Lesser General Public License.
145
+
146
+ The Free Software Foundation may publish revised and/or new versions
147
+ of the GNU Lesser General Public License from time to time. Such new
148
+ versions will be similar in spirit to the present version, but may
149
+ differ in detail to address new problems or concerns.
150
+
151
+ Each version is given a distinguishing version number. If the
152
+ Library as you received it specifies that a certain numbered version
153
+ of the GNU Lesser General Public License "or any later version"
154
+ applies to it, you have the option of following the terms and
155
+ conditions either of that published version or of any later version
156
+ published by the Free Software Foundation. If the Library as you
157
+ received it does not specify a version number of the GNU Lesser
158
+ General Public License, you may choose any version of the GNU Lesser
159
+ General Public License ever published by the Free Software Foundation.
160
+
161
+ If the Library as you received it specifies that a proxy can decide
162
+ whether future versions of the GNU Lesser General Public License shall
163
+ apply, that proxy's public statement of acceptance of any version is
164
+ permanent authorization for you to choose that version for the
165
+ Library.
@@ -0,0 +1 @@
1
+ ntgcalls
Binary file