Package Details: telegram-tdlib 1.8.0-3

Git Clone URL: https://aur.archlinux.org/telegram-tdlib.git (read-only, click to copy)
Package Base: telegram-tdlib
Description: Cross-platform library for building Telegram clients
Upstream URL: https://core.telegram.org/tdlib
Keywords: tdlib telegram
Licenses: boost
Conflicts: telegram-tdlib
Provides: telegram-tdlib
Submitter: tleican
Maintainer: tleican
Last Packager: tleican
Votes: 13
Popularity: 0.000070
First Submitted: 2018-05-16 09:26 (UTC)
Last Updated: 2022-05-27 02:58 (UTC)

Pinned Comments

tleican commented on 2022-06-08 15:12 (UTC) (edited on 2022-06-08 15:14 (UTC) by tleican)

A note before you flag this out of date. :)

Telegram's main developer will tag stable releases on Github, and that is what is packaged here. See this comment from the main developer about requesting a 1.7 tag while 1.6 was the lastest tagged version:

The last release is still 1.6.0. All later version are development versions with continuously changing API. They all can be called 1.7.0-beta-X instead. Before TDLib 1.5.0 they wasn't even published on Github until next minor release. The 1.7.0 version will have a tag as soon it is ready.

Unless you can make Telegram change their mind about tagging, this is what you get here: a stable version.

If you need the latest unstable version, based on commit messages, check out libtd, it's fine! (Except it also brings PHP. 😅.)

Latest Comments

1 2 Next › Last »

xiota commented on 2023-11-12 13:08 (UTC)

libtd should be added to provides/conflicts because it shares the same files and upstream project.

nicholascw commented on 2023-05-17 20:08 (UTC) (edited on 2023-05-17 20:08 (UTC) by nicholascw)

The current PKGBUILD does not generate correct pkgconfig configurations.


--- a/a
+++ b/b
@@ -19,12 +19,12 @@ sha256sums=('30d560205fe82fb811cd57a8fcbc7ac853a5b6195e9cb9e6ff142f5e2d8be217')
 build() {
   mkdir -p "td-$pkgver/build"
   cd "td-$pkgver/build"
-  cmake -DCMAKE_INSTALL_PREFIX="${pkgdir}/usr" -DCMAKE_BUILD_TYPE=Release ..
+  cmake -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_BUILD_TYPE=Release ..
   cmake --build .
 }

 package() {
   cd "td-$pkgver/build"
   mkdir -p ${pkgdir}/usr
-  cmake --build . --target install
+  make DESTDIR=${pkgdir} install
 }

tleican commented on 2022-06-08 15:12 (UTC) (edited on 2022-06-08 15:14 (UTC) by tleican)

A note before you flag this out of date. :)

Telegram's main developer will tag stable releases on Github, and that is what is packaged here. See this comment from the main developer about requesting a 1.7 tag while 1.6 was the lastest tagged version:

The last release is still 1.6.0. All later version are development versions with continuously changing API. They all can be called 1.7.0-beta-X instead. Before TDLib 1.5.0 they wasn't even published on Github until next minor release. The 1.7.0 version will have a tag as soon it is ready.

Unless you can make Telegram change their mind about tagging, this is what you get here: a stable version.

If you need the latest unstable version, based on commit messages, check out libtd, it's fine! (Except it also brings PHP. 😅.)

Thaodan commented on 2022-06-05 23:11 (UTC)

Another way is to enable lto fat objects read here: https://archlinux.org/todo/lto-fat-objects/

Thaodan commented on 2022-05-17 22:17 (UTC) (edited on 2022-05-17 22:17 (UTC) by Thaodan)

@ephoz: If the user has the option lto in makepkg.conf enabled it breaks the static archives since stripping of static archives isn't supported with lto enabled.

tleican commented on 2022-05-16 17:27 (UTC)

@Thaodan What do you mean? I was under the impression that LTO was not enabled by default, assuming you meant -DTD_ENABLE_LTO=ON here.

Thaodan commented on 2022-05-15 21:36 (UTC)

tdlibs static archives break when lto is used. Can you add !lto to options?

fl.duriez commented on 2022-03-06 17:23 (UTC)

Please add aarch64 in arch list

tleican commented on 2021-03-17 19:49 (UTC)

@ellton: I'll try if I find the time. :)

ellton commented on 2021-03-17 19:42 (UTC)

Can you create a new pkg telegram-tdlib-git?