Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version

From: "Helmut K. C. Tessarek" <tessarek@evermeet.cx>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>, Stephen Hutchinson <qyot27@gmail.com>,
	ffmpeg@gyani.pro
Subject: Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
Date: Tue, 15 Feb 2022 17:02:21 -0500
Message-ID: <05c94ae2-6490-40cc-d53e-6cdc0da64ac0@evermeet.cx> (raw)
In-Reply-To: <4bfdbb23-2124-dd38-c091-f25a1c616cbb@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2022-02-14 17:03, Stephen Hutchinson wrote:

> Should be fixed in 
> https://github.com/AviSynth/AviSynthPlus/commit/0e583378116c857372232e9886c5
99df2fb8da85
>
> 
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.

What is the solution?

I am compiling ffmpeg with AviSynthPlus-3.5.1 and my configure just errored
out with

ERROR: avisynth/avisynth_c.h avisynth/avs/version.h not found

Which makes sense because I don't have a version.h

Do I have to use the latest git version of AviSynthPlus. Is there a fix
coming for configure so that I can compile it as I did 2 days ago?

Cheers,
  K. C.

- -- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmIMIu0ACgkQvgmFNJ1E
3QCIRBAAt2kUYvy3+rMfskOBLISsDQm0epV4/RYWROqfUfzdn7ZWyUbshEGzEfSP
EuxYSgAXcvHhNYKhdgCLPFPTD5dqmxHR/9xYagelCEoEDY898DSOw0LFWyrBpak4
qvBtZP7Xt7bzFTvtoDAr+J4yrQCZN4M8gmQLhNqsh4nOawvmYlhONjXZ1eHX49Ki
9R3XFvm8jbdUqrvsil5+SNHtrf0734HYcZ5wcXNgulcfzdGDxvuGw1wS+XI9USQv
lyyom9AjgQaKZK/Kv68pVY4wLpkpVyO0KPYrfv3isNctwP69bNupRMc1BKKAPnhT
48FfSwZpU5d3CETdIXve/oX7VyWtYvNxbhqDCexlQICQgZEoWWgmUncxhVrQkMbF
e5N0mYhKTd2kJ3/31qaV/OfHqCznh2/BFzz3yeM+sH1NLj/bkAQQtCQ0I4jlW2jc
3sDxhtGmLtLXen1hnvAQLsEreT+jnlilhs1kTV8j4zZZ0rZexn7q6MFGMCR8Bmsb
7YZv0gY/1evuIvcjeviuPU9eYtbKqIeWqhIg+cRvmAJkqu1f2As0jl34Uuvw2agX
JdpfQ+x4R16wXlOYKTVu8hiX9l4pNvmeeNxUFLQSFs+Vz+bPVW9me4VCbVzbV+Dc
MwjxnhEOnarIcozsslvJLrQIwXnN+98RSpZJFmwRAM56w6QvZ1A=
=mifW
-----END PGP SIGNATURE-----
_______________________________________________
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".