[gst-devel] Re: [gst-cvs] dlehn gst-plugins: gst-plugins/

[David I. Lehn]

* Thomas Vander Stichele <thomas at urgent.rug.ac.be> [20021003 03:33]:
> could you send a small mail detailing what this changes in practice for 
> any of the libs ?
> 
> > Module:         gst-plugins
> > 
> > Log message:
> > use proper version prefix
> > use pkgconfig to find libdv
> > 
> > Modified files:
> >     .               : configure.ac
...
> >  dnl when going to/from release please set the nano (fourth number) right !
> >  dnl releases only do Wall, cvs and prerelease does Werror too
> > -AS_VERSION(gst-plugins, GST_PLUGINS, 0, 4, 1, 1, GST_ERROR="-Wall", GST_ERROR="-Wall -Werror")
> > +AS_VERSION(gst-plugins, GST_PLUGINS_VERSION, 0, 4, 1, 1, GST_ERROR="-Wall", GST_ERROR="-Wall -Werror")
> >  AM_INIT_AUTOMAKE($PACKAGE,$VERSION)
> >  AS_LIBTOOL(GST_PLUGINS, 0, 0, 0, yes)
> >  

Sure,

The AS_VERSION() macro defines some version stuff based on that second
parameter, such as FOO_MAJOR, FOO_MINOR, etc.  The AS_LIBTOOL() macro
expects vars of the form FOO_VERSION_MAJOR, FOO_VERSION_MINOR, etc.  It
uses these to constuct the value of FOO_LT_LDFLAGS and/or
FOO_LIBVERSION.  So... you need to pass in FOO_VERSION to AS_VERSION()
to get things setup properly.  This is how it's done in the core.

The reason those AS_LIBTOOL() defined vars are needed now is that the
gstgconf code should be built as a library and not a plugin.  So it
needs to have versioning info of some sort and might as well use the
same methodology as the core to version it.

Seem reasonable?

-dave