Hi, all<br>I just upload a new package gst-plugin-android to group, which include audio sink based on android's audio flinger.<br><br><a href="http://prajnashi.googlegroups.com/web/gst-plugins-android-0.10.01.tgz?gda=tooxuVEAAAAmX5VkMcQNC9gap3c4jgFmuAwMIrpotOpbGpZoqMllA2IPRmyFx3eaggFGONDrkSuIgECKHgU_zy4mUbZCk4xDUwk_6Qi3BU8HCN0q6OYwM5VxXgp_nHWJXhfr7YhqVgA">http://prajnashi.googlegroups.com/web/gst-plugins-android-0.10.01.tgz?gda=tooxuVEAAAAmX5VkMcQNC9gap3c4jgFmuAwMIrpotOpbGpZoqMllA2IPRmyFx3eaggFGONDrkSuIgECKHgU_zy4mUbZCk4xDUwk_6Qi3BU8HCN0q6OYwM5VxXgp_nHWJXhfr7YhqVgA</a><br>
<br>Anyone can help me review it? BTW, how can it be released into up stream? Send a patch to community?<br><br><div class="gmail_quote">On Sat, Mar 14, 2009 at 11:43 PM, Edward Hervey <span dir="ltr"><<a href="mailto:bilboed@gmail.com">bilboed@gmail.com</a>></span> wrote:<br>
<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"><br>
On Sat, 2009-03-14 at 23:36 +0800, Prajnashi S wrote:<br>
> Some comments<br>
><br>
> On Sat, Mar 14, 2009 at 1:56 AM, Edward Hervey <<a href="mailto:bilboed@gmail.com">bilboed@gmail.com</a>><br>
> wrote:<br>
><br>
> Hi all,<br>
</div><div class="im">> * Auto-generated .c/.h files<br>
><br>
> Apart from the Android.mk files, the only thing required to<br>
> compile<br>
> several libraries/plugins are files that are generated by the<br>
> standard<br>
> autotools system at build/dist time.<br>
><br>
> We have been thinking lately with Zaheer (who ported<br>
> gstreamer to S60<br>
> [1]) that we should have a common location for all the .c/.h<br>
> files<br>
> generated at build/dist time.<br>
> Currently we have some files for the win32 build system in<br>
> win32/, but<br>
> we need to make this more generic. Maybe have a generated/<br>
> directory in<br>
> GStreamer containing those files.<br>
> This could help solve a big chunk of the non-standard build<br>
> systems.<br>
> [Prajnashi S]<br>
> Good. This is also a pain for me.<br>
><br>
> I want to know how community handle above c/h in win release?<br>
> Do they re-generate these files?<br>
<br>
</div> We do it ... by hand :( It might make more sense to have those files<br>
automatically generated when we run 'make dist', which is used to<br>
generate the tarballs (so basically... when doing releases).<br>
But it's been causing us some headaches in the past. We need to find a<br>
smart solution for this.<br>
<br>
Edward<br>
<br>
><br>
><br>
> --<br>
> -- Prajnashi S<br>
<div><div></div><div class="h5">><br>
> ><br>
<br>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google Groups "prajnashi" group.<br>
To post to this group, send email to <a href="mailto:prajnashi@googlegroups.com">prajnashi@googlegroups.com</a><br>
To unsubscribe from this group, send email to <a href="mailto:prajnashi%2Bunsubscribe@googlegroups.com">prajnashi+unsubscribe@googlegroups.com</a><br>
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><br>
-~----------~----~----~----~------~----~------~--~---<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- Prajnashi S<br>