Cristian Adam f34def3f64 Updated Visual Studio project files. пре 14 година
..
libvorbis f34def3f64 Updated Visual Studio project files. пре 14 година
libvorbisfile 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. пре 15 година
vorbisdec 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. пре 15 година
vorbisenc 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. пре 15 година
README dbda7087e8 Some more clarifications (hopefully not clear as mud :) пре 16 година
libogg.vsprops c5b59af00d Bumped libogg version to 1.1.4 and fixed dynamic compilation because of missing export function. пре 15 година
vorbis_dynamic.sln f34def3f64 Updated Visual Studio project files. пре 14 година
vorbis_static.sln f34def3f64 Updated Visual Studio project files. пре 14 година

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"