[gstreamer-bugs] [Bug 361675] New: Allow applications to use libxml2 and GStreamer even if the latter is configured using --disable-registry and --disable-loadsave

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=361675

  GStreamer | gstreamer (core) | Ver: HEAD CVS

           Summary: Allow applications to use libxml2 and GStreamer even if
                    the latter is configured using --disable-registry and --
                    disable-loadsave
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: pkj at axis.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
If I try to compile an application which uses both libxml2 and GStreamer, it
will fail if I have configured GStreamer to neither use the registry nor
loadsave.  This is because gstobject.h defines xmlNode to gpointer if
GST_DISABLE_LOADSAVE_REGISTRY is defined.  However, this definition will clash
with the real declaration in libxml2 when the application includes it.

Steps to reproduce:
1. Configure and build GStreamer with -disable-registry and --disable-loadsave
2. Build an application that uses both libxml2 and GStreamer


Actual results:
I get a compiler warning, and with -Werror that is fatal...


Expected results:
The compilation should succeed.

Does this happen every time?
Yes

Other information:


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email