[vorbis-dev] Ogg Vorbis SDK.

Scott Velasquez scottv at gearboxsoftware.com
Sun Aug 24 18:33:17 PDT 2003



Tim:

You should also add a version resource to each MSVC project as well.  
I've done this for our game which is handy when you begin testing.

Another thing you might consider changing in the MSVC projects, is the 
dynamic linking against msvcr71.dll.  This forces users to distribute 
this .dll with their application when they could be statically linking 
against the library instead.

-scottv

Michael Smith wrote:

>On Friday 22 August 2003 13:05, tim.hutt at btinternet.com wrote:
>  
>
>>Hi, I've started making an Ogg Vorbis SDK, as per IRC topic instructions :)
>>
>>Some questions:
>>
>>Its just targetting MSVC right? Not borland/whatever?
>>    
>>
>
>Right. The code is meant to compile under other windows compilers, but we 
>don't have the resources to give full support for all of them, so we chose to 
>support the main/most popular one. 
>
>  
>
>>Should it install the headers/libraries in the msvc dir (c:\Program
>>Files\Microsoft Visual Studio\VC98\(Include|Lib)), or should it put them in
>>the same directory as the document (c:\Program Files\Ogg Vorbis
>>SDK\(Include|Lib)), and have the sample projects add thoses dirs to the
>>search path?
>>    
>>
>
>Should definately be in the SDK directory. 
>
>  
>
>>Secondly, is CVS meant to build? I got the nightly tarball, and I get these
>>unresolved symbols when building libvorbisfile dynamically: vorbisfile.obj
>>: error LNK2001: unresolved external symbol _vorbis_synthesis_halfrate
>>vorbisfile.obj : error LNK2001: unresolved external symbol
>>_vorbis_synthesis_halfrate_p
>>    
>>
>
>This is probably a missing export from the vorbis.def file - that file has to 
>list all the symbols that are exported from the library. Changes will 
>probably also be needed to vorbisfile.def and maybe ogg.def. This sort of 
>thing is precisely why we need someone with the tools and some knowledge of 
>windows programming to do the SDK stuff - all of this sort of thing is 
>win32-specific.
>
>  
>
>>Should I make this SDK from the last stable release rather than CVS?
>>    
>>
>
>No. The whole point of this is to update the SDK ready for the next release.
>
>  
>
>>Thirdly, Where should the DLLs go? %WINDOWS%\system32 ?
>>    
>>
>
>They shouldn't get automatically installed anywhere outside the SDK directory.
>
>
>Mike
>
>--- >8 ----
>List archives:  http://www.xiph.org/archives/
>Ogg project homepage: http://www.xiph.org/ogg/
>To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
>containing only the word 'unsubscribe' in the body.  No subject is needed.
>Unsubscribe messages sent to the list will be ignored/filtered.
>  
>

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.



More information about the Vorbis-dev mailing list