GStreamer-devel

Re: GIT repositories

Classic

List

Threaded

4 messages Options

Prajnashi S

Re: GIT repositories

Some comments

On Sat, Mar 14, 2009 at 1:56 AM, Edward Hervey <[hidden email]> wrote:

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-) : http://cgit.freedesktop.org/~bilboed/

These repositories share all the commits from the upstream official
git repositories.
glib : git://git.gnome.org/preview/glib
liboil : git://anongit.freedesktop.org/git/liboil
gst* : git://anongit.freedesktop.org/git/gstreamer/gst*
build : git://android.git.kernel.org/platform/build.git

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://anongit.freedesktop.org/~bilboed/android-$i $i; done

I have also got a 'build' repository, currently containing the prelink
patch.
You can check it out as follow:

$ cd build/
$ git remote add fdo
git://anongit.freedesktop.org/~bilboed/android-build
$ git checkout -b gst fdo/master

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.

[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?

* plugins are not libraries

All the plugins are currently using the build/core/shared_library.mk
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 'plugin.mk' 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] http://zaheer.merali.org/articles/2009/03/11/gstreamer-port-to-s60/
[2] http://source.android.com/documentation/building-for-dream

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 [hidden email]
To unsubscribe from this group, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/prajnashi?hl=en
-~----------~----~----~----~------~----~------~--~---

--
-- Prajnashi S

------------------------------------------------------------------------------
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. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Edward Hervey

Re: GIT repositories

Administrator

On Sat, 2009-03-14 at 23:36 +0800, Prajnashi S wrote:

> Some comments
>
> On Sat, Mar 14, 2009 at 1:56 AM, Edward Hervey <[hidden email]>
> wrote:
>
> Hi all,
> * 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.
> [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?

We do it ... by hand :( It might make more sense to have those files
automatically generated when we run 'make dist', which is used to
generate the tarballs (so basically... when doing releases).
But it's been causing us some headaches in the past. We need to find a
smart solution for this.

Edward

>
>
> --
> -- Prajnashi S
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "prajnashi" group.
> To post to this group, send email to [hidden email]
> To unsubscribe from this group, send email to prajnashi
> +[hidden email]
> For more options, visit this group at
> http://groups.google.com/group/prajnashi?hl=en
> -~----------~----~----~----~------~----~------~--~---
>

------------------------------------------------------------------------------
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. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Prajnashi S

Re: GIT repositories

Hi, all
I just upload a new package gst-plugin-android to group, which include audio sink based on android's audio flinger.

http://prajnashi.googlegroups.com/web/gst-plugins-android-0.10.01.tgz?gda=tooxuVEAAAAmX5VkMcQNC9gap3c4jgFmuAwMIrpotOpbGpZoqMllA2IPRmyFx3eaggFGONDrkSuIgECKHgU_zy4mUbZCk4xDUwk_6Qi3BU8HCN0q6OYwM5VxXgp_nHWJXhfr7YhqVgA

Anyone can help me review it? BTW, how can it be released into up stream? Send a patch to community?

On Sat, Mar 14, 2009 at 11:43 PM, Edward Hervey <[hidden email]> wrote:

On Sat, 2009-03-14 at 23:36 +0800, Prajnashi S wrote:
> Some comments
>
> On Sat, Mar 14, 2009 at 1:56 AM, Edward Hervey <[hidden email]>
> wrote:
>
> Hi all,

> * 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.
> [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?

We do it ... by hand :( It might make more sense to have those files
automatically generated when we run 'make dist', which is used to
generate the tarballs (so basically... when doing releases).
But it's been causing us some headaches in the past. We need to find a
smart solution for this.

Edward

>
>
> --
> -- Prajnashi S

>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "prajnashi" group.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/prajnashi?hl=en
-~----------~----~----~----~------~----~------~--~---

Edward Hervey

Re: GIT repositories

Administrator

Hi,

As for the other modules, I created a git repository which I uploaded
to:
git://anongit.freedesktop.org/~bilboed/gst-plugins-android

Same as usual, you can just check it out in external/ and it will get
built.

I've already fixed the indentation, and will have a closer look soon
at what it's doing.

Edward

On Sat, 2009-03-14 at 23:46 +0800, Prajnashi S wrote:

> Hi, all
> I just upload a new package gst-plugin-android to group, which include
> audio sink based on android's audio flinger.
>
> http://prajnashi.googlegroups.com/web/gst-plugins-android-0.10.01.tgz?gda=tooxuVEAAAAmX5VkMcQNC9gap3c4jgFmuAwMIrpotOpbGpZoqMllA2IPRmyFx3eaggFGONDrkSuIgECKHgU_zy4mUbZCk4xDUwk_6Qi3BU8HCN0q6OYwM5VxXgp_nHWJXhfr7YhqVgA
>
> Anyone can help me review it? BTW, how can it be released into up
> stream? Send a patch to community?
>
> On Sat, Mar 14, 2009 at 11:43 PM, Edward Hervey <[hidden email]>
> wrote:
>
> On Sat, 2009-03-14 at 23:36 +0800, Prajnashi S wrote:
> > Some comments
> >
> > On Sat, Mar 14, 2009 at 1:56 AM, Edward Hervey
> <[hidden email]>
> > wrote:
> >
> > Hi all,
>
> > * 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.
> > [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?
>
>
> We do it ... by hand :( It might make more sense to have
> those files
> automatically generated when we run 'make dist', which is used
> to
> generate the tarballs (so basically... when doing releases).
> But it's been causing us some headaches in the past. We need
> to find a
> smart solution for this.
>
> Edward
>
> >
> >
> > --
> > -- Prajnashi S
>
> >
> > >
>
>
>
>
>
>
>
> --
> -- Prajnashi S
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "prajnashi" group.
> To post to this group, send email to [hidden email]
> To unsubscribe from this group, send email to prajnashi
> +[hidden email]
> For more options, visit this group at
> http://groups.google.com/group/prajnashi?hl=en
> -~----------~----~----~----~------~----~------~--~---
>