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

Helmut K. C. Tessarek tessarek at evermeet.cx
Fri Feb 18 00:19:16 EET 2022


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



On 2022-02-16 19:55, Stephen Hutchinson wrote:
> FFmpeg dlopens AviSynth, it only needs the headers and doesn't try to
> link it.  It has never linked to AviSynth.

This I find strange. dlopen is rather useless when you create static
binaries unless you want to ship X diffreent dylibs or SOs with the binary.

There's also no static version of frei0r. Very annoying.

> If 3.5.1 is working (and by that I assume you mean you're opening a
> Version() script in FFplay and it's showing you the video clip with the
> version and copyright information), then libavisynth.dylib is somewhere
> on your DYLD_LIBRARY_PATH, and you could just as easily set
> DYLD_LIBRARY_PATH to the /usr/lib directory in the -filesonly package and
> that Version() script will start reporting 3.7.1 instead.

It's definitely not working, since I don't ship any dylibs. I always thought
3.5.1 li9nked a static lib, but I checked. It does not.

Even if I wanted to I couldn't ship any dylibs, since I can't build
AviSynthPlus on macOS 10.14.

> At this point, just use latest git, since that's where the HEADERS_ONLY
> fix resides: And HEADERS_ONLY is exactly what it says on the tin: it only
> sets CMake to install the headers, and stops it from building the
> library, which wouldn't get linked to anyway.

Ok, this worked. I was able to compile ffmpeg again. At least now I know
that avisynth won't work with static banaries unless people install dylibs
themselves.

- -- 
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-----

iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmIOyeMACgkQvgmFNJ1E
3QDS7g//VMqsrxTK7uC/N65ydY4MvEOhqZJcAJqTtmyDStqWrgLOr1zeTutu359I
G3ah7M9/BYnZVwiVDypLgvRBNLR9F7bgv4CdG+VaV2M5Ljuv8yqiLG4ohbY6BcC3
6Da+CV2X7ylDunnGuI+jFQ2+E/DrP6lJRvMweotsLZvluTU3PCGNIpOHxt6SLq1S
eN9V9UluOZT/+YYk4XOWiWpYucDBvZbRUCfcZtckKESRwpRrZCMRO9ExJXdRvNRr
gyy0EIIDqAHhoEyP7RkadFuHOco4Beppalru4+UEvSwWae2B2pr8pwfFh8RUvXk6
75SNWOzfQoyndvEQR4jDv3PLFswWMv8upeGoGJHsb0NcOY31Uk0Y58kMzbzDC/eT
uK8Jp5+5Gx+uOG8k/dvKQK5TllnelApSFaVbyeuzrcRnphVi6ad6OtdSPBaWKjdD
BljKMkAr/plpCsfuJ9THdXIo3Q0qwoXC4l/fL8Q35uiqYcOOa8Ax/FePe/srMDnp
vxtDBBzo+8nA2305OUtErEAq0XhgCnSvOyfzoXx4fWxF39N15tU2VKTDoPAkjx9A
5dx/753wos5HewC5WeESzKCALXWu5l9r/sV/Jih8rf+8YXzJweMjso+Ca2B8e7bv
2nWvPMAcqtByklBnsVpkV3QTGDaxb2c1E4XhEoTchKjVKeFzrQo=
=5yaK
-----END PGP SIGNATURE-----


More information about the ffmpeg-devel mailing list