[gstreamer-bugs] [Bug 520756] New: different registry backend configurations cause build errors

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=520756

  GStreamer | gstreamer (core) | Ver: HEAD CVS
           Summary: different registry backend configurations cause build
                    errors
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ensonic at sonicpulse.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


After some discussion on irc we concluded that instead of adding
GST_USING_BINARY_REGISTRY, we clean the mess:

a) Remove the _binary_{read|write}_cache declarations from gstregistry.h. They
could not have been used as they we're relying on a define from config.h. keep
the xml ones with a fixme for backwards compat.

b) Add empty stubs for the gst_registry_xml versions of the functions when
building the binary registry (in the end of gstbinraryregistry.c with a fixme)
so that they're still available in the ABI, to avoid breaking any *existing*
gst-python which might have been compiled to use them

todo:
* gst-python can provide stub wrappers
* core can deprecate the xml_{read|write}_cache for next release


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=520756.