[vorbis-dev] Library issues (BOUNCE vorbis-dev@xiph.org: Non-member submission from [rob@emusic.com]) (fwd)

[Michael Smith]

>Sender: robert at emusic.com
>
>I just brought the FreeAmp codebase up to speed with the latest Vorbis
>source. In doing so, I've come up with the following questions:
>
>1) There is libvorbis.a and vorbisfile.a. Why is vorbisfile.a not
> libvorbisfile.a? This presents problems when FreeAmp attemps to see if
> the vorbis libs are installed on the target machine. The source tarball
> that I just posted requires the lib to be installed in /usr/lib. Not a
> great solution. If vorbisfile.a were libvorbisfile.a I could just have
> configure do a AC_CHECK_LIB and then have the vorbis plugin be compiled
> with -lvorbis and -lvorbisfile

There isn't any particular reason for this. If nobody objects, it would
seem entirely reasonable to change it to libvorbisfile.a - leave this
floating for a couple of days, if we don't hear anything against this, I'd
say go ahead and change it (or bug someone else to - I don't know if you
have CVS access)

> 
>2) Are there any plans for creating shared libs?

I imagine people will eventually. I would strongly suggest that people NOT
distribute libvorbis in shared library form until 1.0, however. The API is
stable, but I would expect binary incompatibilities to creep in (I think
some needed additions to the comment interface, for example, will break
binary compatibility, though not source compatibility)

>
>What is the overall philosophy about the libraries? Should we include
>the vorbis source inside of FreeAmp and avoid these problems? I'd prefer
>to have shared libs...

Shared libs are a 1.0 thing, I'd say. Anything before then is more likely
to cause problems than anything else.

Michael

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/