This patch targets GNU/Linux; macOS and Windows to be handled later.

Change-Id: I20581f8c1c345b087b117ce4441cb145b6e6e01d

Change-Id: I3a87ac3c2c506dd8d73fa76392e4587ec823a7ea

Tobias Hildebrandt authored 2 years ago and Adrien Béraud committed 2 years ago

disable -y by default

Change-Id: I6befd8564fc4334dae398d32d54d3871bd19b717

* build.py (QT5_VERSION):
(write_qt_conf): Remove (vestigial and not used anymore).
(PACMAN_BASED_DISTROS): Add parabola.
(ZYPPER_DEPENDENCIES):
(ZYPPER_CLIENT_QT_DEPENDENCIES):
(DNF_DEPENDENCIES):
(DNF_CLIENT_QT_DEPENDENCIES):
(APT_DEPENDENCIES):
(APT_CLIENT_QT_DEPENDENCIES):
(PACMAN_DEPENDENCIES):
(PACMAN_CLIENT_QT_DEPENDENCIES):
(OSX_DEPENDENCIES):
(OSX_DEPENDENCIES_UNLINK): Update dependency list for Qt 6, and move
lrc dependencies into client dependency lists.
(ZYPPER_QT_WEBENGINE):
(DNF_QT_WEBENGINE):
(APT_QT_WEBENGINE):
(PACMAN_QT_WEBENGINE): Move Qt WebEngine pacakge(s) into separate
list, so that they can be conditionally included or excluded.
(run_dependencies): Install daemon dependencies earlier than and
separately from lrc and client dependencies, mainly so that the
installation of daemon dependencies could still succeed on distros
that don't currently have Qt 6 packaged.
(run_dependencies):
(run_install):
(run_uninstall):
(run_run):
(main)
(parse_args): Add new --gnome switch, only use client-gnome when
this switch is given.  Add new --macos switch, only use client-macos
when this switch is given.  Otherwise, default to using client-qt.
Add new --no-webengine switch, disable using Qt WebEngine when this
switch is given.  Remove vestigial --qtver switch not used anymore.
Also, replace a few mentions of "Ring" with "Jami" in strings.
(validate_args): Test for minimum version of Windows 10 and do not
require an exact match/equality.

* scripts/build-windows.py (build_lrc):
(build_client):
(parsed_args): Remove vestigial and unneeded --qtver switch and its
corresponding variable.  Both make-lrc.py and make-client.py scripts
in their corresponding repositories have an up-to-date default Qt
version number, and specifying the version from this script is both
unnecessary and defeats their purpose.

* scripts/install.sh (QT6_MIN_VER): Rename to QT_MIN_VER.
(qt6ver): Remove, not used anymore.
(qt6path): Rename to qtpath.
(sys_qt6ver): Rename to sys_qtver.
(installed_qt6ver): Rename to installed_qtver.
(required_qt6ver): Rename to required_qtver.
(enable_webengine): New variable for tracking whether or not to use
Qt WebEngine.  Defaults to true.
(getopts): Add w option; when given, set enable_webengine to false.
(client_cmake_flags): Set -DWITH_WEBENGINE="${enable_webengine}".

Note: as of the time of this commit, QLibraryInfo from the qt6-base
package in Debian (and Ubuntu) currently has path issues and returns
wrong paths, stemming from '/lib' being a symlink.  This leads to
"Qt WebEngine resources not found" errors as the WebEngine tries to
find its needed resources at a wrong location '/share/qt6/resources'.
The issue has already been reported by others and a proposed patch to
fix it by disabling Qt's relocatable feature is pending review:
https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010575
In the mean time, using './build.py --install --no-webengine' to build
Jami without Qt WebEngine works.  Alternatively, using a custom build
of Qt (such as our libqt-jami) that does not suffer from this issue
would also work, using './build.py --install --qt=/usr/lib/libqt-jami'
where '/usr/lib/libqt-jami' should be the prefix directory where the
custom Qt build is installed.

GitLab: #1434
Change-Id: Ie053522de19b33871a1082ce46f3d36380a8b5aa

Change-Id: Ib005955e44a38cf6186bba9ea1acaff9454bcdbc

Change-Id: I4c319a058057c37154271ff0d3eec05a7e990c56

Change-Id: I2f624e870197d8369b166691375adf03e5dadffa

Change-Id: Ibb2def3712204ecc87c2e0d0666848aa002a25e9

Change-Id: I4266eed0e81621f3b27c52c7b63106e6f49beda3

Change-Id: I0a407e6667976bc6a90c24b4581593ee96a85453

Change-Id: I45428dbf670683f9039dd796a2d8c811c5c339e4

Change-Id: I9848e66358ce36630a201171831f23486ef48c3f

Change-Id: Id3e23e3273f95d522ad6b6af4314a76c508682d1

Change-Id: I32e75bdef93a386425fed12ef3b5e1f0d681cbbc

Change-Id: I32e75bdef93a386425fed12ef3b5e1f0d681cbbc

Change-Id: Ic523de4442c8b08651cbacf4f22d9a462fb5e62c

Change-Id: Ib0bb0985a396a9284229c79acc113a25c79c97bd

Change-Id: Iadb4c2091913c670e977c1966ccc22f962d787a1

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

Change-Id: I0e24dd8bbcc90e29cb63698507c46df439a2ca16

Change-Id: Iadb4c2091913c670e977c1966ccc22f962d787a1

Change-Id: Ib0bb0985a396a9284229c79acc113a25c79c97bd

Change-Id: I0e24dd8bbcc90e29cb63698507c46df439a2ca16

Since for our deb packages all the binary packages share the same
source package, and are built in the same environment, depending on
the distro and dpkg tools versions, dpkg-shlibdeps might incorrectly
add the wrong libclient package for either clients.  For example,
have the jami-gnome package depend on both jami-libclient-gnome and
jami-libclient; which is wrong, since jami-libclient-gnome and
jami-libclient conflict with each other and cannot be installed
simultaneously.  So, we instruct dpkg-shlibdeps to exclude the two
libclient packages from ${shlibs:Depends}, which is fine because
we already manually add the correct one to each client's Depends.

Also, use the system libarchive-dev package for Ubuntu 18.04 as well;
since like with Debian 10, building libarchive from daemon's contribs
fails there too.

GitLab: #1415
Change-Id: I1c065a7fd3fc58324c7893d5d23039f2a5109931

Change-Id: Ib0bb0985a396a9284229c79acc113a25c79c97bd

Change-Id: Ib0bb0985a396a9284229c79acc113a25c79c97bd