[android-porting] Re: aplay.c

2009-05-19 Thread Claw
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

[android-porting] Re: aplay.c

2009-05-19 Thread Ravishankar Haranath
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 wrote: > > Thank you, this is what I did. I have another problem now. > > I try running the buil

[android-porting] Re: aplay.c

2009-05-20 Thread Claw
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 eve

[android-porting] Re: aplay.c

2009-05-20 Thread crazygenie
Incompatibility is the most likely issue.. I would recommend you to do a complete rootfs build for your target and a separate kernel build. On May 20, 12:22 pm, Claw wrote: > yes, I have done these. Having included the last one > BUILD_WITH_ALSA_UTILS :=true, I am able to build the alsa_aplay, >

[android-porting] Re: aplay.c

2009-05-15 Thread crazygenie
comment out typedef for off64_t in external/alsa-utils/android/ aconfig.h and retry. On May 14, 3:56 pm, Claw 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/ap