Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stephen Hutchinson <qyot27@gmail.com>
To: "Helmut K. C. Tessarek" <tessarek@evermeet.cx>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	ffmpeg@gyani.pro
Subject: Re: [FFmpeg-devel] [PATCH 3/3] configure: check avisynth header version
Date: Wed, 16 Feb 2022 19:55:42 -0500
Message-ID: <b296f3da-1e2e-e2d1-1c13-9e5e1071591e@gmail.com> (raw)
In-Reply-To: <0eac6e0d-a957-c239-2c58-dd0c096c7412@evermeet.cx>

On 2/16/22 1:25 PM, Helmut K. C. Tessarek wrote:
> 
> On 2022-02-16 02:37, Stephen Hutchinson wrote:
>> There is another option, basically what Gyan suggested earlier: grab the
>> release build of 3.7.1, fetch the extra headers from the Github repo,
>> then copy either all the contents of the tarball's /usr directory into
>> the system /usr directory (or wherever your working ${prefix} is), or
>> just the 'avisynth' directory into ${prefix}/include.  Then try FFmpeg
>> again.
> 
> This does not work. I compile static binaries. The filesonly tarball only
> has dylibs.
> 
> As I mentioned nefore:. 3 days ago everything worked fine. Now the ffmpeg
> builds are broken and I can no longer compile ffmpeg.
> 
> Is there any chancf you can add something to make it work again with 3.5.1
> which compiled withtout issues on macOS 10.14 and which I've been using
> since it was released.
> 
> 

FFmpeg dlopens AviSynth, it only needs the headers and doesn't try to 
link it.  It has never linked to AviSynth.

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.

After fetching the extra headers in that sequence of commands, copy the 
fixed-up /usr/include/avisynth in the -filesonly package to wherever it 
is on your system you point FFmpeg's configure to to see AviSynth's 
headers, whether that's the default /usr/local/include or /usr/include 
or somewhere in your build root.  You can completely omit copying the 
.dylibs and it won't care.

At this point, just use latest git, since that's where the HEADERS_ONLY 
fix resides:
git clone https://github.com/AviSynth/AviSynthPlus
cd AviSynthPlus
mkdir build && cd build
cmake -DCMAKE_INSTALL_PREFIX:PATH=${TARGET} -DHEADERS_ONLY=ON ../
make VersionGen install

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.

This all did expose a major problem with the version detection inside 
the frame properties initialization area in the demuxer, so that check 
needs to be simplified and not try to be so clever.  Between 
HEADERS_ONLY from AviSynth+-git and the simplifying patch*, which I'll 
need to push sometime in the next day or so, that should completely 
resolve the problem.

*http://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293128.html
_______________________________________________
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".

  parent reply	other threads:[~2022-02-17  0:55 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
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 [this message]
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=b296f3da-1e2e-e2d1-1c13-9e5e1071591e@gmail.com \
    --to=qyot27@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpeg@gyani.pro \
    --cc=tessarek@evermeet.cx \
    /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