Cristian Adam1b85914e78Removed Release_SSE and Release SSE2 configurations. Changed Windows Mobile 5.0 configuration from "Pocket PC SDK 2 (ARMV4I)" to "Pocket PC SDK (ARMV4I)", version "2" was generated by versions of Windows Mobile 5.0 SDK which are no longer available on MSDN.
1b85914e78
Removed Release_SSE and Release SSE2 configurations. Changed Windows Mobile 5.0 configuration from "Pocket PC SDK 2 (ARMV4I)" to "Pocket PC SDK (ARMV4I)", version "2" was generated by versions of Windows Mobile 5.0 SDK which are no longer available on MSDN.
1b85914e78
Removed Release_SSE and Release SSE2 configurations. Changed Windows Mobile 5.0 configuration from "Pocket PC SDK 2 (ARMV4I)" to "Pocket PC SDK (ARMV4I)", version "2" was generated by versions of Windows Mobile 5.0 SDK which are no longer available on MSDN.
1b85914e78
Removed Release_SSE and Release SSE2 configurations. Changed Windows Mobile 5.0 configuration from "Pocket PC SDK 2 (ARMV4I)" to "Pocket PC SDK (ARMV4I)", version "2" was generated by versions of Windows Mobile 5.0 SDK which are no longer available on MSDN.
1b85914e78
Removed Release_SSE and Release SSE2 configurations. Changed Windows Mobile 5.0 configuration from "Pocket PC SDK 2 (ARMV4I)" to "Pocket PC SDK (ARMV4I)", version "2" was generated by versions of Windows Mobile 5.0 SDK which are no longer available on MSDN.
bec2629b54
Refactored Visual Studio 2005 project files. Added static, dynamic library support, and x64 platform support.
16 years ago
README
libvorbis has libogg as a dependency, you need to have libogg
compiled beforehand.
Lets say you have libogg and libvorbis in the same directory:
libogg-1.1.3
libvorbis-1.2.0
Because there is no automatic library detection you have to,
either:
1. Rename libogg-1.1.3 to libogg
2. Open libogg.vsprops with a text editor (even notepad.exe
will suffice) and see if LIBOGG_VERSION is set to the correct
version, in this case "1.1.3"