The path `${CMAKE_INSTALL_PREFIX}/lib/pythonM.N/site-packages` is
not Debian-specific, and will exist on too many systems where it
should _not_ be assumed to be the correct install path. (This is
causing Fedora and other `lib64`-using distros to install the
bindings into `/usr/lib/`, when they were previously being
installed into the correct `/usr/lib64/` location.)
Due to seeking optimizations the file can be closed and reopened. The packet's pointer becomes NULL in this case. This change ensures that packet's pointer is valid after seeking performed (if any).
* Remove a SWIG pragma from Frame.h (gcc warns on it)
* Place the equivalent %warnfilter in the openshot.i files
* Set openshot.i PROPERTY GENERATED_COMPILE_OPTIONS with flags to
disable warning spew in generated SWIG code, if -Wall is used
(Also, remove 'using namespace std' from Frame.h, and add std::
prefixes to necessary variables.)
Give the AppendDebugMethod() declaration a set of default values for
all parameters after the first. (It uses `""` and `-1.0`, which are
what callers were passing in anyway.) This way, callers have the
_option_ to eschew this kind of thing:
```
ZmqLogger::Instance()->AppendDebugMethod("Message", "start", start,
"length", length, "", -1, "", -1, "", -1, "", -1);
```
instead, they can use the functionally equivalent:
```
ZmqLogger::Instance()->AppendDebugMethod("Message", "start", start,
"length", length);
```
Passing meaningless args is the compiler's job, not the programmer's.