opusfile library for Windows is not helpful to Windows developers
There are three bugs in the Opusfile library for windows (version 0.6, built 6/11/2014):
- It does not include .lib link libraries for Visual Studio, thus cutting out about 99.9% of all Windows developers (that number may be an under-estimate). GCC-generated .a linkable libraries are not useable from Visual Studio, and cannot be converted to Visual Studio .lib format using included MSSDK tools like "dumpbin" or "lib" or "link."
There are free-as-in-beer versions of Visual C++ Express, so cost should not be an impediment to solving this.
The included opusfile.h header is not sufficient to use the library -- it also includes files ogg/ogg.h and opus_multistream.h, which are not included.
The includes of files relative to opusfile.h are done with <> brackets, not "" quotes. This means that you expect the ogg.h and opus_multistream.h headers to be part of the standard system includes, which is not generally true on Windows systems. Instead, this file should include those header files with "" includes, to signal that the include path is relative to wherever opusfile.h is located, which would enable a self-contained download of this library to be created.
(Note that opusfile.h itself can be included with relative includes, with #include "opusfile-0.6-win32/opusfile.h", or with some other mechanism -- you should not assume opusfile.h is installed in the system include path.
Separately, the build instructions say "build doing ./configure and make," which is not at all helpful to 99.9% (or more) of Windows developers. If you want to support Windows, please actually do so. Else, just drop the support. The current library is not helpful and is just bad marketing for the opusfile library.