On Thu, 2009-07-02 at 16:20 -0400, Paul Davis wrote:
> On Thu, Jul 2, 2009 at 3:16 PM, John Swenson<
johnswenson1@...> wrote:
>
> > 1) Version control. Will the plugin need to be recompiled when the server is
> > recompiled? If yes, some form of strong versioning is essential to make sure
> > the correct version of the plugin is used. If the same plugin can be used
> > with multiple server instantiations, when do you have to have a new one?
>
> they communicate using an API with opaque data structures. only if the
> API is changed would they need recompiling. and anyway, these
> "plugins" (there would likely be 1-3 of them) would really be
> considered part of JACK - packagers might bundle them separately but
> they would be built from the same source release and would depend on
> each other.
Just in the same way that in a properly packaged distribution installed
development packages have to match the original package (and yes, both
are compiled at the same time from the same source).
-- Fernando
> > 2) How to find the plugin. Will the plugin have to live in a specific
> > location (such as in the same directory as the server) or is a search path
> > necessary. If using a search path is it a new path that has to be setup
> > somehow, or will it "borrow" an existing search path?
>
> we have to do this for backends ("drivers") now - it works, and an
> almost identical system would happen for control plugins. backends
> live in a known directory ($libdir/jack) and there is no search path
> involved.
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
