Some comments <div class="gmail_quote">On Sat, Mar 14, 2009 at 1:56 AM, 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;"> Hi all, * GIT repositories I have finally taken time to cleanup my repositories and patches. All the repositories are located here (the ones starting with android-) : <a href="http://cgit.freedesktop.org/%7Ebilboed/" target="_blank">http://cgit.freedesktop.org/~bilboed/</a> These repositories share all the commits from the upstream official git repositories. glib : git://<a href="http://git.gnome.org/preview/glib" target="_blank">git.gnome.org/preview/glib</a> liboil : git://<a href="http://anongit.freedesktop.org/git/liboil" target="_blank">anongit.freedesktop.org/git/liboil</a> gst* : git://<a href="http://anongit.freedesktop.org/git/gstreamer/gst*" target="_blank">anongit.freedesktop.org/git/gstreamer/gst*</a> build : git://<a href="http://android.git.kernel.org/platform/build.git" target="_blank">android.git.kernel.org/platform/build.git</a> This makes it much easier to 'rebase' the android patches against a newer release or commit. 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. I have also modified the makefiles so that you no longer need to put them in a subdirectory in external, but directly in external (like all the other external projects). To check them out (once you've already checked out the full build system and done repo sync), do the following: $ cd external/ $ for i in glib liboil gstreamer gst-plugins-base gst-plugins-good gst-plugins-bad; do git clone git://<a href="http://anongit.freedesktop.org/%7Ebilboed/android-$i" target="_blank">anongit.freedesktop.org/~bilboed/android-$i</a> $i; done I have also got a 'build' repository, currently containing the prelink patch. You can check it out as follow: </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> $ cd build/ $ git remote add fdo git://<a href="http://anongit.freedesktop.org/%7Ebilboed/android-build" target="_blank">anongit.freedesktop.org/~bilboed/android-build</a> $ git checkout -b gst fdo/master </blockquote><div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> From that point on, just build android as you normally would and it will build/install the libraries/plugins. * Auto-generated .c/.h files Apart from the Android.mk files, the only thing required to compile several libraries/plugins are files that are generated by the standard autotools system at build/dist time. We have been thinking lately with Zaheer (who ported gstreamer to S60 [1]) that we should have a common location for all the .c/.h files generated at build/dist time. Currently we have some files for the win32 build system in win32/, but we need to make this more generic. Maybe have a generated/ directory in GStreamer containing those files. This could help solve a big chunk of the non-standard build systems. </blockquote><div>[Prajnashi S] Good. This is also a pain for me. I want to know how community handle above c/h in win release? Do they re-generate these files? </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> * plugins are not libraries All the plugins are currently using the build/core/<a href="http://shared_library.mk" target="_blank">shared_library.mk</a> makefile ... which results in those libraries ending up in /system/lib in the target. This is painful for many reasons. Plugins aren't 'standard' shared libraries: * They don't need to be prelinked * They are not imported at link time * When scanning for plugins (with GST_PLUGIN_PATH=/system/lib), we end up with a *lot* of non-plugins. They should be in a separate directory, like /system/gst-plugins. I'm currently investigating a modification to the build/ system to add the notion of plugins so that we can just use '<a href="http://plugin.mk" target="_blank">plugin.mk</a>' in every plugin directory and have the problems above solved. I'll keep you updated on this progress and will push it to my android-build git repository. * android-gst manifest The only thing left to bring everything together is to setup a manifest specifying all the afore-mentionned git repositories/branches. I'll look into it. * It runs on the G1 Yes, setup the build system as you would for the G1 [2], checkout the repositories/branches mentionned above, run 'make' from the toplevel directory and then flash your phone with it... and it works :) * Comments and feedback... ... are most welcome as usual ! Edward [1] <a href="http://zaheer.merali.org/articles/2009/03/11/gstreamer-port-to-s60/" target="_blank">http://zaheer.merali.org/articles/2009/03/11/gstreamer-port-to-s60/</a> [2] <a href="http://source.android.com/documentation/building-for-dream" target="_blank">http://source.android.com/documentation/building-for-dream</a> <div><div></div><div class="h5"> On Wed, 2009-03-04 at 23:17 -0800, bilboed wrote: > Hi all, > > I've been using the various patches to build GStreamer for Android > on the emulator and also on a dev G1 phone and it works great ! > > I've cleaned/splitted up the various patches into smaller commits in > git repositories I have locally. > > What I can do is push upstream the various commits that can actually > go upstream (like the parts to make libiconv/gettext optional for > glib). > > Then ideally, we should create some 'public' git repositories to > easily integrate all of this in a android build. There are many free > git hosting places available to host that (github, gitorious, or we > could even have those repositories at freedesktop alongside the > official gstreamer repositories !). But in the long run, we should > make this as easy as 'repo init -u <gstreamer-manifest-file> && make'. > > I'll try to put my repositories online as soon as possible. > > The easier we make it for people to try/use a gstreamer-based > android, the better it will be for us all (more feedback, more > contributors, maybe even tempting some companies to switch to > gstreamer for Android?) > > Comments welcome, > > Edward > > P.S. For those wondering, I'm one of the GStreamer developers, > therefore very interested to push this as hard as possible :) > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "prajnashi" group. To post to this group, send email to <a href="mailto:prajnashi@googlegroups.com">prajnashi@googlegroups.com</a> To unsubscribe from this group, send email to <a href="mailto:prajnashi%2Bunsubscribe@googlegroups.com">prajnashi+unsubscribe@googlegroups.com</a> For more options, visit this group at <a href="http://groups.google.com/group/prajnashi?hl=en" target="_blank">http://groups.google.com/group/prajnashi?hl=en</a> -~----------~----~----~----~------~----~------~--~--- </div></div></blockquote></div> -- -- Prajnashi S