[vorbis-dev] cvs changes

[Michael Smith]

>> We're basically going to have 3 libraries:
>> 
>> 1) libogg
>> 2) libvorbis
>> 3) libvorbisfile
>
>My encode API changes are going to result in a fourth lib, libvorbisenc.
Just 
>so people know.

I'm just wondering - is it worth having vorbisfile (and now vorbisenc) as
seperate libraries? Almost all users of libvorbis will be using at least
one of these, and including them doesn't negatively impact portability, nor
does it make a significant difference in library size. 

At the very least, vorbisfile/vorbisenc should remain within the same cvs
module as libvorbis (libogg being seperate makes sense - it's useful
independently of vorbis. The others aren't).

Michael

--- >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.