| author | Erik Walthinsen <omega@temple-baptist.org> | |
| Fri, 1 Feb 2002 22:37:16 +0000 (22:37 +0000) | ||
| committer | Erik Walthinsen <omega@temple-baptist.org> | |
| Fri, 1 Feb 2002 22:37:16 +0000 (22:37 +0000) | ||
| commit | 5684e131de866f11e856ad3d69988865f2cd0eaf | |
| tree | 5581bb7868d1aac348e64d627e95d922be6593ae | tree | snapshot (tar.xz tar.gz zip) |
| parent | bc24958dc88053e2e0042df9a486e802b4434ae0 | commit | diff |
Change soversion back to 0:0:0 and add use of -release flag for libtool.
Original commit message from CVS:
Change soversion back to 0:0:0 and add use of -release flag for libtool.
This means that any program linking against libgst will automatically have
the specific release of libgst encoded into it. This enforces the fact
that (for the moment), the API/ABI is changing rapidly enough that you
can't link against 0.3.2 originally and have it still work with 0.3.3. It
might be possible, but highly unlikely.
When we get closer to a stable API/ABI, in the 0.5.0 timeframe most likely,
we will start using soversions as recommended in the libtool docs. Then
we have to pay more attention to forward and backwards compatiblity, or
rather, we have to *start* paying attention <g>
Original commit message from CVS:
Change soversion back to 0:0:0 and add use of -release flag for libtool.
This means that any program linking against libgst will automatically have
the specific release of libgst encoded into it. This enforces the fact
that (for the moment), the API/ABI is changing rapidly enough that you
can't link against 0.3.2 originally and have it still work with 0.3.3. It
might be possible, but highly unlikely.
When we get closer to a stable API/ABI, in the 0.5.0 timeframe most likely,
we will start using soversions as recommended in the libtool docs. Then
we have to pay more attention to forward and backwards compatiblity, or
rather, we have to *start* paying attention <g>
| configure.ac | diff | blob | history | |
| gst/Makefile.am | diff | blob | history |