Hi, all After everything is stable, I think merge everything back to up stream is better. <div class="gmail_quote">On Sat, Mar 14, 2009 at 4:53 PM, Edward Hervey <<a href="mailto:bilboed@gmail.com">bilboed@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Fri, 2009-03-13 at 20:57 +0100, Farkas Levente wrote: > Edward Hervey wrote: > > I thought I'd also send this mail out for anybody interested in building > > GStreamer on android easily with git repositories. > > </div><div class="im">> > These repositories only contain, so far, the patches that were on the > > google groups site. I splitted them up into individual commits, in order > > to make it easier to push upstream what can be pushed upstream and leave > > alone what can't be pushed upstream. > > what's the reason why something can't be pushed upstream? > </div>* intrusive patches that need cleaner rewrites. For example : There's not i18n/libiconv/gettext on Android. Therefore we need to deactivate that everywhere in the modules we're using (glib/liboil/gst*).. but currently it uses non-standard #ifdef ANDROID. We should transform that into a clean way to disable i18n support for all those modules. * Android specific defaults. For example : We can use fbdevsink on the G1... but the default sink isn't the same as on unix. We could split that up in one upstream patch that makes it more modular to compile in a different default, and one patch (a one-liner non-upstream patch) that defines the default fb device on android. * Android-specific Makefiles and auto-generated files Android doesn't use the standard autotools build system, but has it's own build system. That means that we have to store files that are normally generated at configure time (config.h, *.in) or compile time (*-enum.[ch], gst parser (uses flex/bison), ...) and have Android.mk makefiles in all the correct directories. This is in fact a similar issue that was Zaheer has with the S60 port, and very close to what we do for the win32 builds. We need to find a clean/unified way to solve this for all non-autotools build systems/architectures. One could be switching away from autotools and using CMake (which can create Makefiles for various systems). Edward <div><div></div><div class="h5"> ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. <a href="http://p.sf.net/sfu/www-adobe-com" target="_blank">http://p.sf.net/sfu/www-adobe-com</a> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a> </div></div></blockquote></div> -- -- Prajnashi S