[gstreamer-bugs] [Bug 498222] A couple of patches to improve configuration

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

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #16 from Peter Kjellerstedt  2007-11-21 11:55 UTC -------
Of course I will keep the liboil part patch in our local repository if it is
not accepted into the mainline, but I still fail to see why it should not be
accepted. Making it possible to build without liboil is in no way trying to
restrict the use of liboil in GStreamer plugins. It just removes an unnecessary
requirement for those who know they will not need any of the affected plugins. 

I believe the possibility do disable the requirement for liboil could be
beneficial for others as well. As I see it the --without-liboil option falls in
the same category as most of the other --disable-<feature> options available
for GStreamer. I.e., normal users should not use any of them, but for those of
us trying to build a smaller system, e.g., for an embedded product, it is
appreciated to be able to disable features you know you do not need. And with
the latest version of the patch, where one will have to make an active choice
by explicitly specifying --without-liboil to deactivate liboil support, one
should be aware of the implications of doing so. No one should be surprised
that by deactivating liboil it will deactivate plugins which requires it.


-- 
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=498222.