On 26/03/09 12:14, Andoni Morales wrote:
> I agree with the system wide install, I actually prefer to deploy
> GStreamer alongside with my application rather than using the
> GStreamer-Winbuild installer for example. But I think there should be
> a common build system, or at least, an extensible one to start with.
> For Fluendo it may sounds easy to build GStreamer, because you have a
> build system which is already there, but for those developers that
> want to start a project based on GStreamer on Windows it's not that
> easy because it's quite hard to compile GStreamer, mostly because of
> the external dependencies.
> If you have to decide, for example, between DirectShow, VLC or
> GStreamer to start a multimedia project on Windows, would you trust on
> a project that says: "GStreamer is cross-platform but we don't provide
> Windows binaries...You have to compile everything by your own and we
> don't even know which is the best method"?
> I really think the not having a common build system an a release of
> Windows pre-compiled binaries is kind of bad for GStreamer.
I also agree with having a system-wide install. Now that Qt is LGPL as
of 4.5.0, they should also be providing a standard library installer,
since it is silly for each application to install its own copy of the
same libraries again and again. I mention Qt because right now the only
backend supported on Windows is DirectShow, and it requires MSVC to
compile. A library installer for Qt could also potentially provide the
option of including the GStreamer libraries for Windows if such a thing
was standardized.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Locked
