On 25 June 2014 18:23, Anton Lundin <glance at acc.umu.se> wrote: > On 25 June, 2014 - Tanu Kaskinen wrote: [...] >> I didn't do thorough review, but I'm OK with merging this. One wish, >> though: move the Android stuff out from src/Makefile.am to a separate >> file, that is then included by src/Makefile.am. That way I don't need to >> look at the black magic when I operate on src/Makefile.am. >> I'm okay with that, though if you keep looking at black magic, you might get annoyed enough to make it nicer. :p > I currently build PulseAudio with the ndk using a standalone tool chain > and that works great. > > My plan there is to finish off writing a OpenSL sink to be able to run > PulseAudio from a service and using a android device as a PulseAudio > sound server. This way PulseAudio runs ontop of a regular android > system. > > Last time i touched things i could build the whole chain without any > patching. > > If anyone is interested my build script is available at: > https://github.com/glance-/pulseaudio-android-ndk Nice work! Recapping from an earlier mail -- I like the androgenizer approach, because it can generate an Android.mk set that is usable to build NDK packages as well. I feel that this provides a more consistent build environment for your NDK as well (mostly compiler flags being consistent). That said, there are enough projects that work just fine crosscompiling directly for NDK packages for this to not be a big problem. (for those who aren't familiar with Android, my build changes are mainly useful to build PulseAudio as part of the Android OS image itself. The NDK I refer to above is for using this same system to build libpulse/PA for bundling in Android apps) -- Arun
