AOSP Build TARGET_PRODUCT 失败 [英] AOSP Build TARGET_PRODUCT fails

问题描述

我正在尝试使用 AOSP 构建外部工具.我的操作系统是 Linux，发行版 ArchLinux (i3wm)，但为了编译 AOSP，我在 Docker 中使用 Ubuntu (https://android.googlesource.com/platform/build/+/master/tools/docker)

I'm trying to build an external tool with AOSP. My OS is Linux, Distribution ArchLinux (i3wm), but to compile AOSP I use Ubuntu in Docker (https://android.googlesource.com/platform/build/+/master/tools/docker)

第一步:

# init repo
repo init -u https://android.googlesource.com/platform/manifest -b android-8.0.0_r36 --depth=1
repo sync
. build/envsetup.sh # set up environment
lunch aosp_arm-eng # select target to build

第二步:选择工具并构建

cd external/selinux
mma -j48

输出:

ninja: error: unknown target 'MODULES-IN-'
15:41:55 ninja failed with: exit status 1
make: *** [run_soong_ui] Error 1
make: Leaving directory `/home/user/aosp'

#### make failed to build some targets (6 seconds) ###

另一个工具

cd external/wpa_supplicant_8
mma -j48

输出:

ninja: error: unknown target 'MODULES-IN-external-wpa_supplicant_8'
15:41:55 ninja failed with: exit status 1
make: *** [run_soong_ui] Error 1
make: Leaving directory `/home/user/aosp'

#### make failed to build some targets (2 seconds) ###

任何 aosp 通用目标都会发生这种情况:

This happens with any aosp generic target:

Lunch menu... pick a combo:
     1. aosp_arm-eng                    # fails
     2. aosp_arm64-eng                  # fails
     3. aosp_mips-eng                   # fails
     4. aosp_mips64-eng                 # fails
     5. aosp_x86-eng                    # fails
     6. aosp_x86_64-eng                 # fails
     7. full_fugu-userdebug             # works
     8. aosp_fugu-userdebug             # works
     9. car_emu_arm64-userdebug         # fails
     10. car_emu_arm-userdebug          # fails
     11. car_emu_x86_64-userdebug       # fails
     12. car_emu_x86-userdebug          # fails
     13. mini_emulator_arm64-userdebug  # fails
     14. m_e_arm-userdebug              # fails
     15. m_e_mips64-eng                 # fails
     16. m_e_mips-userdebug             # fails
     17. mini_emulator_x86_64-userdebug # fails
     18. mini_emulator_x86-userdebug    # fails
     19. aosp_dragon-userdebug          # works
     20. aosp_dragon-eng                # works
     21. aosp_marlin-userdebug          # works
     22. aosp_marlin_svelte-userdebug   # works
     23. aosp_sailfish-userdebug        # works
     24. aosp_angler-userdebug          # works
     25. aosp_bullhead-userdebug        # works
     26. aosp_bullhead_svelte-userdebug # works
     27. hikey-userdebug                # works

我想在所有arch中编译一些二进制工具:arm、arm64、x86和x86_64.

I want to compile some binary tools in all arch: arm, arm64, x86 and x86_64.

为什么 aosp_arm-eng 不起作用?或者如何从非通用 aosp 目标更改 CPU 架构?

Why aosp_arm-eng does not work? Or how can I change the CPU architecture from non generic aosp target?

使用 tapas 不起作用.

推荐答案

在尝试使用 mm... 快捷方式之前，您可能需要进行完整的 AOSP 构建 - 看起来有些构建脚本文件是尚未生成.

You probably need to make a full AOSP build before trying to use mm... shortcuts - looks like some build script files were not generated yet.

这篇关于AOSP Build TARGET_PRODUCT 失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！