Recent libclient and client-qt use avframe from ffmpeg's libavutil.

Change-Id: Ia860e374eb2b8d6c22a79ee0f5a22673a292bf19

After the recent merge of the video renderer changes into lrc and
client-qt, the build for client-gnome is currently broken because it
has not yet been updated to follow the new API, a non-trivial task.
Thus, we add a separate lrc-gnome submodule for use by client-gnome,
as a temporary measure until the future vendoring of lrc into the two
clients.

With this change, the users of the Qt client ('jami' package) would
continue using 'jami-libclient' as a dependency, whereas for users of
the GNOME client ('jami-gnome') they would install and use the new
'jami-libclient-gnome' package.

Change-Id: I6aacb6c495c9a2953c328f2e9bfe6acd2b8cc645

Change-Id: I34fc48ac880a6673579f88b700b0baa5bd8cd585

Sébastien Blin authored 3 years ago and Amin Bandali committed 3 years ago

* docker/Dockerfile_opensuse-leap_15.3: The 'opensuse/leap:15.3'
docker image doesn't seem to have gcc11, so use gcc10 instead.
* packaging/rules/rpm/jami-gnome.spec: Unconditionally require
'make' for build, and require 'cmake' only where a recent enough
version is available in the distro (otherwise, we grab and use
external cmake e.g. using 'scripts/install-cmake.sh').

jami-packaging#111


Co-authored-by: Amin Bandali <amin.bandali@savoirfairelinux.com>
Change-Id: I5686f8e5d77eb8108b1581a33a2432006a1a688b

Maxim Cournoyer authored 3 years ago and Maxim Cournoyer committed 3 years ago

The top level tarball directory was renamed from ring-project to
jami-project in commit 21d9f320.

Automated via:
  $ git grep -l ring-project | xargs sed -i 's/ring-project/jami-project/g'

Change-Id: I4c0f01cca94d06c536fc1d75bf608e5728d41b31

Change-Id: Iacf9fd55b6a8cfc3521df1c10cb99192de8ae536

tumbleweed is broken since months (zypper crashes on the docker image)
and no issue remounted, also we support guix and snap for this platforms.

Change-Id: I0de908ba91eeeaf42c0d2599b3d69924fbcb7920

https: //git.jami.net/savoirfairelinux/jami-packaging/-/issues/111
Change-Id: I481e71d9650ce738c3211448aadd1d93478d84dc

For packages, jamid should be generated on Linux.

GitLab: #1312
Change-Id: I164a88617cbeb5ec79aa910054d5098942ea26d2

Change-Id: I4e08d256c651cdbc143c8315329931c6d95364c7

Change-Id: I54ef1d4adc7823fe3a38cd9ff7e7ee9af6a774bb

https://review.jami.net/c/jami-client-qt/+/19283 recently marked
Python 3 as a required build depdendency for building client-qt,
as it's needeed for generating 'resources.qrc' in build time.

Change-Id: Ib7eb3822ec5af5e4223d8a05b52d7cb5bb22e8d5

Maxim Cournoyer authored 3 years ago and Sébastien Blin committed 3 years ago

* packaging/rules/debian/rules (override_dh_auto_configure): Move
recipes to ...
(override_dh_auto_configure_build): ... here.  This is necessary as
the LRC now must find the share library of the daemon, hence it must
be built before the LRC configuration occurs.
<-DENABLE_LIBWRAP=true>: New option when configuring the LRC.
* packaging/rules/rpm/jami-libclient.spec (%build): Likewise.
* scripts/install.sh (lrc_cmake_flags): Likewise.
(OSTYPE): Remove variable.
(sharedLib): Remove variable.  The Jami daemon shared library is
needed when dynamically linking against it when libwrap is enabled.
* packaging/rules/rpm/jami-daemon.spec (%build): Drop the --disable-shared
option.
(%files): Register the libring.so dynamic library.
* packaging/rules/debian/rules (override_dh_auto_configure): Drop the
--disable-shared option.

GitLab: jami-packaging#101
Change-Id: Id1acaaf15a0f3d561c73bf34dde48f4eaf058eed

* packaging/rules/rpm/jami-daemon.spec (%files): Remove jami_contact.h header.

Change-Id: If13ca9d29a4bd65066857a9bce7e3b44379515cb

Change-Id: I9ed56eee9cc52a6423af3daafa3b57b494481e03

Change-Id: I4a03364f4062379fe8dc849ba02343d14de730f9

This give us more controls about bugs and anyway, we're going to
use Qt 6.2 for macOS support.

Change-Id: I78c17a9984248b4dad08ab2091532159335d4c97

Automated via: $ git grep -l dring | xargs sed -i 's/dring/jamid/g'

Change-Id: I67715a37e0fae42a0e4d9ce42bd01becc1ac77f5

This is a follow up to the f0fb8148ba7f453d73e31e1cece2dcffae68e878
commit (Use the PROGSHAREDIR macro to refer to the custom datadir) in
the daemon, that moved the ringtones from a hard-coded location of
/usr/share/ring/ringtones to $datadir/jami/ringtones.

* packaging/rules/rpm/jami-daemon.spec (%files): Adjust accordingly.
* scripts/install.sh (client_cmake_flags) <DRINGTONE_DIR>: Likewise.

Change-Id: Ia9d3403f5600a4ab4eefe28ee20611afc3f5e8b0

* build.py (run_run) <dring>: Adjust file name.
* packaging/rules/rpm/jami-daemon.spec (%install): Likewise.

Change-Id: Iedc4e0803bda19d139b29a4ccc669dcc8cc3fb9f

Workaround <https://bugreports.qt.io/browse/QTBUG-94800>.

This is to avoid out of memory conditions during the build, which
requires up to about 2 GiB of memory per parallel process.  There was
also a problem with how the MAKEFLAGS was passed, which led
qtwebengine to be built using all the CPU cores even when specifying a
lesser NO_CPUS value.

* packaging/rules/debian-qt/rules (min, max): New functions.
(NO_CPUS): Express in terms of max.
(AVAILABLE_MEMORY, MEMORY_REQUIRED_PER_CORE, COMPUTED_JOB_COUNT)
(JOB_COUNT, MAX_PARALLEL_BUILDS): New variables.
(override_dh_auto_build): Override to manually control job count.
Specify NINJAFLAGS for the Chromium build.
* packaging/rules/rpm/jami-libqt.spec (min, max, cpu_count)
(available_memory, computed_job_count, job_count): New macros.
(%build): Re-indent and use the above 'job_count' variable as
the number of parallel jobs.
(%install): Likewise.

Change-Id: I9134c1e63e92104a1da8435670e2919ce692040c

Change-Id: Ib5ad6c091560f7fc4ee9734ca283e78c90d9d769

* packaging/rules/rpm/jami-all.postinst (is_distribution_supported):
Make version agnostic.
(has_rpm, is_opensuse): New procedures.
(CAN_ADD_REPO_SOURCE, JAMI_REPO, ENDTAG): Delete variable.
(jami_repo_name, jami_repo_base_url): New variables.

Change-Id: I01ee72da39a1a8377ec70ae9dc3ef218d0837633

This follows commit 2afa99fd1 in the daemon.

* build.py (run_run) <dring>: Adjust file name.
* packaging/rules/rpm/jami-daemon.spec (%install): Likewise.  Hard
code the jamid binary location as /usr/libexec/dring, to not argue
with OpenSUSE Leap's %{_libexecdir}.

Change-Id: Iea6bf3cc6c4dce853f0b7c92861dfee7b8a07bbe

Change-Id: I07cf920ed99f460bffe1d8a16f3444706f4572c3

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: I18c33fc508d549b8935ddf16d55556a98ad9b6d1

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: Ied0febeca35f3d39724401669427bdfecc8f093c

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: Ib3e5a459f907928882bd9be4427fafe75f053080

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

also de-duplicate code

Change-Id: I3ea9fedec5b4520e74489f3f4e03a533130d9e83