tag | e3dfd7c817e2a31ade0a1cb7e55afa673248f636 | |
---|---|---|
tagger | Jenkins <jenkins@jami-buildmachine-02.mtl.sfl> | Thu Aug 10 17:03:30 2023 -0400 |
object | 2066123520e24f3655e15202e07e759660003f3b |
Bump to version 376
commit | 2066123520e24f3655e15202e07e759660003f3b | [log] [tgz] |
---|---|---|
author | Adrien Béraud <adrien.beraud@savoirfairelinux.com> | Thu Aug 10 16:08:30 2023 -0400 |
committer | Adrien Béraud <adrien.beraud@savoirfairelinux.com> | Thu Aug 10 16:09:13 2023 -0400 |
tree | 3798952609bce3718e0c8ba790c483ffe72d3f5e | |
parent | 3d5a8e6f90915fb097ecf9547a8e40765f1b1b23 [diff] |
proguard: fix build with Gradle 8.0+ Change-Id: I2074f5b531d2466bf6151ee1ac5949378a992352
The Jami client for Android
App | CI |
---|---|
Download the project including the daemon submodule with:
git clone --recursive https://review.jami.net/jami-client-android
Or to download the daemon submodule from the existing project directory:
git submodule update --init --recursive
Make sure to have autotools, autopoint, swig, yasm, m4, ninja-build and cmake available on your system: on Debian/Ubuntu:
apt install cmake build-essential swig yasm ninja-build m4 autotools
On macOS:
brew install cmake automake autotools libtool pkg-config yasm swig
When using brew on macOS, the 'libtoolize' binary might be available as 'glibtoolize'. In that case, the following command makes it avaialble to the build system:
ln -s /opt/homebrew/bin/glibtoolize /opt/homebrew/bin/libtoolize
Make sure to have the Android SDK and NDK available.
With Android Studio:
With the command line:
cd jami-client-android/jami-android ./gradlew assembleDebug
Update translations using the Transifex client (tx) :
./update-translations.sh
Generate a new release commit updating the version code and version string:
./update_version.py --commit
Report issues on Gitlab: https://git.jami.net/savoirfairelinux/jami-client-android