Because before the Genymotion simulator, yesterday did an update, and the results of the problem of the Play.exe stop work, online all kinds of ways toss a few hours invalid, finally put
Oracle VM Virtualboxgenymotion was completely uninstalled with 360 software management, then restarted, then re-downloaded aVirtualBox +genymotionof the integrated installation package, not negative, after the restart of the machine can normally enter the simulator : Http://files2.genymotion.com/genymotion/genymotion-2.2.0/genymotion-2.2.0-vbox.exe look at the effect is good, the process of the simulator I will not say in detail Let's find out for ourselves, there are many online tutorials
We're ready to start our commissioning process.
1. We download a pluginDownload the Eclipse plugin
- Genymotion Plugin for Eclipse
- mandatory dependency for Eclipse plugin v1.0.3
This plugin can also be installed directly through Eclipse: Help->install New Software, then add the following address:
Http://plugins.genymotion.com/eclipse
Note: If you want to use this plugin, your system must already have Genymotion installed
Source: >
Plug-in process is not detailed said the official website copy down has written 2,
error message: install_failed_cpu_abi_incompatible There must have been a mistake like this when we first debugged.install_failed_cpu_abi_incompatibleThe reason is because our simulator is the processor of the x86 architecture, but Eclipse compiled apk can only run on the arm's architecture, so it will prompt this error but it doesn't matter the vast number of netizens is endless, we just download a patch, installed on the normal run APK ( Patches from there will not be refined, anyway can be used as well) the following patch address:Http://pan.baidu.com/s/1h7yPDPatch installation is very simple, the download of the file directly into the simulator, will pop up a series of hints, all points yes, the prompt after the box to restart the simulator, and then start the simulator again, may error, but it doesn't matter, we don't care about it, restart again, until normal 3, good, Then we can start our debugging cause, because we are talking about the VS debug ndk, here we need to use an artifact visualgdb, you can search online automatically, you can also in the QQ group:25093009, Group share self-download, group share file name:
Eclipse vs the ndk, The file contains details on how to install the configuration, which is not described in detail here
notice a problem during debugging, so must be compiled into a x86 schema, how to compile the x86 schema so? It's easy to create a application.mk in the JNI directory and write the following code: App_abi: = Armeabi armeabi-v7a x86Simple, so the sub-ndk-build command at compile time will automatically compile the above three architecture of so file, so we can arbitrarily frame inside debugging 4, Next we see a few bar, debugging process Additional interface
APK has not loaded so vs inside the breakpoint is in a blank breakpoint state hover window out, so has successfully loaded, see our vs Breakpoint, has been able to use the normal, and successfully entered the breakpoint. Here we debug success, we are not feeling very excited, if you feel excited, on the point of praise it, haha, go to test it, heartbeat than action.
From for notes (Wiz)
