[gst-devel] libtool requirement for plugins
Thomas Vander Stichele
thomas at urgent.rug.ac.be
Sat May 24 21:50:02 CEST 2003
I still think this merits some discussion. I remember doing a lot of
work on the C++ handling to the point where I got everything working to
satisfaction. If this is not the case, at least provide some info so
that interested parties (for example, me) can help solve this.
This doesn't really sound like that good a reason at all to force this
requirement, especially knowing that libtool 1.5 has a slew of other
bugs that might bite us.
On Thu, 2003-05-22 at 22:37, Benjamin Otte wrote:
> Hi people,
> I'm about to upgrade the libtool requirement of the plugins to 1.5.
> I'm fully aware that neither Debain unstable nor Redhat 9 ship 1.5, but it
> is needed.
> The reason for this:
> Libtool prior to 1.5 used CC for doing the linking not caring if it was a
> C++ program/lib. Monkeymedia and Modplug however require a linked in
> libstdc++ if you compile with C++. But Forte barfs in that case because it
> doesn't know about that lib.
> So my choices were messing around with Makefiles and maybe even
> configure.ac or updating the libtool requirement. (remember: it's a cvs
> HEAD requirement for devs only, tarballs are not affected.)
> I decided for the cleaner way.
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
Dave/Dina : future TV today ! - http://davedina.apestaart.org/
<-*- thomas (dot) apestaart (dot) org -*->
I can't leave you alone
because you're so disarming
and I'm caught in the midst of you
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.rug.ac.be/
More information about the gstreamer-devel