On 2013-09-03 16:05, Stephen Hutchinson wrote:
On Tue, Sep 3, 2013 at 9:21 AM, Luca Barbato <[email protected]> wrote:
On 03/09/13 15:17, Stephen Hutchinson wrote:
In preparation for the rewritten AviSynth demuxer, provide local
copies of AviSynth's and AvxSynth's requisite headers in
compat/avisynth/.
The versions of the headers are the same as those provided with x264
for consistency's sake.
---
compat/avisynth/avisynth_c.h | 879
+++++++++++++++++++++
compat/avisynth/avxsynth_c.h | 727
+++++++++++++++++
.../windowsPorts/basicDataTypeConversions.h | 85 ++
compat/avisynth/windowsPorts/windows2linux.h | 77 ++
4 files changed, 1768 insertions(+)
create mode 100644 compat/avisynth/avisynth_c.h
create mode 100644 compat/avisynth/avxsynth_c.h
create mode 100644
compat/avisynth/windowsPorts/basicDataTypeConversions.h
create mode 100644 compat/avisynth/windowsPorts/windows2linux.h
Aren't those headers provided by the respective projects?
Would make more sense just require them to be installed?
In AvxSynth's case, it's negligible since it does install these headers as
part of the normal 'make install' process. AviSynth as a project does not
because its source is MSVC-based, and would require the user to go fishing
to find the header and copy it to the right place.
Can you enlighten the poor fools like me about the difference(s) between
avisynth and avxsynth?
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
