Mirror/jami-client-qt
1
0
Fork 0
mirror of https://github.com/savoirfairelinux/jami-client-qt.git synced 2025-12-17 15:55:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

misc: Rename jami-qt to jami and remove launcher script.

Browse Source 
Now that there is no longer a second official client (jami-gnome), we
can remove this uninteresting implementation detail from the name.

Mostly automated via:

  $ git grep jami-qt -l | xargs sed 's/jami-qt/jami/g' -i

* src/app/jami: Delete launcher script.
* CMakeLists.txt: Un-register it from installation.

Change-Id: I5167c29089feb4e64c12d7d01c1ce281e16c0613
This commit is contained in:
Maxim Cournoyer
2022-07-26 09:22:44 -04:00
committed by Amin Bandali
parent 2fc8661d08
commit bf4a8c314f
12 changed files with 33 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
INSTALL.md
View File

@@ -79,7 +79,7 @@ Then, you can build daemon and the client with:
./build.py --install --qt
```
And you will have the daemon in `daemon/bin/jamid` and the client in `client-qt/build-local/jami-qt`. You also can run it with
And you will have the daemon in `daemon/bin/jamid` and the client in `client-qt/build-local/jami`. You also can run it with
If you use a Qt version that is not wide-system installed you need to specify its path after the `--qt` flag, i. e., `./build.py --install --qt /home/<username>/Qt/6.2.1/gcc_64
@@ -124,7 +124,7 @@ e.g. (with Qt version from https://jami.net)
cmake .. -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=jami-project/install/client-qt -DCMAKE_PREFIX_PATH=/usr/lib/libqt-jami
```
After the build has finished, you are finally ready to launch jami-qt in your build directory.
After the build has finished, you are finally ready to launch jami in your build directory.
If you want to install it to the path provided by `CMAKE_INSTALL_PREFIX` you can run:
@@ -201,7 +201,7 @@ When that happens you need to compile the client separately:
### Build Module Individually
- Jami-qt also support building each module (daemon, jami-qt) seperately
- Jami also supports building each module (daemon, jami) separately
**Daemon**
@@ -222,7 +222,7 @@ When that happens you need to compile the client separately:
python winmake.py -b opendht
```
**Jami-qt**
**Jami**
- Make sure that daemon, is built first
@@ -300,4 +300,4 @@ Built client could be find in `client-qt/build-local/Jami`
Compile the client with `BUILD=Debug` and compile LibRingClient with
`-DCMAKE_BUILD_TYPE=Debug`
Then, if you want to enable logging when running `jami-qt` launch it with `-d` or `--debug`
Then, if you want to enable logging when running `jami` launch it with `-d` or `--debug`