From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec: add bink2 video decoder
Date: Sat, 28 May 2022 12:39:38 +0200
Message-ID: <DB6PR0101MB22149E64A7067AB3366D982C8FDB9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20220524133650.18299-1-onemda@gmail.com>
Paul B Mahol:
> Signed-off-by: Paul B Mahol <onemda@gmail.com>
> ---
> configure | 1 +
> libavcodec/Makefile | 1 +
> libavcodec/allcodecs.c | 1 +
> libavcodec/bink2.c | 479 +++++++++++++
> libavcodec/bink2f.c | 1234 ++++++++++++++++++++++++++++++++
> libavcodec/bink2g.c | 1479 +++++++++++++++++++++++++++++++++++++++
The latter two files are not standalone files, but are included in
bink2.c. That means that bink2.d will contain bink2f.c and bink2g.c as
prerequisites for bink2.c. Yet if the code were to be changed so that
these files would no longer exist, then the build would fail if you have
an old bink2.d with bink2[fg]].c prerequisites, because make would not
know how to create these prerequisites.
To fix this, rename these files so that they are either templates or
headers.
> libavcodec/codec_desc.c | 7 +
> libavcodec/codec_id.h | 1 +
> libavformat/bink.c | 7 +-
> 9 files changed, 3206 insertions(+), 4 deletions(-)
> create mode 100644 libavcodec/bink2.c
> create mode 100644 libavcodec/bink2f.c
> create mode 100644 libavcodec/bink2g.c
>
_______________________________________________
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:[~2022-05-28 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:36 Paul B Mahol
2022-05-25 18:17 ` Tomas Härdin
2022-05-28 10:39 ` Andreas Rheinhardt [this message]
2022-06-01 8:09 ` Paul B Mahol
2022-06-01 8:57 ` Andreas Rheinhardt
2022-06-01 9:04 ` Paul B Mahol
2022-06-01 9:03 ` Andreas Rheinhardt
2022-06-01 9:45 ` Anton Khirnov
2022-06-01 8:20 Paul B Mahol
2022-06-01 10:41 Paul B Mahol
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=DB6PR0101MB22149E64A7067AB3366D982C8FDB9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
--to=andreas.rheinhardt@outlook.com \
--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