The current build instructions at https://github.com/telegramdesktop/tdesktop/blob/dev/docs/building-cmake.md assume Ubuntu 14.04, which is ancient; and require installing unstable versions of a bunch of libraries system-wide, which I'm not too keen on.
There are a few bugs on telegram desktop which I'd like to fix but can't do that if I can't even build it...
Building against system-wide libraries requires lots of patching of GYP scripts. Install version from Flatpak.
My issue is that the build instruction make you install the libraries, does using flatpak avoid that? how does it handle the monkey-patched Qt library?
Flatpak version built against Qt runtime.
and require installing unstable versions of a bunch of libraries system-wide, which I'm not too keen on.
Well, you can use docker for building.
Well, you can use docker for building.
Feels like a non-solution tbh, are all libraries statically linked? it would also make debugging very awkward because of the path differences.
Surely there must be a way to build telegram desktop without polluting your system
Surely there must be a way to build telegram desktop without polluting your system
If you want easy build process, you need to remove whole ugly GYP and replace it by cmake build system, like already did in Kepka fork.
@xvitaly if I install Telegram from Flatpak how does that help me making changes to the telegram sources?
If I try to compile disregarding the monkey patched libraries I have issues with the crl submodule, which seems to only support windows and apple but it's in the dependencies of other stuff
@mbasaglia It supports Linux as well, with Qt thread pool as a backend.
It just doesn't compile, I get to "#error "Configuration is not supported."" in crl_common_list.h which from what I've seen you avoid that branch by being on apple and have CRL_USE_DISPATCH defined or go to a different branch on that file by having the winapi