Android 调试: 高通代码编译报错

本文解决高通代码编译时因路径配置不当导致的错误。通过调整BSP路径设置,确保代码编译顺利进行。文章详细介绍了如何检查与修正代码路径,以及如何更新BuildEnv.sh文件。
AI助手已提取文章相关产品:

高通代码编译报错-集合
1:报错:

makefile:52: recipe for target 'ABL_FV_IMG' failed
make: *** [ABL_FV_IMG] Error 127
make: Leaving directory '/home/work/factory/bootable/bootloader/edk2'

一开编译0%就报这个错误,原因是高通代码默认下载好后,自己会保存的代码编译路径为你下载的路径
----应该要BSP把这个指定路径修改为动态路径
查询路径方式如下:
进入目录:factory/bootable/bootloader/edk2
用命令查看:

. ./edksetup.sh BaseTools------------------------前面是“.”  +  " "  +   "."      点+空格+点

结果提示路径空
bash: …/edksetup.sh: No such file or directory
或者提示之前下载代码的老路径,编译报错是因为你移动了代码目录到其他目录:

A@ubuntu:~/work/factory/bootable/bootloader/edk2$ ./edksetup.sh BaseTools/
Please note: This script must be 'sourced' so the environment can be changed.
. edksetup.sh
source edksetup.sh
./edksetup.sh: line 129: return: can only `return' from a function or sourced script
Loading previous configuration from /home/ckt/work/blackberry-660-factory/bootable/bootloader/edk2/Conf/BuildEnv.sh
WORKSPACE: /home/work/factory/bootable/bootloader/edk2-------------代码工作环境也就是代码路径在这
EDK_TOOLS_PATH: /media/acd822ab-cb6b-4e42-854d-7096e903502c/blackberry660/factory/bootable/bootloader/edk2/BaseTools
CONF_PATH: /home/work/factory/bootable/bootloader/edk2/Conf

EDK_TOOLS_PATH提示的路径是之前的老路径,和 CONF_PATH对应不上
所以用which build查看是空,没有路径。代码编译会报错。

重新设置下代码路径:
在代码/bootable/bootloader/edk2目录下:
echo $EDK_TOOLS_PATH 查看下路径
删除Conf/BuildEnv.sh 在运行这2个命令
unset EDK_TOOLS_PATH 发现路径不对,重新设置它

. ./edksetup.sh BaseTools
which build

这时候which build应该就会有显示了

您可能感兴趣的与本文相关内容

09-25 08:27:41.152 20211 20211 F DEBUG : #00 pc 00000000000380c4 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm64/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::CmpHelperEQ<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+44) (BuildId: b5e7e34835ac71674d64a641e0ca2484) 09-25 08:27:41.152 20211 20211 F DEBUG : #01 pc 00000000000374e4 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm64/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::EqHelper::Compare<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent, (void*)0>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+48) (BuildId: b5e7e34835ac71674d64a641e0ca2484) 09-25 08:27:41.175 994 19599 E android.hardware.nfc@1.2-impl: failed to send event!!! 09-25 08:27:41.179 0 0 I nfc_dev_ioctl: cmd = 4004e906 arg = 0 09-25 08:27:41.185 0 0 I nfc_dev_flush: read thread already released 09-25 08:27:41.185 0 0 I nfc_dev_close: 496, 0 hs@hscyx-OptiPlex-Tower-7010:~/log/vts_nfc$ hs@hscyx-OptiPlex-Tower-7010:~/log/vts_nfc$ hs@hscyx-OptiPlex-Tower-7010:~/log/vts_nfc$ hs@hscyx-OptiPlex-Tower-7010:~/log/vts_nfc$ adb logcat -b all | grep nfc 09-25 07:45:27.115 26945 26945 F DEBUG : #00 pc 00000000000380c4 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm64/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::CmpHelperEQ<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+44) (BuildId: b5e7e34835ac71674d64a641e0ca2484) 09-25 07:45:27.115 26945 26945 F DEBUG : #01 pc 00000000000374e4 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm64/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::EqHelper::Compare<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent, (void*)0>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+48) (BuildId: b5e7e34835ac71674d64a641e0ca2484) 09-25 07:46:45.408 27939 27939 F DEBUG : #00 pc 0001ce64 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::CmpHelperEQ<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+22) (BuildId: 675df8604db11d13f71f81b34683c087) 09-25 07:46:45.408 27939 27939 F DEBUG : #01 pc 0001c74b /data/local/tmp/VtsHalNfcV1_0TargetTest/arm/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::EqHelper::Compare<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent, (void*)0>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+30) (BuildId: 675df8604db11d13f71f81b34683c087) 09-25 08:26:40.392 0 0 I nfc_dev_open: 496, 0 09-25 08:26:40.392 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 1 09-25 08:26:40.492 0 0 I nfc_dev_ioctl: cmd = 4004e904 arg = 0 09-25 08:26:40.503 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 1 09-25 08:26:40.603 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 0 09-25 08:26:40.714 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 1 09-25 08:26:40.747 0 0 I nfc_dev_ioctl: cmd = 4004e906 arg = 0 09-25 08:26:40.753 0 0 I nfc_dev_flush: read thread already released 09-25 08:26:40.753 0 0 I nfc_dev_close: 496, 0 09-25 08:26:40.764 0 0 I nfc_dev_open: 496, 0 09-25 08:26:40.765 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 1 09-25 08:26:40.865 0 0 I nfc_dev_ioctl: cmd = 4004e904 arg = 0 09-25 08:26:40.875 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 1 09-25 08:26:40.976 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 0 09-25 08:26:41.086 0 0 I nfc_dev_ioctl: cmd = 4004e901 arg = 1 09-25 08:27:41.152 20211 20211 F DEBUG : #00 pc 00000000000380c4 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm64/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::CmpHelperEQ<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+44) (BuildId: b5e7e34835ac71674d64a641e0ca2484) 09-25 08:27:41.152 20211 20211 F DEBUG : #01 pc 00000000000374e4 /data/local/tmp/VtsHalNfcV1_0TargetTest/arm64/VtsHalNfcV1_0TargetTest (testing::AssertionResult testing::internal::EqHelper::Compare<android::hardware::nfc::V1_0::NfcEvent, android::hardware::nfc::V1_0::NfcEvent, (void*)0>(char const*, char const*, android::hardware::nfc::V1_0::NfcEvent const&, android::hardware::nfc::V1_0::NfcEvent const&)+48) (BuildId: b5e7e34835ac71674d64a641e0ca2484) 09-25 08:27:41.179 0 0 I nfc_dev_ioctl: cmd = 4004e906 arg = 0 09-25 08:27:41.185 0 0 I nfc_dev_flush: read thread already released 09-25 08:27:41.185 0 0 I nfc_dev_close: 496, 0 执行后触发报错高通andorid 13 代码如何修改
最新发布
09-26
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值