From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] ffmpeg (5.1.2)
Date: Thu, 16 Feb 2023 18:48:21 +0000 [thread overview]
Message-ID: <85635018-02c6-52bf-82bb-7334b6d606b0@dronecode.org.uk> (raw)
In-Reply-To: <20230214181130.6c1d22a30592243e132c20a3@nifty.ne.jp>
On 14/02/2023 09:11, Takashi Yano via Cygwin-apps wrote:
> On Mon, 13 Feb 2023 18:28:37 +0000
> Jon Turney wrote:
>> On 06/02/2023 13:53, Takashi Yano via Cygwin-apps wrote:
>>> if [ ${all_codecs} = "yes" ]
>>> then
>>> cat <<_EOF_ > ffmpeg-wchar.patch
>>> --- origsrc/ffmpeg-5.1.2/libavcodec/mf_utils.h 2022-07-23 02:58:39.000000000 +0900
>>> +++ src/ffmpeg-5.1.2/libavcodec/mf_utils.h 2023-01-26 12:33:12.745550400 +0900
>>> @@ -29,6 +29,7 @@
>>> // mf*.h headers below indirectly include strmif.h.)
>>> #include <icodecapi.h>
>>> #else
>>> +#include <wchar.h>
>>> #define NO_DSHOW_STRSAFE
>>> #include <dshow.h>
>>> // Older versions of mingw-w64 need codecapi.h explicitly included, while newer
>>> _EOF_
>>> PATCH_URI+=" ffmpeg-wchar.patch"
>>> el
>>
>> This seems an odd way to write this. If possible, just apply the patch
>> unconditionally (I assume it doesn't break all_codec=no builds), and
>> treat it normally (i.e. keep it next to the cygport, list it in
>> PATCH_URI, so it gets placed into the source package.)
>>
>> If it's really necessary to only apply the patch in the all_codec=yes
>> case, use src_patch_apply_hook [1].
>>
>> [1]
>> https://cygwin.github.io/cygport/src_prep_cygpart.html#src_patch_apply_hook
>>
>> Otherwise, looks good.
>
> Patching conditionally is necessary because the target file
> is excluded from free-source tarball (ffmpeg_free_sources)
> if all_codecs != "yes".
Ah, I see.
> I revised the cygport file which uses src_patch_apply_hook()
> as you recommended.
Looks good.
prev parent reply other threads:[~2023-02-16 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:35 Takashi Yano
2023-01-20 15:04 ` Thomas Wolff
2023-01-20 15:28 ` Takashi Yano
2023-01-20 15:47 ` Thomas Wolff
2023-01-20 15:58 ` Takashi Yano
2023-01-20 20:05 ` Thomas Wolff
2023-01-22 12:20 ` Takashi Yano
2023-01-20 18:40 ` Jon Turney
2023-01-20 21:04 ` Brian Inglis
2023-01-22 12:25 ` Takashi Yano
2023-01-24 3:28 ` Takashi Yano
2023-02-04 16:45 ` Jon Turney
2023-02-05 8:40 ` Takashi Yano
2023-02-06 13:53 ` Takashi Yano
2023-02-13 18:28 ` Jon Turney
2023-02-14 9:11 ` Takashi Yano
2023-02-16 18:48 ` Jon Turney [this message]
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=85635018-02c6-52bf-82bb-7334b6d606b0@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).