23rd March 2015, 01:13
|
#1040
| Link
|
|
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
Originally Posted by martin53
I'm sure there is reason in the things explained in that post, but:
Avisynth+'s header includes <avs/config.h>, <avs/capi.h> and <avs/types.h> which in turn include <avs/cpuid.h> and so on.
I feel this is not plugin writer friendly.
#include <...> in contrast to #include "..." makes success with the Filter SDK compiling instructions harder because it requires to further extend the standard library directories settings in the compiler.
Though I think I'd personally be able to manage that, and the files are on GitHub (easy to download), I still feel it's complicated and should not be like that. |
https://github.com/AviSynth/AviSynthPlus/pull/54
Quote:
|
At quick glance I couldn't find what happened to the GetVarDef function in the avisynth+ header, either, so I'll preliminarily stick to the standard Avisynth 2.6 one.
|
From https://github.com/AviSynth/AviSynthPlus/pull/53:
Code:
partial-2 GetVarDef is one of a group of several similar functions that seem to be gone in
avsplus, so don't bother with it.
|
|
|