From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v28 1/2] avcodec/evc_encoder: Provided support for EVC encoder
Date: Thu, 09 Nov 2023 15:12:19 +0200
Message-ID: <43AE2213-FE98-43B8-A936-2727573E3E48@remlab.net> (raw)
In-Reply-To: <009801da12f5$cdfe8d30$69fba790$@samsung.com>
Hi,
Le 9 novembre 2023 12:16:28 GMT+02:00, "Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com> a écrit :
>Hi,
>
>Both, the implementation of the EVC encoder and decoder for FFmpeg depend on external libraries (at least for now). They are just wrappers using external libraries, namely libxeve (encoder implementation) and libxevd (decoder implementation).
>
>The EVC defines two profiles: the "Baseline Profile" and the "Main Profile".
>For the encoder and decoder, libraries can be built for both main and baseline profiles as follows:
>cmake .. -DSET_PROF=BASE && make && make install
>cmake .. -DSET_PROF=MAIN && make && make install
I guess that the point is that Linux distributions want a single library for all profiles. You can't have two libraries with the same name, obviously. And you also don't want two libraries with different SO names, but the same/conflicting exported symbols and same header and function names.
You make it sound like you have to choose a profile at compilation time, which sounds lazy to stay polite.
Br,
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-11-09 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230919113442eucas1p2ab81a8bbba4e1b5b79863ab4e23243b3@eucas1p2.samsung.com>
2023-09-19 11:34 ` Dawid Kozinski
2023-10-18 13:16 ` Neal Gompa
2023-11-09 10:16 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-11-09 13:12 ` Rémi Denis-Courmont [this message]
2023-11-12 0:36 ` Neal Gompa
2023-11-20 15:00 ` James Almer
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=43AE2213-FE98-43B8-A936-2727573E3E48@remlab.net \
--to=remi@remlab.net \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git