[gstreamer-bugs] [Bug 550616] Add support for GObject-Introspection and provide GIR file with introspection data

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=550616
  GStreamer | gstreamer (core) | git

Colin Walters <walters> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |walters at verbum.org

--- Comment #13 from Colin Walters <walters at verbum.org> 2010-09-10 19:25:19 UTC ---
(In reply to comment #12)
> (From update of attachment 169975 [details])
> Thanks for the patches.
> 
> I think I'd like to make them conditional though, so g-i 0.6.x still works.
> 
> 
> >Use --identifier-prefix and --symbol-prefix as appropriate.
> 
> There's something I'm wondering about here: so, we have the GStreamer core lib,
> libgstreamer-0.10.so (in gstreamer/gst/), and then a bunch of other helper
> libraries, both in core (gstreamer/libs/gst/foo/, libgstfoo-0.10.so) and
> gst-plugins-base (gst-plugins-base/gst-libs/gst/bar/, libgstbar-0.10.so).
> 
> Before, with g-i 0.6.x we would use
> 
>   for the core library:
> 
>    --namespace Gst
> 
>   and for the helper libs in core/base:
> 
>     --namespace Gst{Base,Controller,Net,Audio,Video,etc.} \
>     --strip-prefix=Gst

So as of about 5 minutes ago I just readded --strip-prefix, since you were
using it correctly.  The problem arose due the heuristics we did in casefolding
which created messy bugs, i.e. if you specified --strip-prefix=gst, that would
sort of work in the old scanner, but WebKit had no way for us to know their
symbols look like web_kit, not webkit.  Anyways...

So I'll attach a new patch.

> Is this correct? Will this yield the same namespace etc. as before? (ie. we
> don't want e.g. GstBase or gst_base as identifier-prefix or symbol-prefix for
> the util libs, right?)

This should be identical, yes.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.