yes, I have done these. Having included the last one BUILD_WITH_ALSA_UTILS :=true, I am able to build the alsa_aplay, alsa_mixer and alsa_ctl executables.
The problem is the linux kernel runs the file system with data and system, taken from the SDK 1.0 of the android emulator. But it does not even boot the data and system folders taken from the latest android git. When init.android is run, I get to the screen of ANDROID but the desktop of Android does not appear. Are there any compatibility issues? Thank you. On May 19, 8:41 pm, Ravishankar Haranath <[email protected]> wrote: > I hope you have used the following; > BOARD_USES_GENERIC_AUDIO := false > BOARD_USES_ALSA_AUDIO := true > BUILD_WITH_ALSA_UTILS := true > > in your BoardConfig.mk file!! > > On Tue, May 19, 2009 at 5:17 PM, Claw <[email protected]>wrote: > > > > > > > Thank you, this is what I did. I have another problem now. > > > I try running the built alsa_aplay, alsa_ctl on the device but with no > > success. The device simply does nothing. I am using the data and > > system folders taken from emulator SDK 1.0. My kernel is a is a 2.5.26 > > which is not take from android git. > > > Even when I say "alsa_ctl -h" nothing is displayed. This is quite > > strange. Do I have to build the alsa_ctl with older GIT files only? > > > On May 16, 10:10 am, crazygenie <[email protected]> wrote: > > > comment out typedef for off64_t in external/alsa-utils/android/ > > > aconfig.h and retry. > > > > On May 14, 3:56 pm, Claw <[email protected]> wrote: > > > > > All, > > > > I have the aplay.c which is taken on 14th May 2009. This does not > > > > build for arm. > > > > > Here is the faliure message: > > > > > In file included from external/alsa-utils/aplay/aplay.c:49: > > > > external/alsa-utils/android/aconfig.h:7: error: conflicting types for > > > > 'off64_t' > > > > bionic/libc/include/sys/types.h:68: error: previous declaration of > > > > 'off64_t' was here > > > > external/alsa-utils/aplay/aplay.c:113: warning: overflow in implicit > > > > constant conversion > > > > external/alsa-utils/aplay/aplay.c: In function 'test_wavefile': > > > > external/alsa-utils/aplay/aplay.c:859: warning: comparison between > > > > signed and unsigned > > > > external/alsa-utils/aplay/aplay.c: In function 'set_params': > > > > external/alsa-utils/aplay/aplay.c:1094: warning: comparison between > > > > signed and unsigned > > > > external/alsa-utils/aplay/aplay.c: In function 'end_au': > > > > external/alsa-utils/aplay/aplay.c:2102: warning: comparison between > > > > signed and unsigned > > > > external/alsa-utils/aplay/aplay.c: In function 'playback_go': > > > > external/alsa-utils/aplay/aplay.c:2154: warning: comparison between > > > > signed and unsigned > > > > external/alsa-utils/aplay/aplay.c: In function 'playback': > > > > external/alsa-utils/aplay/aplay.c:2194: warning: overflow in implicit > > > > constant conversion > > > > external/alsa-utils/aplay/aplay.c: In function 'capture': > > > > external/alsa-utils/aplay/aplay.c:2292: warning: overflow in implicit > > > > constant conversion > > > > external/alsa-utils/aplay/aplay.c:2295: warning: comparison is always > > > > true due to limited range of data type > > > > external/alsa-utils/aplay/aplay.c:2349: warning: comparison between > > > > signed and unsigned > > > > external/alsa-utils/aplay/aplay.c:2351: warning: comparison between > > > > signed and unsigned > > > > make: *** [out/target/product/generic/obj/EXECUTABLES/ > > > > alsa_aplay_intermediates/aplay/aplay.o] Error 1 > > > > > Has anyone faced the same? If there is apatchfor the same, can that > > > > please be passed? > > > > > Thanks. > > -- > Ravishankar Haranathhttp://www.linmaya.net > > We should be taught not to wait for inspiration to start a thing. Action > always generates inspiration. Inspiration seldom generates action. > - Frank Tibolt --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
