[gstreamer-bugs] [Bug 342564] Configure options causing compilation to fail

[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=342564

  GStreamer | gstreamer (core) | Ver: 0.10.x


Peter Kjellerstedt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #73658|0                           |1
        is obsolete|                            |




------- Comment #16 from Peter Kjellerstedt  2006-11-15 14:45 UTC -------
Created an attachment (id=76641)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=76641&action=view)
Maintain a consistent ABI when --disable-parse is used

The idea behind the #defines was to maintain the API even when --disable-parse
is used. This is the same as how it is done for a number of the other --disable
options.

However, I fully agree with you that we should also maintain the ABI. That way
it does not matter whether the version of GStreamer you build your application
against has been configured with --disable-parse or not, the application will
be able to use the functionality when it exists.

So, I have attached a new patch that should hopefully be acceptable as it
maintains both the API and ABI when --disable-parse is used.

One might consider adding a GST_PARSE_ERROR_UNSUPPORTED as well to be able to
tell the real reason why a pipeline could not be constructed.


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