Go to file
2024-02-07 20:50:00 +03:00
benchmark Update copyright year. 2024-01-01 03:07:21 +03:00
CMake Change deprecated exec_program to execute_process in iOS.cmake 2023-12-22 15:39:13 +03:00
example Add registerUser.disable_notification. 2024-01-29 16:43:42 +03:00
memprof Update copyright year. 2024-01-01 03:07:21 +03:00
sqlite Export static targets in a separate file 2023-10-14 23:56:00 +03:00
td Add td_api::messageChatBoost. 2024-02-07 20:50:00 +03:00
tdactor Improve ServiceActor logging. 2024-02-01 20:31:43 +03:00
tddb Add source to Binlog::sync. 2024-02-02 15:09:17 +03:00
tdnet Update copyright year. 2024-01-01 03:07:21 +03:00
tdtl Update copyright year. 2024-01-01 03:07:21 +03:00
tdutils Minor fixes. 2024-02-07 17:50:57 +03:00
test Strip more empty characters. 2024-02-01 21:16:01 +03:00
.clang-format Update clang-format to 16.0.0. 2023-02-08 15:28:36 +03:00
.gitattributes Various fixes. 2023-04-07 16:02:31 +03:00
.gitignore Update .gitignore. 2023-02-13 15:51:04 +03:00
build.html Update FreeBSD build instructions to FreeBSD 13. 2023-11-27 13:21:56 +03:00
CHANGELOG.md Improve documentation. 2023-11-30 18:43:38 +03:00
CMakeLists.txt Add empty SavedMessagesManager. 2024-02-04 12:41:53 +03:00
Doxyfile Project import generated by Copybara. 2017-12-31 23:08:40 +03:00
format.ps1 Improve listing of files to be formatted. 2022-01-27 15:37:42 +03:00
format.sh Improve listing of files to be formatted. 2022-01-27 15:37:42 +03:00
LICENSE_1_0.txt Project import generated by Copybara. 2017-12-31 23:08:40 +03:00
post.js tdweb: temporary fix to access Module.FS before promise is completed 2020-10-09 19:40:13 +03:00
README.md Update version to 1.8.24. 2024-01-27 03:43:28 +03:00
SplitSource.php Add empty SavedMessagesManager. 2024-02-04 12:41:53 +03:00
src.ps1 Update src.sh/src.ps1. 2023-02-13 15:43:55 +03:00
src.sh Update src.sh/src.ps1. 2023-02-13 15:43:55 +03:00
tdclientjson_export_list Remove set_log_fatal_error_callback. Add td_set_log_message_callback, deprecate td_set_log_fatal_error_callback. 2021-05-18 04:41:09 +03:00
TdConfig.cmake Minor improvements. 2023-10-15 01:20:09 +03:00
update_version.sh Fix typos. (#2365) 2023-03-26 22:38:14 +03:00

TDLib

TDLib (Telegram Database library) is a cross-platform library for building Telegram clients. It can be easily used from almost any programming language.

Table of Contents

Features

TDLib has many advantages. Notably TDLib is:

  • Cross-platform: TDLib can be used on Android, iOS, Windows, macOS, Linux, FreeBSD, OpenBSD, NetBSD, illumos, Windows Phone, WebAssembly, watchOS, tvOS, Tizen, Cygwin. It should also work on other *nix systems with or without minimal effort.
  • Multilanguage: TDLib can be easily used with any programming language that is able to execute C functions. Additionally, it already has native Java (using JNI) bindings and .NET (using C++/CLI and C++/CX) bindings.
  • Easy to use: TDLib takes care of all network implementation details, encryption and local data storage.
  • High-performance: in the Telegram Bot API, each TDLib instance handles more than 24000 active bots simultaneously.
  • Well-documented: all TDLib API methods and public interfaces are fully documented.
  • Consistent: TDLib guarantees that all updates are delivered in the right order.
  • Reliable: TDLib remains stable on slow and unreliable Internet connections.
  • Secure: all local data is encrypted using a user-provided encryption key.
  • Fully-asynchronous: requests to TDLib don't block each other or anything else, responses are sent when they are available.

Examples and documentation

See our Getting Started tutorial for a description of basic TDLib concepts.

Take a look at our examples.

See a TDLib build instructions generator for detailed instructions on how to build TDLib.

See description of our JSON, C++, Java and .NET interfaces.

See the td_api.tl scheme or the automatically generated HTML documentation for a list of all available TDLib methods and classes.

Dependencies

TDLib depends on:

  • C++14 compatible compiler (Clang 3.4+, GCC 4.9+, MSVC 19.0+ (Visual Studio 2015+), Intel C++ Compiler 17+)
  • OpenSSL
  • zlib
  • gperf (build only)
  • CMake (3.0.2+, build only)
  • PHP (optional, for documentation generation)

Building

The simplest way to build TDLib is to use our TDLib build instructions generator. You need only to choose your programming language and target operating system to receive complete build instructions.

In general, you need to install all TDLib dependencies, enter directory containing TDLib sources and compile them using CMake:

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
cmake --build .

To build TDLib on low memory devices you can run SplitSource.php script before compiling main TDLib source code and compile only needed targets:

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
cmake --build . --target prepare_cross_compiling
cd ..
php SplitSource.php
cd build
cmake --build . --target tdjson
cmake --build . --target tdjson_static
cd ..
php SplitSource.php --undo

In our tests clang 6.0 with libc++ required less than 500 MB of RAM per file and GCC 4.9/6.3 used less than 1 GB of RAM per file.

Using in CMake C++ projects

For C++ projects that use CMake, the best approach is to build TDLib as part of your project or to install it system-wide.

There are several libraries that you could use in your CMake project:

  • Td::TdJson, Td::TdJsonStatic — dynamic and static version of a JSON interface. This has a simple C interface, so it can be easily used with any programming language that is able to execute C functions. See td_json_client documentation for more information.
  • Td::TdStatic — static library with C++ interface for general usage. See ClientManager and Client documentation for more information.

For example, part of your CMakeLists.txt may look like this:

add_subdirectory(td)
target_link_libraries(YourTarget PRIVATE Td::TdStatic)

Or you could install TDLib and then reference it in your CMakeLists.txt like this:

find_package(Td 1.8.24 REQUIRED)
target_link_libraries(YourTarget PRIVATE Td::TdStatic)

See example/cpp/CMakeLists.txt.

Using in Java projects

TDLib provides native Java interface through JNI. To enable it, specify option -DTD_ENABLE_JNI=ON to CMake.

See example/java for example of using TDLib from Java and detailed build and usage instructions.

Using in .NET projects

TDLib provides native .NET interface through C++/CLI and C++/CX. To enable it, specify option -DTD_ENABLE_DOTNET=ON to CMake. .NET Core supports C++/CLI only since version 3.1 and only on Windows, so if older .NET Core is used or portability is needed, then TDLib JSON interface should be used through P/Invoke instead.

See example/csharp for example of using TDLib from C# and detailed build and usage instructions. See example/uwp for example of using TDLib from C# UWP application and detailed build and usage instructions for Visual Studio Extension "TDLib for Universal Windows Platform".

When TDLib is built with TD_ENABLE_DOTNET option enabled, C++ documentation is removed from some files. You need to checkout these files to return C++ documentation back:

git checkout td/telegram/Client.h td/telegram/Log.h td/tl/TlObject.h

Using from other programming languages

TDLib provides efficient native C++, Java, and .NET interfaces. But for most use cases we suggest to use the JSON interface, which can be easily used with any programming language that is able to execute C functions. See td_json_client documentation for detailed JSON interface description, the td_api.tl scheme or the automatically generated HTML documentation for a list of all available TDLib methods and classes.

TDLib JSON interface adheres to semantic versioning and versions with the same major version number are binary and backward compatible, but the underlying TDLib API can be different for different minor and even patch versions. If you need to support different TDLib versions, then you can use a value of the version option to find exact TDLib version to use appropriate API methods.

See example/python/tdjson_example.py for an example of such usage.

License

TDLib is licensed under the terms of the Boost Software License. See LICENSE_1_0.txt for more information.