On 3/12/20 4:46 AM, Marton Balint wrote:
Is it still required to include the headers in our source tree? AVISynth
was frowned upon in the past beacuse generally we do not allow headers
of external libraries in our tree.
If there is a way to completely remove the headers and keep the feature
On Wed, 11 Mar 2020, Stephen Hutchinson wrote:
AviSynth+ can now be used on Linux, which required some changes
to the headers.
As part of this, and to not cause issues with adding a new header,
correct the header inclusion guards to make FATE happy.
Is it still required to include the heade
AviSynth+ can now be used on Linux, which required some changes
to the headers.
As part of this, and to not cause issues with adding a new header,
correct the header inclusion guards to make FATE happy.
---
compat/avisynth/avisynth_c.h | 30 ++
compat/avisynth/avs/capi.h | 22 ++-
On Wed, Mar 11, 2020 at 06:50:15AM -0400, Stephen Hutchinson wrote:
> AviSynth+ can now be used on Linux, which required some changes
> to the headers.
> ---
> compat/avisynth/avisynth_c.h | 24
> compat/avisynth/avs/capi.h | 16 +
> compat/avisynth/avs/config.h | 46
AviSynth+ can now be used on Linux, which required some changes
to the headers.
---
compat/avisynth/avisynth_c.h | 24
compat/avisynth/avs/capi.h | 16 +
compat/avisynth/avs/config.h | 46 +--
compat/avisynth/avs/posix.h | 111 +++
com
As part of the update, it is now possible to test 32-bit GCC builds
of AviSynth+ with FFmpeg by using the AVS_WIN32_GCC32 define. Due to
different calling conventions between MSVC and GCC regarding 32-bit
Windows, this is unfortunately necessary.
---
compat/avisynth/avisynth_c.h | 503
