This commit clarifies the need for the user to specify the path to libqt-jami
in the ./build.py --install call.
Change-Id: I89d512bae7d476e9e5cbf73cb5e05b8d00e842cf
- Give a hint on how to troubleshoot the contribs build.
- Add instruction for debugging runtime crashes using GDB.
Change-Id: I6ad931223ce0904fb292a59090d37a2cec422ae8
This will prevent a graphical issue present when disabling QWINDOWKIT_ENABLE_WINDOWS_SYSTEM_BORDERS to avoid the Windows 10 top border issue for the frameless window option. This allows us to remove the temp workaround that likely introduces side effects.
Gitlab: #1581
Change-Id: I36801064d31e2380312d73f88233e8ed9b757403
This commit makes the necessary changes to migrate from Qt 6.5.3 to
Qt 6.6.1 and fixes the following issues:
- EditedPopup.qml: "layout polish loop" and "recursive rearrange"
errors (GitLab: #1510) as well as an unreported bug where text was
clipped instead of elided
- BaseContextMenu.qml: QML warning ("Created graphical object was not
placed in the graphics scene.")
The daemon is also bumped in order to include a patch for a build issue
on openSUSE Leap (GitLab: #1552).
GitLab: #1466
Change-Id: I12df2f84067ebe961368879e08ff7ef275d93395
+ Requires that the Qt path is supplied when calling build.py --init.
+ format.py now also takes a --qt argument to specify the Qt path, used to locate qmlformat.
+ format.py takes a --type argument to specify the type of files to format (qml, cpp, or both).
qmlformat is called with `--normalize` and `--force`.
Gitlab: #1059
Change-Id: Id9ff4b17018370696792b44f55ed2f4bc8091193
This homogenizes the script calling convention with other platforms, and will allow for a cleaner approach when searching for Qt tools (qmlformat).
Gitlab: #1059
Change-Id: I540ff61bd92186bb5a2998670665631e352852b9
- simplifies and fixes the python build script for Windows
- applies pep8 to the script also
Gitlab: #899
Change-Id: Ieb3debd08ddf1649a46208fc52362d20c504c1b1
This patch moves already existing packaging scripts from jami-project
into client-qt.
Introduced changes are:
+ WITH_SUBMODULE must search in system lib too because for
packaging client-qt (for rpm) will be built separately, and will
depend on jami-daemon.
+ Fix appdata.xml (replace old wiki with docs.jami.net)
+ path changes (because we build in client-qt not jami-project).
GitLab: #853
Change-Id: I1313830d85c8094fcbcc52e22033a2add7b1e89f
Use registry
"HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion
/Themes/Personalize/AppsUseLightTheme"
to check if system theme is supported and if it is dark or
light.
Removes "EnableDarkTheme" in favor of "AppTheme".
Requires Windows SDK version 10.0.18362.0 to build with
system theme support.
Note: This does not watch for changes in system theme in
runtime as the support for it requires Windows Runtime
version 10.0.10240.0.
GitLab: #723
Change-Id: Ice8f7936a90535f47dc1870d4f18215e062684ba
Bring over the build.py script and its associated scripts from the
scripts subdirectory of the jami-project.git as of commit
14a328b88007bff5ea21650fb00f6d4ead14cf02, with small changes to
simplify and drop unneeded parts and adapt to their new locations.
Change-Id: I500702854e45392a931ff7505e191b966015cd16
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
Can be used directly in QML without having to derive from
QSortFilterProxyModel and manage source model settings from C++
code.
Change-Id: Icac1f6dadfc0d1f64b4459ae0cdbebdd30b79b3e
