[gst-devel] GStreamer on Windows

[Julien Moutte]

I tend to agree. A good VCPROJ and some global solution file holding all
the dependencies will probably be good enough for most people.

This also integrates pretty well with existing Windows developers workflow.

I think the OABUILD approach is very close to that and that's what we
use (somehow modified) to build Elisa and Fluendo codecs.

I will check what is the version of GStreamer core we depend on for our
codecs.

Cheers,

Julien Moutte,
FLUENDO S.A.



Vincent Torri wrote:
> On Mon, 30 Mar 2009, Edward Hervey wrote:
>
>   
>> On Sat, 2009-03-28 at 03:19 +0800, Alex Lee wrote:
>>     
>>> HI Julien, are you a developer of Elisa? I installed Elisa on my
>>> desktop (WindXP).
>>> But can not run the program. It says my graphical card is not power
>>> enough to
>>> support it or lack of graphical driver to run it correctly.
>>>
>>>
>>> Seems Elisa and Songbird use different ways to build GStreamer for
>>> Windows.
>>>       
>>  Most likely, yes. There's no unified way to do it. But SongBird's
>> build system is documented AFAIK.
>>     
>
> Imho, Windows developpers use mostly Visual Studio, so using what is 
> curently in the win32/ subdir is good enough. It's just a matter of 
> maintaining the vcproj file, having a good batch script to launch 
> everything automatically (we have that in the EFL, if you want, you can 
> look at it) and an installer for 3rd party libs. And finally, a script for 
> an installer (like NSIS) for the gstreamer packages. So most everything 
> can be automated, I think.
>
> Vincent Torri
>
> ------------------------------------------------------------------------------
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>