xiph/vorbis

Cristian Adam fe70b7fc3c Fixed project configuration which referenced two CRT versions in output binaries.		il y a 14 ans
..
libvorbis	fe70b7fc3c Fixed project configuration which referenced two CRT versions in output binaries.	il y a 14 ans
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.	il y a 15 ans
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.	il y a 15 ans
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.	il y a 15 ans
README	5f768cd31b Added Visual Studio 2008 project files	il y a 16 ans
libogg.vsprops	c5b59af00d Bumped libogg version to 1.1.4 and fixed dynamic compilation because of missing export function.	il y a 15 ans
vorbis_dynamic.sln	5f768cd31b Added Visual Studio 2008 project files	il y a 16 ans
vorbis_static.sln	5f768cd31b Added Visual Studio 2008 project files	il y a 16 ans

		
				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"