Hi Santosh,
When you are starting the emulator it is ok to stop the booting
process, because there is no emma.jar file installed on the system.
The emulator tries to find the missing file every ~5 secs. So if you
are executing the adb remount and adb sync it will continue booting
up. (it synchronizes the image and the build system directories. Emma
jar and the requiered project(s) will be copied to it. )
One more thing:
If you would like to boot the emulator immediately, you have to add
the emma.jar into the system.img file. To do that, add the following
lines at the and of the "build/target/product/core.mk" file:
PRODUCT_COPY_FILES += \
out/target/common/obj/JAVA_LIBRARIES/emma_intermediates/
javalib.jar:system/framework/emma.jar\
Note: add these lines to the file before the make ... command(s)
Gabor
On Aug 26, 3:39 am, santosh kumar <santosh.1...@gmail.com> wrote:
> Hi All,
>
> I have few questions about this.. plz clarify me..
>
> i want to generate code coverage for apidemos only...
>
> first i changed init.rc then i followed every thing which is mentioned
> in gobor mail..
>
> one thing i am not understanding... when i start the emulator,
> emulator is getting stucked with the boot up logo,
>
> i have seen some other artical... we need to run runtest.py?
>
> is it correct?
>
> why emulator is getting stucked?
>
> Thanks
> Santosh
>
> On Aug 26, 2:28 am, hari uppalapati <hari.andr...@gmail.com> wrote:
>
> > hi
> > i was not facing any issues with emulator.Only thing was my coverage.ec file
> > was empty as my sdcard is not recognised.with the following steps the issues
> > was resolved.If possible post the logcat o/p and also the steps followed.
> > 1) edit system/core/rootdir/Android.mk so that the copy_from variable on
> > line 6 contains etc/vold.conf.
> > copy_from := \
> > etc/dbus.conf \
> > etc/vold.conf \
> > etc/init.goldfish.sh \
> > etc/hosts
>
> > 2)copy vold.conf from (git://
> > android.git.kernel.org/platform/vendor/htc/dream-open.git) to
> > system/core/rootdir/etc/
> > cp vendor/htc/dream-open/vold.conf system/core/rootdir/etc.
> > regards
> > Haritha
>
> > On Tue, Aug 25, 2009 at 2:40 AM, santosh kumar
> > <santosh.1...@gmail.com>wrote:
>
> > > Hi All,
>
> > > what changes you have been done to vold.conf?
>
> > > and i followed the steps of gobor..
>
> > > but for me also, emulator is getting stucked..
>
> > > can you plz help me..
>
> > > On Aug 25, 2:23 am, Haritha <hari.andr...@gmail.com> wrote:
> > > > thanks everyone for posting info on emma coverage.I was also able to
> > > > generate coverage reports for custom tests with necessary changes to
> > > > vold.conf.
> > > > regards
> > > > Haritha
>
> > > > On Aug 20, 6:08 am, Gabor <gabor.andr...@googlemail.com> wrote:
>
> > > > > Hi All,
>
> > > > > Finally, the emma code coverage measurement is working for me (for a
> > > > > custom project). So here are the steps what you need to make it work
> > > > > (I have tested it, with Java 1.5 on Ubuntu 8.04):
>
> > > > > mkdir android-src
> > > > > cd android-src
> > > > > repo init -u git://android.git.kernel.org/platform/manifest.git -b
> > > > > cupcake
> > > > > repo sync
>
> > > > > # Add emma.jar to the system/core/rootdir/init.rc
> > > > > sed 's/\/system\/framework\/core.jar:\/system\/framework\/ext.jar:/\/
> > > > > system\/framework\/core.jar:\/system\/framework\/ext.jar:\/system\/
> > > > > framework\/emma.jar:/' system/core/rootdir/init.rc > system/core/
> > > > > rootdir/init.rc.tmp
> > > > > mv system/core/rootdir/init.rc.tmp system/core/rootdir/init.rc
>
> > > > > # Rebuild the boot image
> > > > > make bootimage
>
> > > > > # To build the full system image
> > > > > make -j4
>
> > > > > # Set the PATH:
> > > > > export PATH=${PATH}:/<_path_>/android-src/out/host/linux-x86/bin/
>
> > > > > # Build the emma jar itself
> > > > > make emma
>
> > > > > # Setting the environment and additional bash commands. (like
> > > > > m,mm,mmm, choosecombo etc) Notice the space after the dot!
> > > > > . build/envsetup.sh
>
> > > > > # Set EMMA_INSTRUMENTATION to true
> > > > > export EMMA_INSTRUMENT=true
>
> > > > > # Copy your project to development/samples/<_projectname_> or
> > > > > somewhere..:)
> > > > > # Based on the ApiDemo create an Android.mk file for the project
> > > > > directory and the project test directory
> > > > > # The LOCAL_INSTRUMENTATION_FOR value in test dir Android.mk has to be
> > > > > equal with the LOCAL_PACKAGE_NAME defined in the Android.mk in the
> > > > > main project dir.
> > > > > # Compile the Application would like to instrument
> > > > > mmm development/samples/<_projectname_>
>
> > > > > # Set the ANDROID_PRODUCT_OUT directory for the emulator to know the
> > > > > image location
> > > > > export ANDROID_PRODUCT_OUT=/<_path_>/android-src/out/target/product/
> > > > > generic
>
> > > > > # Start an emulator with a simulated sdcard:
> > > > > emulator -sdcard <path to sdcard>
>
> > > > > # Remount the drive - it is needed to have a writable drive. without
> > > > > that sync wont work
> > > > > adb remount
>
> > > > > # Synchronize the local content with the emulator
> > > > > adb sync
>
> > > > > adb shell
> > > > > # create directory: mkdir /etc/coverageresult
>
> > > > > # Executing tests
> > > > > adb shell am instrument -w -e coverage true -e coverageFile /etc/
> > > > > coverageresult/coverage.ec hu.agsoftware.sample.tests/
> > > > > android.test.InstrumentationTestRunner
>
> > > > > # Dump a runtime coverage data file:
> > > > > adb pull /etc/coverageresult/coverage.ec coverage.ec
>
> > > > > # Generate a coverage report
> > > > > java -cp external/emma/lib/emma.jar emma report -r html -in
> > > > > coverage.ec -sp development/samples/<_projectname_>/src -in
> > > out/target/
> > > > > common/obj/APPS/<_projectname>_intermediates/coverage.em
>
> > > > > I hope it helps.
>
> > > > > Gabor- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
