[gst-devel] GStreamer on Windows

[Carsten]

 From experience I can say that the hardest part of compiling GSteamer 
on Windows with the MSVC toolchain is to compile the dependent libraries.
Especially liboil since it uses gnu binutils to generate code. So it 
would be a good exercise to create a cmake wrapper for this lib just to 
see if it can be done. :)

Andoni Morales wrote:
> 2009/3/26 Julien Moutte <julien at moutte.net>:
>> I agree with you guys. Somehow the VCPROJ that we created are 50% of
>> that solution but there's still a need for something that would pull the
>> dependencies and provides VCPROJ for them as well (somehow what oabuild
>> does).
>>
>> We could try to setup a build server that would provide binaries dlls of
>> GStreamer core, base, good together with an installer and some set of
>> dependencies.
>>
>> Hard to figure out what's really needed though.
> 
> That is most of the work that I have been doing with GStreamer
> WinBuild, and part of the work that I proposed as a GSoC project. I
> think I am actually able to create some kind of script (or whatever
> does the same job) to provide a build environment with all the
> external dependencies needed to build GStreamer on Windows.
> I also proposed to migrate all that VCPROJ to Code::Blocks, because it
> is free software and because it can use several toolchains to make the
> build. As Julien Isorce said, CMake would be another option as it can
> generate Visual Studio projects, Xcode projects and CodeBlocks
> projects files.
> 
> Andoni
>> As Christian proposed the GStreamer get together at Guadec might be a
>> good opportunity to discuss that around some cervezas :)
>>
>> Cheers,
>>
>> Julien Moutte,
>> FLUENDO S.A.
>>
>> Julien Isorce wrote:
>>>
>>> 2009/3/26 Andoni Morales <ylatuya at gmail.com <mailto:ylatuya at gmail.com>>
>>>
>>>     2009/3/26 Julien Moutte <julien at moutte.net <mailto:julien at moutte.net>>:
>>>     >
>>>     > I think there are plenty of different Windows build strategies for
>>>     > GStreamer.
>>>     >
>>>     > I know we have one here at Fluendo for our codecs and for Elisa media
>>>     > center, Songbird probably have their own, Collabora has yet
>>>     another and
>>>     > there are probably many that I don't know about which we discover
>>>     today
>>>     > in that thread.
>>>     >
>>>     > Anyway as the packaging philosophy on Windows feels more like
>>>     > applications are self contained I'm not sure it makes sense to try and
>>>     > have a system wide install of GStreamer with a common build system.
>>>
>>>     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.
>>>
>>>     Andoni
>>>
>>>
>>> Hi,
>>>
>>> I agree with Andoni Morales.
>>> A common build system for gstreamer on windows is not destinated to a
>>> profesional use.
>>> As far I am concerned, at home I am using the installer
>>> (http://www.gstreamer-winbuild.ylatuya.es/doku.php?id=download). I can
>>> experiment gstreamer, develop plugins, and link my apps with gstreamer.
>>> But at the office we are compiling gstreamer on windows from scratch
>>> because we want to have the control on the compiler, and we can change
>>> anything we want in the source code, and we can have just the plugins we
>>> need. And several other reasons.
>>>
>>> I think it's the same thing on linux, for a profesional use, compagnies
>>> are compiling gstreamer them self.
>>> For home (public) usage, people are just doing apt-get install gstreamer.
>>>
>>> Maybe an "installer" is too much, but for home usage we still need
>>> binaries and dev packages.
>>>
>>> Julien
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> gstreamer-devel mailing list
>>> gstreamer-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>>
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
> 
> 
>