From: chloris-pale-green <chloris-pale-green@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: Jami
Date: Thu, 01 Jun 2023 16:22:23 +0200 [thread overview]
Message-ID: <20230601142223.FE4L3nDugogLFxdj5pFhGqYefjxK8k9qIxHjI-HpV4A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/4420#issuecomment-1572113459
Comment:
Renaming `ch_layout` to `channel_layout` in the code does not work. There seem to be different versions of the `ffmpeg` library with different APIs.
We currently have version 4.4 with [this API](https://ffmpeg.org/doxygen/4.4/structAVCodecContext.html). Struct `AVCodecContext` has a field `uint64_t channel_layout`.
[The `trunk` version](https://ffmpeg.org/doxygen/trunk/structAVCodecContext.html) has another kind of a field: `AVChannelLayout ch_layout`, which seems to be what the Jami code expects. It seems to first appear in `ffmpeg` 5.1. Perhaps an older version of Jami would build ...
In addition, they have switched to `sd-dbus`, which we don't have. Compiling without `dbus` support.
EDIT: compilation proceeds with a pre-FFmpeg 6 commit of `jami-daemon`, but it chokes on a header, belonging to [RESTinio](https://github.com/Stiffstream/restinio), which we don't have in our repos.
next prev parent reply other threads:[~2023-06-01 14:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4420@inbox.vuxu.org>
2019-10-29 0:35 ` Package Request: Ring voidlinux-github
2020-03-05 18:40 ` avoidr
2020-09-14 9:29 ` Mirodin
2021-04-25 9:48 ` autoteelar
2021-10-10 20:35 ` Package Request: Ring / Jami mika-nl
2021-10-10 20:39 ` mika-nl
2021-10-11 18:59 ` Chocimier
2021-10-13 18:22 ` mika-nl
2021-10-19 1:18 ` jgarte
2022-04-15 0:50 ` github-actions
2022-06-25 1:39 ` Package Request: Jami classabbyamp
2022-06-30 19:22 ` Idesmi
2022-06-30 21:49 ` ericonr
2023-06-01 6:41 ` chloris-pale-green
2023-06-01 10:01 ` chloris-pale-green
2023-06-01 10:02 ` chloris-pale-green
2023-06-01 14:00 ` chloris-pale-green
2023-06-01 14:05 ` chloris-pale-green
2023-06-01 14:22 ` chloris-pale-green
2023-06-01 14:22 ` chloris-pale-green [this message]
2023-06-01 14:22 ` chloris-pale-green
2023-06-01 15:00 ` chloris-pale-green
2023-08-26 14:14 ` HanoJing
2023-08-30 18:14 ` Chocimier
2021-10-16 2:51 [ISSUE] Package Request: jami jgarte
2021-10-16 7:53 ` notthewave
-- strict thread matches above, loose matches on Subject: below --
2021-04-25 9:48 [ISSUE] Package Request: Jami autoteelar
2021-04-25 13:19 ` notthewave
2021-04-25 13:20 ` notthewave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230601142223.FE4L3nDugogLFxdj5pFhGqYefjxK8k9qIxHjI-HpV4A@z \
--to=chloris-pale-green@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).