RepoMirrors
/
tdesktop
mirror of https://github.com/telegramdesktop/tdesktop
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tdesktop/docs/building-cmake.md

45 lines
1.5 KiB
Markdown
Raw Normal View History

Update Linux build instructions Co-authored-by: Ilya Fedin <fedin-ilja2010@ya.ru>
2020-12-13 06:16:37 +00:00
## Build instructions for CMake using Docker
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Don't provide 'api_id' and 'api_hash' by default. We ask the developer to obtain his own api credentials, because the bundled 'api_id' / 'api_hash' are strictly limited by the server. The old credentials still could be used for test purposes, but the developer will need to explicitly opt-in to use them.
2018-11-04 10:29:30 +00:00
### Obtain your API credentials
You will require **api_id** and **api_hash** to access the Telegram API servers. To learn how to obtain them [click here][api_credentials].
Update Linux build instructions Co-authored-by: Ilya Fedin <fedin-ilja2010@ya.ru>
2020-12-13 06:16:37 +00:00
### Clone source code
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Move build to Ubuntu 14.04 and GCC 7.2. To be able to run on the same distributions as before we need to have the same GLIBC version dependency as in Ubuntu 12.04, which is 2.15. For that we need to remove all usages of GLIBC features from 2.16 and above. Currently there are three methods used, so they're wrapped in a separate static library, linux_glibc_wraps. It is a separate library because it must be compiled without '-flto' flag, otherwise the inline __asm__ is not working and we get unresolved symbols.
2017-09-28 09:40:26 +00:00
git clone --recursive https://github.com/telegramdesktop/tdesktop.git
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Update Linux build instructions Co-authored-by: Ilya Fedin <fedin-ilja2010@ya.ru>
2020-12-13 06:16:37 +00:00
### Prepare libraries
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Update Linux build instructions Co-authored-by: Ilya Fedin <fedin-ilja2010@ya.ru>
2020-12-13 06:16:37 +00:00
Go to the `tdesktop` directory and run
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Update Linux build instructions Co-authored-by: Ilya Fedin <fedin-ilja2010@ya.ru>
2020-12-13 06:16:37 +00:00
docker build -t tdesktop:centos_env Telegram/build/docker/centos_env/
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Move build to Ubuntu 14.04 and GCC 7.2. To be able to run on the same distributions as before we need to have the same GLIBC version dependency as in Ubuntu 12.04, which is 2.15. For that we need to remove all usages of GLIBC features from 2.16 and above. Currently there are three methods used, so they're wrapped in a separate static library, linux_glibc_wraps. It is a separate library because it must be compiled without '-flto' flag, otherwise the inline __asm__ is not working and we get unresolved symbols.
2017-09-28 09:40:26 +00:00
### Building the project
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Update Linux build instructions Co-authored-by: Ilya Fedin <fedin-ilja2010@ya.ru>
2020-12-13 06:16:37 +00:00
Make sure that you're still in the `tdesktop` directory and run (using [your **api_id** and **api_hash**](#obtain-your-api-credentials))
docker run --rm \
-v $PWD:/usr/src/tdesktop \
tdesktop:centos_env \
/usr/src/tdesktop/Telegram/build/docker/centos_env/build.sh \
-D TDESKTOP_API_ID=YOUR_API_ID \
-D TDESKTOP_API_HASH=YOUR_API_HASH \
-D DESKTOP_APP_USE_PACKAGED=OFF \
-D DESKTOP_APP_DISABLE_CRASH_REPORTS=OFF
Or, to create a debug build, run (also using [your **api_id** and **api_hash**](#obtain-your-api-credentials))
docker run --rm \
-v $PWD:/usr/src/tdesktop \
-e DEBUG=1 \
tdesktop:centos_env \
/usr/src/tdesktop/Telegram/build/docker/centos_env/build.sh \
-D TDESKTOP_API_ID=YOUR_API_ID \
-D TDESKTOP_API_HASH=YOUR_API_HASH \
-D DESKTOP_APP_USE_PACKAGED=OFF \
-D DESKTOP_APP_DISABLE_CRASH_REPORTS=OFF
The built files will be in the `out` directory.
Moved all builds to GYP.
2016-09-12 11:45:41 +00:00
Don't provide 'api_id' and 'api_hash' by default. We ask the developer to obtain his own api credentials, because the bundled 'api_id' / 'api_hash' are strictly limited by the server. The old credentials still could be used for test purposes, but the developer will need to explicitly opt-in to use them.
2018-11-04 10:29:30 +00:00
[api_credentials]: api_credentials.md