Done. Environment: android-n x86 related image downloaded by sdk manager + android-goldfish-3.18-dev source code
export ARCH=x86 export CROSS_COMPILE=x86_64-linux-android- export PATH=x86_64-linux-android-4.9/bin/:$PATH make i386_ranchu_defconfig
Then copy the generated bzImage to your/android/sdk/system-images/android-N/default/x86/ Back up the original kernel-ranchu, and then rename bzImage to kernel-ranchu. Then use system.img userdata.img ramdisk.img and kernel-ranchu in this directory to start the emulator: emulator -kernel ./kernel-ranchu -sysdir ./ -system ./system.img -data ./userdata. img -ramdisk ./ramdisk.img The key to the previous failure was that i386_ranchu_defconfig was not used during make. I haven't figured out the difference between this i386_ranchu_defconfig and i386_emu_defconfig.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Done.
Environment: android-n x86 related image downloaded by sdk manager + android-goldfish-3.18-dev source code
export ARCH=x86
export CROSS_COMPILE=x86_64-linux-android-
export PATH=x86_64-linux-android-4.9/bin/:$PATH
make i386_ranchu_defconfig
Then copy the generated bzImage to your/android/sdk/system-images/android-N/default/x86/
Back up the original kernel-ranchu, and then rename bzImage to kernel-ranchu.
Then use system.img userdata.img ramdisk.img and kernel-ranchu in this directory to start the emulator:
emulator -kernel ./kernel-ranchu -sysdir ./ -system ./system.img -data ./userdata. img -ramdisk ./ramdisk.img
The key to the previous failure was that i386_ranchu_defconfig was not used during make. I haven't figured out the difference between this i386_ranchu_defconfig and i386_emu_defconfig.