What's the relation between OAH Build System and the GStreamer WinBuilds?

Asked by wl2776

I've recentrly found this site: http://www.gstreamer-winbuild.ylatuya.es

They state that "The GStreamer WinBuilds project goal is to provide precompiled GStreamer binary packages for Microsoft Windows, including a large collection of encoding/decoding plugins. It is based on the OSSBuild developing suite."

OAH Build system is noted in the Developer's links.

What is the relation between OAH Build System and that project?

Question information

Language:
English Edit question
Status:
Solved
For:
OAH Build Edit question
Assignee:
No assignee Edit question
Solved by:
wl2776
Solved:
Last query:
Last reply:
Revision history for this message
Haakon Sporsheim (ieei) said :
#1

As far as I know, they started with OABuild. OAHBuild is next generation of OABuild. You will need to ask the guys behind http://www.gstreamer-winbuild.ylatuya.es how they went on. Anyway, I'm pretty sure the just used OABuild as a starting point.

And I guess they are unrelated now, as they are focusing on GStreamer, and OAH Build tries to define one way of building all Open source software (using the Microsoft compiler/linker). (Which btw isn't too easy).

A side note:
OAHBuild sits on top of Visual studio and the build engine for C\C++ integration called VCBuild. As of Visual Studio 2010, which will be released in first half of 2010, VCBuild will be deprecated. So OAH Build will probably die out. I am currently moving over to the the next generation (current backend for building .NET apps) build system called msbuild. See https://launchpad.net/hsbuild

Revision history for this message
David Hoyt (dhoyt) said :
#2

I'm the maintainer of OSSBuild and work w/ the GStreamer WinBuilds team. They used OABuild initially and then we joined forces to work on OSSBuild. A lot of the work is similar to what you're providing in OAHBuild/HSBuild - we just do a mix of mingw (gcc) builds and MS builds w/ a focus on libs used by GStreamer. However the libs are usable for any purpose. We provide dev packages that include the .libs, headers, etc. We're working on a WiX-based system of merge modules for inclusion in Windows installers and as Haakon noted (b/c he's right), we'll eventually be dropping VCBuild support in favor of MSBuild. Anyway, sorry about the advertisement - just trying to explain the difference. Go to http://code.google.com/p/ossbuild/ for more details.

Revision history for this message
wl2776 (wl2776) said :
#3

Thanks.