> 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.
>
> - --
> regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Hello.
This probably will not help you, since I cross-compile under Ubuntu for target
Win10.
However, for the record I did this, not quite according to the git
instructions, and it did not abort:
# Changed dir from /home/u/Desktop/_working/workdir/x86_64/AviSynthPlus_git to
subfolder avisynth-build
cmake ..
-DCMAKE_TOOLCHAIN_FILE="/home/u/Desktop/_working/workdir/mingw_toolchain.cmake"
-G"Ninja"
-DCMAKE_INSTALL_PREFIX=/home/u/Desktop/_working/workdir/toolchain/x86_64-w64-mingw32/x86_64-w64-mingw32
-DHEADERS_ONLY:bool=on
ninja VersionGen -j 6
ninja install -j 6
Cheers
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
