Commit 11881196 authored by Stephen Hutchinson's avatar Stephen Hutchinson Committed by Luca Barbato

avisynth: update documentation about the avisynth_c.h header

Signed-off-by: 's avatarLuca Barbato <lu_zero@gentoo.org>
parent a8c99205
...@@ -145,20 +145,25 @@ enable it. ...@@ -145,20 +145,25 @@ enable it.
@section AviSynth @section AviSynth
Libav can read AviSynth scripts as input. To enable support you need a Libav can read AviSynth scripts as input. To enable support you need a
suitable @file{avisynth_c.h} header to compile against. The header in suitable @file{avisynth_c.h} header to compile against. The header as
classic AviSynth's CVS repository is not compatible as it has not been provided by AviSynth+ is fully compatible. AviSynth 2.5 is not supported
updated to support AviSynth 2.6. AviSynth 2.5 is not supported by Libav. by Libav. Once you have the appropriate header, pass
Once you have the appropriate header, pass @code{--enable-avisynth} to @code{--enable-avisynth} to configure to enable AviSynth support.
configure to enable AviSynth support.
For Windows, supported AviSynth variants are For Windows, supported AviSynth variants are
@url{http://avisynth.nl, AviSynth 2.6} for 32-bit builds and @url{http://avisynth.nl, AviSynth 2.6} for 32-bit builds and
@url{http://avs-plus.net, AviSynth+ 0.1} for 32-bit and 64-bit builds. @url{http://avs-plus.net, AviSynth+ 0.1} for 32-bit and 64-bit builds.
The necessary @file{avisynth_c.h} header is the variant in the @file{extras/} @url{https://github.com/AviSynth/AviSynthPlus, AviSynth+'s git repository}
directory of the @url{https://www.videolan.org/developers/x264.html, x264} provides a GNU-style Makefile which can install just the headers using
source tree. For convenience, this header is also available from a @code{make install PREFIX=/install/prefix}.
@url{https://github.com/qyot27/avisynth_headers, temporary repository}
along with an installation routine. @float NOTE
When using AviSynth+'s installed headers, the user must also pass
the avisynth/ include directory to @code{--extra-cflags}. For example,
if the PREFIX given to AviSynth+'s Makefile was /usr/i686-w64-mingw32,
then the correct command would be
@code{--extra-cflags="-I/usr/i686-w64-mingw32/include/avisynth"}.
@end float
For Linux and OS X, the supported AviSynth variant is For Linux and OS X, the supported AviSynth variant is
@url{https://github.com/avxsynth/avxsynth, AvxSynth}. @url{https://github.com/avxsynth/avxsynth, AvxSynth}.
......
...@@ -27,16 +27,7 @@ ...@@ -27,16 +27,7 @@
/* Enable function pointer definitions for runtime loading. */ /* Enable function pointer definitions for runtime loading. */
#define AVSC_NO_DECLSPEC #define AVSC_NO_DECLSPEC
/* Platform-specific directives for AviSynth vs AvxSynth. /* Platform-specific directives for AviSynth vs AvxSynth. */
*
* avisynth_c.h needs to be the one provided with x264, as
* the one in AviSynth's CVS hasn't been updated to support
* 2.6's extra colorspaces. A temporary source of that header,
* installable from a GNU-style Makefile is available from
* github.com/qyot27/avisynth_headers -- AvxSynth doesn't
* require this kind of special treatment because like any
* standard *nix application, it installs its headers
* alongside its libs. */
#ifdef _WIN32 #ifdef _WIN32
#include <windows.h> #include <windows.h>
#undef EXTERN_C #undef EXTERN_C
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment