Hi, Thank you for support. As per your suggestions on LTP porting on android, i have installed android NDK, SDK on Ubuntu 10.04,
As per the Android NDK compilation steps, i have to create android.mk ( to describe the native source to NDK build system) file to compile LTP source using NDK. Can you please suggest the procedure or send the sample android.mk file to compile LTP-20110228 source by using NDK build system. Also, i have cross compiled Busy box by using arm-none-linux-gnueabi and generated the busy box binary. Can you please suggest the procedure of how to port the busy box binary to the android platform. Thanks in advance. Rajender.G ________________________________________ From: Maxin B John [[email protected]] Sent: Thursday, August 25, 2011 4:29 PM To: G Rajender Cc: Cyril Hrubis; [email protected]; Kumar; Anupam Srivastava - ERS, HCL Tech; [email protected] Subject: Re: [LTP] Porting of LTP on Android on Beagleboard Hi, On Thu, Aug 25, 2011 at 1:31 PM, G Rajender <[email protected]> wrote: > I have Cross compiled the LTP-20110228 source using scratch box and generated > the binaries for beagleboard. Android is a totally different environment in terms of user-land (Dalvik based), libraries (bionic) and kernel as compared to the normal GNU/Linux. You can't use the same cross-tool-chains for normal Linux and Android. > I also built the android ginger bread source and obtained the binaries for > beagleboard. > > I have copied the android images along with LTP binaries (in data partition) > on to SD card and inserted in to sd/mmc slot on beagleboard and booted. > > I got adb command prompt. The script files runltp.sh, runalltests.sh, > runltplite.sh are not running in adb prompt. > > Can u please suggest the procedure of how to run the ltp scripts in adb > command prompt. As mentioned above, the LTP binaries and scripts which are compiled using the normal cross-tool-chain won't work in Android environment. You need to use the specific Android Tool-chain (latest NDK available here: http://developer.android.com/sdk/ndk/index.html ). Repeat the same cross-compiling of LTP using the Android NDK (won't be that easy as bionic isn't as smart or big as glibc). I would also recommend you to port "Busybox" for Android or download it from the Android market itself. The "ash" shell available in Busybox should be enough for you to get started with the scripts in LTP. There are some patches already available for porting LTP to Android : http://comments.gmane.org/gmane.linux.ltp/14497 However, these patches may not be acceptable to the mainstream LTP as it breaks some existing tests in the "common/normal" platforms. I think we can go ahead with the way we support UCLINUX in LTP .. ie: #ifdef UCLINUX So, if we care to re-write those patches with #ifdef ANDROID (or #ifndef ANDROID based on our logic) without breaking other tests, I think we can officially welcome Android related patches to LTP. Cyril, Garrett, please let us know your thoughts on this. Best Regards, Maxin Larsen & Toubro Limited www.larsentoubro.com This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
