[Issue]
ADB can’t work.
[Root cause]
|
Executable files |
image |
Executable obj files |
|
/root/sbin/adbd |
Ramdisk |
out/target/product/tulkas/obj/EXECUTABLES/adbd_intermediates |
|
/system/bin/adb |
system |
out/target/product/tulkas/obj/EXECUTABLES/adb_intermediates |
1. I’vemodified one file(services.c), this file will be linked to bothexecutable files, however this file need to be compiled differently beforelinking.
2. Ifthe file(services.c) is in the original path, compile tool will putdifferent OBJ files into different folders.

3. Ifthe file is put to the new path(device/ti/tulkas/android/system/core/adb), it’s only compiled once, and theexecutable OBJ file is put to another path(out/target/product/tulkas/device/ti/tulkas/android/system/core/adb/).

4. Whichone is compiled firstly? Here ADB is the previous one, ADBD is the next one.And the file(services.c) is compiled once. So the next executable file(ADBD)doesn’t work.
[Solution]
Here we try tocreate different executable OBJ files.

I’ve verifiedthis solution, and the result is OK.
本文针对ADB无法工作的问题进行了深入分析。发现由于一个共享文件services.c的不同编译路径导致了后续执行文件ADBD出现问题。通过调整编译流程,确保每个执行文件都有独立的对象文件,最终解决了问题。
926

被折叠的 条评论
为什么被折叠?



