From: Stephen Hutchinson <qyot27@gmail.com>
To: ffmpeg@gyani.pro, ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
Date: Mon, 14 Feb 2022 17:03:20 -0500
Message-ID: <4bfdbb23-2124-dd38-c091-f25a1c616cbb@gmail.com> (raw)
In-Reply-To: <bc1bad55-8f88-85ad-61ef-873755848c96@gyani.pro>
On 2/14/22 6:56 AM, Gyan Doshi wrote:
>
>
> On 2022-02-14 05:04 am, Stephen Hutchinson wrote:
>> On 2/8/22 6:02 AM, Stephen Hutchinson wrote:
>>> The headers from version 3.7.1 are needed in order to support
>>> parsing of frame properties. avs/version.h has been generated
>>> as part of the AviSynth+ build process for a long time, but was
>>> never installed with the includes until version 3.7.1a. Checking
>>> for the presence of avs/version.h might have been sufficient,
>>> but a version check mechanism might be useful in the future.
>>>
>>> This does not change the version compatibility with the library
>>> itself; previous 3.x versions of AviSynth+ as well as AviSynth 2.6
>>> can still be used with the demuxer.
>>>
>>> Signed-off-by: Stephen Hutchinson <qyot27@gmail.com>
>>> ---
>>> configure | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> index 493493b4c5..544d341b49 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -6508,7 +6508,9 @@ for func in $COMPLEX_FUNCS; do
>>> done
>>> # these are off by default, so fail if requested and not available
>>> -enabled avisynth && require_headers "avisynth/avisynth_c.h"
>>> +enabled avisynth && { require_headers
>>> "avisynth/avisynth_c.h avisynth/avs/version.h" &&
>>> + { test_cpp_condition
>>> avisynth/avs/version.h "AVS_MAJOR_VER >= 3 && AVS_MINOR_VER >= 7 &&
>>> AVS_BUGFIX_VER >= 1 || AVS_MAJOR_VER >= 3 && AVS_MINOR_VER > 7 ||
>>> AVS_MAJOR_VER > 3" ||
>>> + die "ERROR: AviSynth+ header
>>> version must be >= 3.7.1"; } }
>>> enabled cuda_nvcc && { check_nvcc cuda_nvcc || die "ERROR:
>>> failed checking for nvcc."; }
>>> enabled chromaprint && require chromaprint chromaprint.h
>>> chromaprint_get_version -lchromaprint
>>> enabled decklink && { require_headers DeckLinkAPI.h &&
>
> The advice for AVS+ dlopen consumers is to only build and install AVS+
> headers.
> That does not install version.h and arch.h which are only built with the
> binary artifacts, not with -DHEADERS_ONLY.
>
> For my Windows build, I just manually copied and renamed the template
> files to make configure succeed.
>
> Regards,
> Gyan
Should be fixed in
https://github.com/AviSynth/AviSynthPlus/commit/0e583378116c857372232e9886c599df2fb8da85
with the caveat (noted in AviSynth+'s README.md) that the `make install`
step now needs to explicitly invoke the VersionGen target, `make
VersionGen install`. I fiddled with it for a while, but I couldn't get
the install process to invoke it automatically.
Related, the older GNUmakefile method is not set up to generate
version.h and arch.h (especially considering both of those use *.cmake
scripts), so it's now pretty clearly deprecated.
_______________________________________________
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-02-14 22:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 11:02 [FFmpeg-devel] [PATCH 0/3] avformat/avisynth: support frame properties Stephen Hutchinson
2022-02-08 11:02 ` [FFmpeg-devel] [PATCH 1/3] avisynth: corrected interlace detection Stephen Hutchinson
2022-02-13 23:33 ` Stephen Hutchinson
2022-02-08 11:02 ` [FFmpeg-devel] [PATCH 2/3] avisynth: use AviSynth+'s frame properties to set various fields Stephen Hutchinson
2022-02-13 23:34 ` Stephen Hutchinson
2022-02-19 20:39 ` Andreas Rheinhardt
2022-02-19 21:41 ` [FFmpeg-devel] [PATCH 1/2] avformat/avisynth: remove unused variable 'frameprop' Stephen Hutchinson
2022-02-19 21:41 ` [FFmpeg-devel] [PATCH 2/2] avformat/avisynth: make sure framedata variable is initialized Stephen Hutchinson
2022-02-19 22:45 ` Andreas Rheinhardt
2022-02-20 0:05 ` Stephen Hutchinson
2022-02-20 0:09 ` [FFmpeg-devel] [PATCH] avformat/avisynth: remove framedata variable Stephen Hutchinson
2022-02-23 18:04 ` Stephen Hutchinson
2022-02-23 18:03 ` [FFmpeg-devel] [PATCH 1/2] avformat/avisynth: remove unused variable 'frameprop' Stephen Hutchinson
2022-02-19 21:45 ` [FFmpeg-devel] [PATCH 2/3] avisynth: use AviSynth+'s frame properties to set various fields Stephen Hutchinson
2022-08-24 17:04 ` Steinar Apalnes
2022-08-25 0:11 ` Stephen Hutchinson
2022-08-25 7:46 ` Steinar Apalnes
2022-09-04 19:14 ` Stephen Hutchinson
2022-02-08 11:02 ` [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version Stephen Hutchinson
2022-02-13 23:34 ` Stephen Hutchinson
2022-02-14 11:56 ` Gyan Doshi
2022-02-14 22:03 ` Stephen Hutchinson [this message]
2022-02-15 22:02 ` Helmut K. C. Tessarek
2022-02-15 23:55 ` Stephen Hutchinson
2022-02-16 1:33 ` Helmut K. C. Tessarek
2022-02-16 3:50 ` Stephen Hutchinson
2022-02-16 5:10 ` Helmut K. C. Tessarek
2022-02-16 7:37 ` Stephen Hutchinson
2022-02-16 18:25 ` Helmut K. C. Tessarek
2022-02-16 23:04 ` hydra3333
2022-02-16 23:13 ` Helmut K. C. Tessarek
2022-02-17 0:55 ` Stephen Hutchinson
2022-02-17 22:19 ` Helmut K. C. Tessarek
2022-02-18 0:21 ` Stephen Hutchinson
2022-02-13 17:48 ` [FFmpeg-devel] [PATCH 0/3] avformat/avisynth: support frame properties Stephen Hutchinson
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=4bfdbb23-2124-dd38-c091-f25a1c616cbb@gmail.com \
--to=qyot27@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg@gyani.pro \
/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