[gst-devel] question on our libs

[Andy Wingo]

On Fri, 21 Dec 2001, Thomas Vander Stichele wrote:

> Hi everyone,

howdy.

> a) should our internal libraries be made available on the system in devel
> packages ? ATM I don't think they are, and if we want to encourage
> external plugin development (in external packages) and lib reuse we should
> probably allow for it.

yes, bundled in whatever package gst/ plugins go in. and have ext libs
depend on that package if they need libs. the libs are dynamically
linked, so they go in binary packages, not devel packages. the headers,
on the other hand, do have to be installed in dev packages.

> b) where would the libs themselves go, how should they be called ?
> should they go in /usr/lib/gst/ ? or in /usr/lib/gst-libs ?
> or /usr/lib/gst/libs ?

in ${prefix}/lib/gst. they are dynamically loaded in the same way
plugins are. afaik they go in the same dir as the plugins.

> 
> c) where would the headers go on the system ?
> /usr/lib/gst/gstaudio.h ?
> /usr/lib/gst-libs/gstaudio.h ?

this is what you and omega were talking about the other day, no?

my opinion goes like this:
${prefix}/include/gst/bytestream/bytestream.h

for bytestream, for example. headers do *not* go in libs though.

> d) how would they be included, both in included plugins and external
> plugins (the same way of course) ?
> #include <gst/gstaudio.h>
> #include <gst/audio/gstaudio.h>
> ...

this determines the structure of the directories, of course. so for my
example,

#include <gst/bytestream/bytestream.h>

> Also, if someone could tell me how I would handle decent EOS handling to
> afsrc, I'd be very grateful.  It would allow me to add afsrc to the
> testscript ;)

look at filesrc :)


best regards,

wingo.