Quote:
Originally Posted by feisty2
mvtools relies on vsFilterScript headers rely on VapourSynth.h -> VapourSynth.h must be placed in the "Include" folder
mvtools relies on VSHelper.h relies on VapourSynth.h -> VapourSynth.h must be placed in the mvtools folder
you will need 2 copies of VapourSynth.h, one in the "Include" folder and one in the mvtools folder, that doesn't look nice 
|
The whole point of doing it how _Are states is that it means one does't have to copy a bunch of headers around and simply can rely on GCC, etc. to find it in the includes/headers search paths (for example under /usr/include). Unless you have some need of a specific version of those headers, you really shouldn't be including them the way you are. Plenty of other plugins don't.
For example in jackoneill's mvtools you'll see the headers are done this way:
Code:
#include <limits.h>
#include <stdexcept>
#include <string>
#include <unordered_map>
#include <VapourSynth.h>
#include <VSHelper.h>
#include "Bullshit.h"
#include "CPU.h"
#include "Fakery.h"
#include "MVAnalysisData.h"
#include "MVDegrains.h"
#include "MVFrame.h"
#include "Overlap.h"
https://github.com/dubhater/vapoursy...MVDegrains.cpp
This is the proper way you should be including the headers.