日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當(dāng)前位置: 首頁 > 运维知识 > Android >内容正文

Android

在 Mac 上为 Android 编译 WebRTC

發(fā)布時(shí)間:2024/4/11 Android 51 豆豆
生活随笔 收集整理的這篇文章主要介紹了 在 Mac 上为 Android 编译 WebRTC 小編覺得挺不錯(cuò)的,現(xiàn)在分享給大家,幫大家做個(gè)參考.

在 Mac 上為 Android 編譯 WebRTC 的基本流程和在任意平臺(tái)上編譯任何其它目標(biāo)平臺(tái)的 WebRTC 大體一致,但在 Mac 上為 Android 編譯 WebRTC 不是 WebRTC 官方正式支持的 WebRTC 的構(gòu)建方式,因而需要針對(duì)這種構(gòu)建方式,對(duì) WebRTC 構(gòu)建系統(tǒng)中的部分配置和工具做一些適當(dāng)?shù)恼{(diào)整。本文將描述在 Mac 上為 Android 編譯 WebRTC 的流程,流程中各個(gè)步驟將會(huì)遇到的問題,問題發(fā)生原因的簡(jiǎn)單解釋,以及問題的解決方法。

在 Mac 上為 Android 編譯 WebRTC 的過程如下。

1. 創(chuàng)建 args.gn 文件

為 Android 版 WebRTC 的構(gòu)建創(chuàng)建 args.gn 文件做一些全局的構(gòu)建配置開關(guān),如:

is_component_build = false rtc_build_tools = false rtc_include_tests = false treat_warnings_as_errors = false use_rtti = false use_dummy_lastchange = true is_clang = true target_cpu = "arm64" is_debug = true symbol_level = 2 clang_base_path = "/Users/lisi/Projects/opensource/OpenRTCClient/build_system/llvm-build/mac/mac/Release+Asserts" android_sdk_build_tools_version = "30.0.1" target_os = "android" android_ndk_root = "/Users/lisi/Library/Android/sdk/ndk/23.1.7779620" android_sdk_root = "/Users/lisi/Library/Android/sdk" clang_use_chrome_plugins = false lint_android_sdk_root = "/Users/lisi/Library/Android/sdk" use_custom_libcxx = false use_sysroot = false enable_libaom = false enable_libaom_decoder = false rtc_use_h264 = true rtc_enable_protobuf = true rtc_include_ilbc = false rtc_libvpx_build_vp9 = true ffmpeg_branding = "Chrome"

2. gn gen 生成構(gòu)建配置文件

通過 gn gen 根據(jù)創(chuàng)建的 args.gn 文件,各個(gè) BUILD.gn 和 *.gni 構(gòu)建配置文件,生成 ninja 構(gòu)建所需的配置文件。假設(shè) args.gn 文件位于 build/android/arm64/debug 目錄下,執(zhí)行如下命令:

OpenRTCClient % gn gen build/android/arm64/debug

這里就報(bào)了錯(cuò),報(bào)錯(cuò)信息如下:

OpenRTCClient % gn gen build/android/arm64/debug ERROR Unresolved dependencies. //examples/androidapp/third_party/autobanh:autobanh_java__header(//build/toolchain/android:android_clang_arm64)needs //third_party/ijar:ijar(//build/toolchain/mac:clang_x64) //third_party/accessibility_test_framework:accessibility_test_framework_java__header(//build/toolchain/android:android_clang_arm64)needs //third_party/ijar:ijar(//build/toolchain/mac:clang_x64) //third_party/android_deps:android_arch_core_common_java__header(//build/toolchain/android:android_clang_arm64)needs //third_party/ijar:ijar(//build/toolchain/mac:clang_x64) //third_party/android_deps:android_arch_core_runtime_java__classes__header(//build/toolchain/android:android_clang_arm64)needs //third_party/ijar:ijar(//build/toolchain/mac:clang_x64) //third_party/android_deps:android_arch_lifecycle_common_java8_java__header(//build/toolchain/android:android_clang_arm64)needs //third_party/ijar:ijar(//build/toolchain/mac:clang_x64) //third_party/android_deps:android_arch_lifecycle_common_java__header(//build/toolchain/android:android_clang_arm64)needs //third_party/ijar:ijar(//build/toolchain/mac:clang_x64) . . . . . .

報(bào)錯(cuò)信息提示說,找不到被廣泛依賴的一個(gè)構(gòu)建目標(biāo) //third_party/ijar:ijar。

通過這段報(bào)錯(cuò)信息,我們不難了解到,這個(gè)構(gòu)建目標(biāo)應(yīng)該是定義在 webrtc/third_party/ijar/BUILD.gn 文件中的。我們打開這個(gè)文件,來看下這個(gè)構(gòu)建目標(biāo)的定義:

if (is_linux || is_chromeos) {config("ijar_compiler_flags") {if (is_clang) {cflags = ["-Wno-shadow","-Wno-unused-but-set-variable",]}}executable("ijar") {sources = ["classfile.cc","common.h","ijar.cc","mapped_file.h","mapped_file_unix.cc","platform_utils.cc","platform_utils.h","zip.cc","zip.h","zlib_client.cc","zlib_client.h",]deps = [ "//third_party/zlib" ]configs += [ ":ijar_compiler_flags" ]# Always build release since this is a build tool.if (is_debug) {configs -= [ "//build/config:debug" ]configs += [ "//build/config:release" ]}} }

通過該文件,可以看到,只有在 Linux 和 ChromeOS 上,才會(huì)定義構(gòu)建目標(biāo) //third_party/ijar:ijar。我們修改上面的 if 判斷里的條件,同樣為 Mac 定義這個(gè)構(gòu)建目標(biāo)。具體來說,是將如下的條件判斷:

if (is_linux || is_chromeos) {

修改為:

if (is_linux || is_chromeos || is_mac) {

webrtc/third_party/ijar/BUILD.gn 這個(gè)文件中的其它內(nèi)容保持不變。

這樣我們可以成功執(zhí)行 gn gen 了:

OpenRTCClient % gn gen build/android/arm64/debug Done. Made 5530 targets from 318 files in 2743ms

3. 執(zhí)行 ninja 命令構(gòu)建 WebRTC

(1). -ffile-compilation-dir=. 導(dǎo)致的編譯錯(cuò)誤

執(zhí)行 ninja 命令構(gòu)建 WebRTC:

OpenRTCClient % ninja -C build/android/arm64/debug

還沒編譯幾行代碼,就報(bào)了個(gè)編譯錯(cuò)誤:

OpenRTCClient % ninja -C build/android/arm64/debug ninja: Entering directory `/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug' [1/5234] CC obj/base/third_party/libevent/libevent/event_tagging.o FAILED: obj/base/third_party/libevent/libevent/event_tagging.o ../../../../../../../Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang -MMD -MF obj/base/third_party/libevent/libevent/event_tagging.o.d -DHAVE_CONFIG_H -D_GNU_SOURCE -DANDROID -DHAVE_SYS_UIO_H -DANDROID_NDK_VERSION_ROLL=r22_1 -D_DEBUG -DDYNAMIC_ANNOTATIONS_ENABLED=1 -I../../../../webrtc/base/third_party/libevent/android -I../../../../webrtc -Igen -fno-delete-null-pointer-checks -fno-ident -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -fcolor-diagnostics -fmerge-all-constants -fcrash-diagnostics-dir=../../../../webrtc/tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -ffp-contract=off -ffunction-sections -fno-short-enums --target=aarch64-linux-android21 -mno-outline-atomics -mno-outline -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= -ffile-compilation-dir=. -no-canonical-prefixes -Oz -fdata-sections -ffunction-sections -fno-unique-section-names -fno-omit-frame-pointer -g2 -gdwarf-aranges -ggnu-pubnames -Xclang -fuse-ctor-homing -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall -Wno-unused-variable -Wno-c++11-narrowing -Wno-unused-but-set-variable -Wno-misleading-indentation -Wno-missing-field-initializers -Wno-unused-parameter -Wloop-analysis -Wno-unneeded-internal-declaration -Wenum-compare-conditional -Wno-psabi -Wno-ignored-pragma-optimize -Wmax-tokens -std=c11 --sysroot=../../../../../../../Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -c ../../../../webrtc/base/third_party/libevent/event_tagging.c -o obj/base/third_party/libevent/libevent/event_tagging.o clang: error: unknown argument: '-ffile-compilation-dir=.' [2/5234] CC obj/base/third_party/libevent/libevent/signal.o . . . . . .

這段報(bào)錯(cuò)信息是說,clang 無法識(shí)別一個(gè)編譯選項(xiàng) -ffile-compilation-dir=.。在 stack overflow 上有個(gè)帖子在討論這個(gè)問題,Can’t build Webrtc with Bitcode enabled。出現(xiàn)這個(gè)問題,是因?yàn)榫幾g WebRTC 用的 clang 版本一般都比較新,WebRTC 的構(gòu)建系統(tǒng)為編譯設(shè)置了較新的 clang 版本才支持的一個(gè)編譯選項(xiàng),但本地編譯時(shí)使用的 clang 版本不夠新,于是出現(xiàn)了編譯工具無法識(shí)別編譯選項(xiàng)的問題。

這個(gè)編譯選項(xiàng)是在 webrtc/build/config/compiler/BUILD.gn 文件中加的:

if (is_clang && strip_absolute_paths_from_debug_symbols) {# If debug option is given, clang includes $cwd in debug info by default.# For such build, this flag generates reproducible obj files even we use# different build directory like "out/feature_a" and "out/feature_b" if# we build same files with same compile flag.# Other paths are already given in relative, no need to normalize them.if (is_nacl) {# TODO(https://crbug.com/1231236): Use -ffile-compilation-dir= here.cflags += ["-Xclang","-fdebug-compilation-dir","-Xclang",".",]} else {# -ffile-compilation-dir is an alias for both -fdebug-compilation-dir=# and -fcoverage-compilation-dir=.cflags += [ "-ffile-compilation-dir=." ]}if (!is_win) {# We don't use clang -cc1as on Windows (yet? https://crbug.com/762167)asmflags = [ "-Wa,-fdebug-compilation-dir,." ]}

這里我們將這個(gè)編譯選項(xiàng)替換掉來解決這個(gè)問題。具體來說,是將如下這行代碼:

cflags += [ "-ffile-compilation-dir=." ]

替換為:

cflags += [ "-fdebug-compilation-dir" ]

修改完成后,重新執(zhí)行 gn gen 和 ninja 命令。

(2). jni_generator.py 執(zhí)行失敗導(dǎo)致的錯(cuò)誤

隨后遇到如下編譯報(bào)錯(cuò):

[1109/5146] ACTION //sdk/android:generated_external_classes_jni(//build/toolchain/android:android_clang_arm64) FAILED: gen/sdk/android/generated_external_classes_jni/Integer_jni.h gen/sdk/android/generated_external_classes_jni/Double_jni.h gen/sdk/android/generated_external_classes_jni/Long_jni.h gen/sdk/android/generated_external_classes_jni/Iterable_jni.h gen/sdk/android/generated_external_classes_jni/Iterator_jni.h gen/sdk/android/generated_external_classes_jni/Boolean_jni.h gen/sdk/android/generated_external_classes_jni/BigInteger_jni.h gen/sdk/android/generated_external_classes_jni/Map_jni.h gen/sdk/android/generated_external_classes_jni/LinkedHashMap_jni.h gen/sdk/android/generated_external_classes_jni/ArrayList_jni.h gen/sdk/android/generated_external_classes_jni/Enum_jni.h python3 ../../../../webrtc/base/android/jni_generator/jni_generator.py --ptr_type=long --includes ../../../../../../../../webrtc/sdk/android/src/jni/jni_generator_helper.h --jar_file ../../../../../../../Library/Android/sdk/platforms/android-31/android.jar --output_file gen/sdk/android/generated_external_classes_jni/Integer_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Double_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Long_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Iterable_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Iterator_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Boolean_jni.h --output_file gen/sdk/android/generated_external_classes_jni/BigInteger_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Map_jni.h --output_file gen/sdk/android/generated_external_classes_jni/LinkedHashMap_jni.h --output_file gen/sdk/android/generated_external_classes_jni/ArrayList_jni.h --output_file gen/sdk/android/generated_external_classes_jni/Enum_jni.h --input_file=java/lang/Integer.class --input_file=java/lang/Double.class --input_file=java/lang/Long.class --input_file=java/lang/Iterable.class --input_file=java/util/Iterator.class --input_file=java/lang/Boolean.class --input_file=java/math/BigInteger.class --input_file=java/util/Map.class --input_file=java/util/LinkedHashMap.class --input_file=java/util/ArrayList.class --input_file=java/lang/Enum.class Traceback (most recent call last):File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/base/android/jni_generator/jni_generator.py", line 1630, in <module>sys.exit(main())File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/base/android/jni_generator/jni_generator.py", line 1624, in mainGenerateJNIHeader(java_path, header_path, args)File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/base/android/jni_generator/jni_generator.py", line 1485, in GenerateJNIHeaderjni_from_javap = JNIFromJavaP.CreateFromClass(input_file, options)File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/base/android/jni_generator/jni_generator.py", line 847, in CreateFromClassjni_from_javap = JNIFromJavaP(stdout.split('\n'), options)File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/base/android/jni_generator/jni_generator.py", line 767, in __init__self.fully_qualified_class = self.fully_qualified_class.replace('.', '/') AttributeError: 'JNIFromJavaP' object has no attribute 'fully_qualified_class' [1110/5146] CXX obj/third_party/abseil-cpp/absl/base/spinlock_wait/spinlock_wait.o warning: unknown warning option '-Wno-unused-but-set-variable'; did you mean '-Wno-unused-const-variable'? [-Wunknown-warning-option]

這次是構(gòu)建系統(tǒng)在執(zhí)行腳本文件 webrtc/base/android/jni_generator/jni_generator.py 生成 JNI 頭文件時(shí)出錯(cuò)。根據(jù)出錯(cuò)的調(diào)用堆棧信息,撈出來相關(guān)的主要的代碼如下:

class JNIFromJavaP(object):"""Uses 'javap' to parse a .class file and generate the JNI header file."""def __init__(self, contents, options):self.contents = contentsself.namespace = options.namespacefor line in contents:class_name = re.match('.*?(public).*?(class|interface) (?P<class_name>\S+?)( |\Z)', line)if class_name:self.fully_qualified_class = class_name.group('class_name')breakself.fully_qualified_class = self.fully_qualified_class.replace('.', '/')# Java 7's javap includes type parameters in output, like HashSet<T>. Strip# away the <...> and use the raw class name that Java 6 would've given us. . . . . . .@staticmethoddef CreateFromClass(class_file, options):class_name = os.path.splitext(os.path.basename(class_file))[0]javap_path = os.path.abspath(options.javap)p = subprocess.Popen(args=[javap_path, '-c', '-verbose', '-s', class_name],cwd=os.path.dirname(class_file),stdout=subprocess.PIPE,stderr=subprocess.PIPE,universal_newlines=True)stdout, _ = p.communicate()jni_from_javap = JNIFromJavaP(stdout.split('\n'), options)return jni_from_javap . . . . . . def GenerateJNIHeader(input_file, output_file, options):try:if os.path.splitext(input_file)[1] == '.class':jni_from_javap = JNIFromJavaP.CreateFromClass(input_file, options)content = jni_from_javap.GetContent()else:jni_from_java_source = JNIFromJavaSource.CreateFromFile(input_file, options)content = jni_from_java_source.GetContent()except ParseError as e:print(e)sys.exit(1)if output_file:with build_utils.AtomicOutput(output_file, mode='w') as f:f.write(content)else:print(content)

相關(guān)代碼的大致意思是,在 GenerateJNIHeader() 函數(shù)中調(diào)用 JNIFromJavaP.CreateFromClass(input_file, options) 方法;在 JNIFromJavaP.CreateFromClass(input_file, options) 方法中執(zhí)行 javap 命令,得到命令執(zhí)行的標(biāo)準(zhǔn)輸出的內(nèi)容,并以此內(nèi)容為參數(shù)創(chuàng)建 JNIFromJavaP,在類 JNIFromJavaP 構(gòu)造函數(shù)中出錯(cuò)。

我們打印 JNIFromJavaP 構(gòu)造函數(shù)接收的 contents 參數(shù),可以看到這個(gè)參數(shù)是空字符串,顯然不符合預(yù)期。我們提取 JNIFromJavaP.CreateFromClass(input_file, options) 方法中執(zhí)行的 javap 命令,這個(gè)命令大概像這樣:

/Library/Java/JavaVirtualMachines/jdk-11.0.13.jdk/Contents/Home/bin/javap -c -verbose -s Integer

我們?cè)诮K端命令行中執(zhí)行這個(gè)命令,這個(gè)命令執(zhí)行會(huì)報(bào)錯(cuò):

OpenRTCClient % /Library/Java/JavaVirtualMachines/jdk-11.0.13.jdk/Contents/Home/bin/javap -c -verbose -s Integer 錯(cuò)誤: 找不到類: Integer

來看一下給 javap 傳的兩個(gè)參數(shù)是干什么的:

OpenRTCClient % javap --help 用法: javap <options> <classes> 其中, 可能的選項(xiàng)包括:-? -h --help -help 輸出此幫助消息-version 版本信息-v -verbose 輸出附加信息-l 輸出行號(hào)和本地變量表-public 僅顯示公共類和成員-protected 顯示受保護(hù)的/公共類和成員-package 顯示程序包/受保護(hù)的/公共類和成員 (默認(rèn))-p -private 顯示所有類和成員-c 對(duì)代碼進(jìn)行反匯編-s 輸出內(nèi)部類型簽名-sysinfo 顯示正在處理的類的系統(tǒng)信息 (路徑, 大小, 日期, MD5 散列)-constants 顯示最終常量--module <模塊>, -m <模塊> 指定包含要反匯編的類的模塊--module-path <路徑> 指定查找應(yīng)用程序模塊的位置--system <jdk> 指定查找系統(tǒng)模塊的位置--class-path <路徑> 指定查找用戶類文件的位置-classpath <路徑> 指定查找用戶類文件的位置-cp <路徑> 指定查找用戶類文件的位置-bootclasspath <路徑> 覆蓋引導(dǎo)類文件的位置GNU 樣式的選項(xiàng)可使用 = (而非空白) 來分隔選項(xiàng)名稱 及其值。每個(gè)類可由其文件名, URL 或其 全限定類名指定。示例:path/to/MyClass.classjar:file:///path/to/MyJar.jar!/mypkg/MyClass.classjava.lang.Object

-c 參數(shù)用于對(duì)代碼進(jìn)行反匯編,-s 參數(shù)用于輸出內(nèi)部類型簽名。不過這里出錯(cuò)的關(guān)鍵不是參數(shù),而是指定類的方式。javap 命令接受的指定類的方式如上面的 help 輸出中最下面的說明。Mac 平臺(tái) javap 命令接受的指定類的方式與 Linux 平臺(tái)的 javap 命令接受的不太一樣。

WebRTC 的構(gòu)建系統(tǒng)會(huì)通過 webrtc/base/android/jni_generator/jni_generator.py 為幾個(gè)標(biāo)準(zhǔn)庫的類生成 JNI 頭文件,這些類的類文件打包在 rt.jar 文件中。我們從 rt.jar 文件中提取所有的類文件,并對(duì)類文件執(zhí)行 javap 命令:

opensource % mkdir jar_classes opensource % cd jar_classes jar_classes % jar xf /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre/lib/rt.jar jar_classes % cd java/lang lang % javap -c -s Integer 錯(cuò)誤: 找不到類: Integer lang % javap -c -s Integer.class Compiled from "Integer.java" public final class java.lang.Integer extends java.lang.Number implements java.lang.Comparable<java.lang.Integer> {public static final int MIN_VALUE;descriptor: Ipublic static final int MAX_VALUE;

在類文件所在的目錄,我們僅通過傳入類名類指定類時(shí),javap 執(zhí)行失敗。而通過 類名.class 的形式指定類時(shí),則可以執(zhí)行成功。在 Linux 平臺(tái)上,如果位于類文件所在的目錄,僅通過傳入類名來指定類,而沒有 .class 后綴名,javap 也可以執(zhí)行成功。

對(duì)于上面例子中的 Integer,在 Mac 平臺(tái)上執(zhí)行 javap 時(shí),正確的參數(shù)格式有多種,可以是 java.lang.Integer,可以是類文件的完整文件路徑,如 /var/folders/1x/5vtfxt410vbf9xhk8vvfz8l40000gn/T/tmp2gbxloem/java/lang/Integer.class,也可以是類文件的文件名 Integer.class,但不能是 Integer。

由此,也就可以得到我們對(duì)這個(gè)問題的解決方案了。

方案一,通過類文件的完整文件路徑來給 javap 指定類,修改 JNIFromJavaP.CreateFromClass(input_file, options) 方法的實(shí)現(xiàn)為:

@staticmethoddef CreateFromClass(class_file, options):if sys.platform == "darwin":class_name = class_fileelse:class_name = os.path.splitext(os.path.basename(class_file))[0]javap_path = os.path.abspath(options.javap)p = subprocess.Popen(args=[javap_path, '-c', '-verbose', '-s', class_name],cwd=os.path.dirname(class_file),stdout=subprocess.PIPE,stderr=subprocess.PIPE,universal_newlines=True)stdout, _ = p.communicate()jni_from_javap = JNIFromJavaP(stdout.split('\n'), options)return jni_from_javap

方案二,由于創(chuàng)建進(jìn)程執(zhí)行命令時(shí),設(shè)置了工作目錄,我們還可以通過類文件的文件名來給 javap 指定類,這修改 JNIFromJavaP.CreateFromClass(input_file, options) 方法的實(shí)現(xiàn)為:

@staticmethoddef CreateFromClass(class_file, options):if sys.platform == "darwin":class_name = os.path.basename(class_file)else:class_name = os.path.splitext(os.path.basename(class_file))[0]javap_path = os.path.abspath(options.javap)p = subprocess.Popen(args=[javap_path, '-c', '-verbose', '-s', class_name],cwd=os.path.dirname(class_file),stdout=subprocess.PIPE,stderr=subprocess.PIPE,universal_newlines=True)stdout, _ = p.communicate()jni_from_javap = JNIFromJavaP(stdout.split('\n'), options)return jni_from_javap

方案三,通過類路徑來給 javap 指定類,這修改 JNIFromJavaP.CreateFromClass(input_file, options) 方法的實(shí)現(xiàn)為:

@staticmethoddef CreateFromClass(class_file, options):if sys.platform == "darwin":path_items = class_file.split("/")i = len(path_items) - 2while i >= 0:class_name = path_items[i] + "." + class_nameif path_items[i] == "java":breaki = i -1else:class_name = os.path.splitext(os.path.basename(class_file))[0]javap_path = os.path.abspath(options.javap)p = subprocess.Popen(args=[javap_path, '-c', '-verbose', '-s', class_name],cwd=os.path.dirname(class_file),stdout=subprocess.PIPE,stderr=subprocess.PIPE,universal_newlines=True)stdout, _ = p.communicate()jni_from_javap = JNIFromJavaP(stdout.split('\n'), options)return jni_from_javap

方案三的這種實(shí)現(xiàn),對(duì)于要生成 JNI 的類有一定的限制。

相對(duì)來說,綜合考慮,方案二無疑是最好的。

(3). Android SDK 工具缺失或版本問題導(dǎo)致的編譯錯(cuò)誤

再次執(zhí)行 ninja,遇到如下編譯報(bào)錯(cuò):

OpenRTCClient % mv ~/Library/Android/sdk/cmdline-tools/latest ~/Library/Android/sdk/cmdline-tools/latest_bak OpenRTCClient % webrtc_build build android arm64 debug /Users/lisi/Projects/opensource/OpenRTCClient/build_system/tools/bin/mac/ninja -C /Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug ninja: Entering directory `/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug' [355/4574] ACTION //examples:AppRTCMobile_test_apk__test_apk__merge_manifests(//build/toolchain/android:android_clang_arm64) FAILED: gen/examples/AppRTCMobile_test_apk__test_apk_manifest/AndroidManifest.xml python3 ../../../../webrtc/build/android/gyp/merge_manifest.py --depfile gen/examples/AppRTCMobile_test_apk__test_apk__merge_manifests.d --android-sdk-cmdline-tools ../../../../../../../Library/Android/sdk/cmdline-tools/latest --root-manifest ../../../../webrtc/examples/androidtests/AndroidManifest.xml --output gen/examples/AppRTCMobile_test_apk__test_apk_manifest/AndroidManifest.xml --extras @FileArg\(gen/examples/AppRTCMobile_test_apk__test_apk.build_config.json:extra_android_manifests\) --min-sdk-version=21 --target-sdk-version=21 Traceback (most recent call last):File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/merge_manifest.py", line 149, in <module>main(sys.argv[1:])File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/merge_manifest.py", line 129, in mainbuild_utils.CheckOutput(File "/Users/lisi/Projects/opensource/OpenRTCClient/webrtc/build/android/gyp/util/build_utils.py", line 276, in CheckOutputraise CalledProcessError(cwd, args, stdout + stderr) util.build_utils.CalledProcessError: Command failed: ( cd /Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug; /Library/Java/JavaVirtualMachines/jdk-11.0.13.jdk/Contents/Home/bin/java -Xmx1G -noverify -cp ../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/build-system/manifest-merger.jar:../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/common/common.jar:../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/sdk-common/sdk-common.jar:../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/sdklib/sdklib.jar:../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/external/com/google/guava/guava/30.1-jre/guava-30.1-jre.jar:../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/external/kotlin-plugin-ij/Kotlin/kotlinc/lib/kotlin-stdlib.jar:../../../../../../../Library/Android/sdk/cmdline-tools/latest/lib/external/com/google/code/gson/gson/2.8.6/gson-2.8.6.jar com.android.manifmerger.Merger --out /Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/gen/examples/AppRTCMobile_test_apk__test_apk_manifest/tmpvg3qg_k3AndroidManifest.xml --property MIN_SDK_VERSION=21 --property TARGET_SDK_VERSION=21 --libs gen/third_party/android_sdk/android_test_base_java/AndroidManifest.xml:gen/third_party/android_sdk/android_test_runner_java/AndroidManifest.xml --main /var/folders/1x/5vtfxt410vbf9xhk8vvfz8l40000gn/T/AndroidManifest.xmlwu610lv1 --property PACKAGE=org.appspot.apprtc.test --remove-tools-declarations ) 錯(cuò)誤: 找不到或無法加載主類 com.android.manifmerger.Merger 原因: java.lang.ClassNotFoundException: com.android.manifmerger.Merger

這個(gè)報(bào)錯(cuò)是因?yàn)?#xff0c;編譯 Android 需要生成一些測(cè)試 APK 文件,此時(shí)需要執(zhí)行 Android SDK 中的一些 Java 工具,這里提示找不到的主類 com.android.manifmerger.Merger,其定義在 sdk/cmdline-tools/latest/lib/build-system/manifest-merger.jar 這個(gè) jar 文件中,但在我們的 SDK 中,沒有 sdk/cmdline-tools/latest/ 這個(gè)目錄。

不難看出 sdk/cmdline-tools/latest/ 是要引用最新版本的 cmdline-tools,但我們的 SDK 包中,只安裝了 3.0 版。

由此,可以有很多種方案來解決這個(gè)問題。

方案一,創(chuàng)建一個(gè)符號(hào)鏈接 sdk/cmdline-tools/latest 指向 sdk/cmdline-tools/3.0,如:

tmp % ln -s ~/Library/Android/sdk/cmdline-tools/3.0 ~/Library/Android/sdk/cmdline-tools/lastest

方案二,安裝最新版的 cmdline-tools,既可以通過 Android Studio 來完成,也可以通過 Android SDK 提供的命令行工具來做,如:

~/Library/Android/sdk/tools/bin/sdkmanager --install "cmdline-tools;latest"

如果發(fā)現(xiàn)安裝了最新版的 cmdline-tools 還是找不到主類 com.android.manifmerger.Merger,則可以看下 cmdline-tools 中是否有 ~/Library/Android/sdk/cmdline-tools/latest/lib/build-system/manifest-merger.jar 這個(gè) jar 文件:

OpenRTCClient % ls -l ~/Library/Android/sdk/cmdline-tools/latest/lib/build-system/ total 424 drwxr-xr-x 3 lisi staff 96 4 11 14:21 builder-model drwxr-xr-x 3 lisi staff 96 4 11 14:21 builder-test-api -rwxr-xr-x 1 lisi staff 213592 4 11 14:21 tools.manifest-merger.jar

如果是這種情況,可以拷貝 tools.manifest-merger.jar 或者為它創(chuàng)建符號(hào)鏈接,如:

OpenRTCClient % cp ~/Library/Android/sdk/cmdline-tools/latest/lib/build-system/tools.manifest-merger.jar ~/Library/Android/sdk/cmdline-tools/latest/lib/build-system/manifest-merger.jar

在上面的報(bào)錯(cuò)信息中,我們可以看到引用了多個(gè) jar 文件,對(duì)于其中的每一個(gè) jar 文件,我們都需要以類似這樣的方式確保它們的存在。

方案三,修改 WebRTC 的構(gòu)建配置。
這里的報(bào)錯(cuò),是在執(zhí)行 webrtc/build/config/android/internal_rules.gni 中定義的 template("merge_manifests") 時(shí)報(bào)出的,cmdline-tools 的路徑是在這里定義的,如:

template("merge_manifests") {action_with_pydeps(target_name) {forward_variables_from(invoker, TESTONLY_AND_VISIBILITY + [ "deps" ])script = "//build/android/gyp/merge_manifest.py"depfile = "$target_gen_dir/$target_name.d"inputs = [invoker.build_config,invoker.input_manifest,]outputs = [ invoker.output_manifest ]_rebased_build_config = rebase_path(invoker.build_config, root_build_dir)args = ["--depfile",rebase_path(depfile, root_build_dir),"--android-sdk-cmdline-tools",rebase_path("${android_sdk_root}/cmdline-tools/latest",root_build_dir),"--root-manifest",rebase_path(invoker.input_manifest, root_build_dir),"--output",rebase_path(invoker.output_manifest, root_build_dir),"--extras","@FileArg($_rebased_build_config:extra_android_manifests)","--min-sdk-version=${invoker.min_sdk_version}","--target-sdk-version=${invoker.target_sdk_version}",]

可以將這里的 cmdline-tools 的路徑修改為我們本地已經(jīng)安裝的版本的路徑。

(4). Clang 缺少 Android NDK 包的庫或工具導(dǎo)致編譯失敗

再次執(zhí)行 ninja,遇到如下編譯報(bào)錯(cuò):

OpenRTCClient % webrtc_build build android arm64 debug /Users/lisi/Projects/opensource/OpenRTCClient/build_system/tools/bin/mac/ninja -C /Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug ninja: Entering directory `/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug' [14/1093] LINK ./stun_prober FAILED: stun_prober exe.unstripped/stun_prober python3 "../../../../webrtc/build/toolchain/gcc_link_wrapper.py" --output="./stun_prober" --strip="../../../../build_system/llvm-build/mac/mac/Release+Asserts/bin/llvm-strip" --unstripped-file="./exe.unstripped/stun_prober" -- ../../../../build_system/llvm-build/mac/mac/Release+Asserts/bin/clang++ -fuse-ld=lld -Wl,--fatal-warnings -Wl,--build-id -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,max-page-size=4096 -Wl,--color-diagnostics -Wl,--no-rosegment -Wl,--no-call-graph-profile-sort -Wl,--exclude-libs=libvpx_assembly_arm.a --unwindlib=none --target=aarch64-linux-android21 -Wl,-mllvm,-enable-machine-outliner=never -no-canonical-prefixes -Wl,--gc-sections -Wl,--gdb-index --sysroot=../../../../../../../Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -Wl,--warn-shared-textrel -Wl,-z,defs -Wl,--as-needed -pie -Bdynamic -Wl,-z,nocopyreloc -Wl,--dynamic-linker,/system/bin/linker64 -o "./exe.unstripped/stun_prober" -Wl,--start-group @"./stun_prober.rsp" -Wl,--end-group -ldl -lm -llog -lGLESv2 -lOpenSLES ld.lld: error: cannot open ../../../../build_system/llvm-build/mac/mac/Release+Asserts/lib/clang/14.0.0/lib/linux/libclang_rt.builtins-aarch64-android.a: No such file or directory ld.lld: error: cannot open ../../../../build_system/llvm-build/mac/mac/Release+Asserts/lib/clang/14.0.0/lib/linux/libclang_rt.builtins-aarch64-android.a: No such file or directory clang++: error: linker command failed with exit code 1 (use -v to see invocation)

這是由于 webrtc 中的 LLVM 工具鏈中缺少編譯鏈接 Android 二進(jìn)制文件所需的一些庫文件。這可以通過將 NDK 中的庫文件拷貝的 LLVM 工具鏈的對(duì)應(yīng)目錄下來解決,如:

android-ndk-r23b-darwin % cp -r toolchains/llvm/prebuilt/darwin-x86_64//lib64/clang/12.0.8/lib/linux ~/Projects/opensource/OpenRTCClient/build_system/llvm-build/mac/mac/Release+Asserts/lib/clang/14.0.0/lib/

再次執(zhí)行 ninja,遇到如下編譯報(bào)錯(cuò):

OpenRTCClient % webrtc_build build android arm64 debug /Users/lisi/Projects/opensource/OpenRTCClient/build_system/tools/bin/mac/ninja -C /Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug ninja: Entering directory `/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug' [33/880] LINK ./stun_prober FAILED: stun_prober exe.unstripped/stun_prober python3 "../../../../webrtc/build/toolchain/gcc_link_wrapper.py" --output="./stun_prober" --strip="../../../../build_system/llvm-build/mac/mac/Release+Asserts/bin/llvm-strip" --unstripped-file="./exe.unstripped/stun_prober" -- ../../../../build_system/llvm-build/mac/mac/Release+Asserts/bin/clang++ -fuse-ld=lld -Wl,--fatal-warnings -Wl,--build-id -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,max-page-size=4096 -Wl,--color-diagnostics -Wl,--no-rosegment -Wl,--no-call-graph-profile-sort -Wl,--exclude-libs=libvpx_assembly_arm.a --unwindlib=none --target=aarch64-linux-android21 -Wl,-mllvm,-enable-machine-outliner=never -no-canonical-prefixes -Wl,--gc-sections -Wl,--gdb-index --sysroot=../../../../../../../Library/Android/sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/darwin-x86_64/sysroot -Wl,--warn-shared-textrel -Wl,-z,defs -Wl,--as-needed -pie -Bdynamic -Wl,-z,nocopyreloc -Wl,--dynamic-linker,/system/bin/linker64 -o "./exe.unstripped/stun_prober" -Wl,--start-group @"./stun_prober.rsp" -Wl,--end-group -ldl -lm -llog -lGLESv2 -lOpenSLES Traceback (most recent call last):File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/toolchain/gcc_link_wrapper.py", line 91, in <module>sys.exit(main())File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/toolchain/gcc_link_wrapper.py", line 78, in mainresult = subprocess.call(File "/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 349, in callwith Popen(*popenargs, **kwargs) as p:File "/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 951, in __init__self._execute_child(args, executable, preexec_fn, close_fds,File "/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 1821, in _execute_childraise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: '../../../../build_system/llvm-build/mac/mac/Release+Asserts/bin/llvm-strip'

這個(gè)報(bào)錯(cuò)是說,在鏈接的時(shí)候,找不到 LLVM 工具鏈中的 llvm-strip。

同樣,我們將 NDK 下的工具拷貝過去,同時(shí)也要將依賴的庫拷貝過去:

android-ndk-r23b-darwin % cp toolchains/llvm/prebuilt/darwin-x86_64/bin/llvm-strip /Users/lisi/Projects/opensource/OpenRTCClient/build_system/llvm-build/mac/mac/Release+Asserts/bin/ android-ndk-r23b-darwin % cp -r toolchains/llvm/prebuilt/darwin-x86_64/lib64 /Users/lisi/Projects/opensource/OpenRTCClient/build_system/llvm-build/mac/mac/Release+Asserts/

要做同樣處理的還有 llvm-nm 工具:

android-ndk-r23b-darwin % cp toolchains/llvm/prebuilt/darwin-x86_64/bin/llvm-nm /Users/lisi/Projects/opensource/OpenRTCClient/build_system/llvm-build/mac/mac/Release+Asserts/bin/

(5). Unix 域 Socket 地址錯(cuò)誤導(dǎo)致的編譯失敗

再次執(zhí)行 ninja,遇到如下編譯報(bào)錯(cuò):

OpenRTCClient % webrtc_build build android arm64 debug /Users/lisi/Projects/opensource/OpenRTCClient/build_system/tools/bin/mac/ninja -C /Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug ninja: Entering directory `/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug' [7/744] ACTION //sdk/android:base_java__errorprone(//build/toolchain/android:android_clang_arm64) FAILED: obj/sdk/android/base_java__errorprone.errorprone.stamp python3 ../../../../webrtc/build/android/gyp/compile_java.py --depfile=gen/sdk/android/base_java__errorprone.d --generated-dir=gen/sdk/android/base_java/generated_java --jar-path=obj/sdk/android/base_java__errorprone.errorprone.stamp --java-srcjars=\[\"gen/sdk/android/base_java.generated.srcjar\"\] --target-name //sdk/android:base_java__errorprone --header-jar obj/sdk/android/base_java.turbine.jar --classpath=\[\"obj/sdk/android/base_java.turbine.jar\"\] --classpath=@FileArg\(gen/sdk/android/base_java.build_config.json:deps_info:javac_full_interface_classpath\) --java-version=1.8 --bootclasspath=@FileArg\(gen/sdk/android/base_java.build_config.json:android:sdk_interface_jars\) --chromium-code=1 --jar-info-exclude-globs=\[\"\*/R.class\",\ \"\*/R\\\$\*.class\",\ \"\*/Manifest.class\",\ \"\*/Manifest\\\$\*.class\",\ \"\*/GEN_JNI.class\"\] --processorpath=@FileArg\(gen/tools/android/errorprone_plugin/errorprone_plugin.build_config.json:deps_info:host_classpath\) --enable-errorprone @gen/sdk/android/base_java.sources --javac-arg=-Werror Traceback (most recent call last):File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_java.py", line 800, in <module>sys.exit(main(sys.argv[1:]))File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_java.py", line 693, in mainand server_utils.MaybeRunCommand(name=options.target_name,File "/Users/lisi/Projects/opensource/OpenRTCClient/webrtc/build/android/gyp/util/server_utils.py", line 40, in MaybeRunCommandraise eFile "/Users/lisi/Projects/opensource/OpenRTCClient/webrtc/build/android/gyp/util/server_utils.py", line 27, in MaybeRunCommandsock.connect(SOCKET_ADDRESS) FileNotFoundError: [Errno 2] No such file or directory

在 webrtc/build/android/gyp/util/server_utils.py 文件中,我們可以看到 SOCKET_ADDRESS 的定義:

SOCKET_ADDRESS = '\0chromium_build_server_socket'

最前面的 ‘\0’ 導(dǎo)致在 Mac 上創(chuàng)建 unix 域 socket 失敗,并設(shè)置它為臨時(shí)目錄下的一個(gè)路徑,如:

SOCKET_ADDRESS = '/tmp/chromium_build_server_socket'

同時(shí),還有把 Unix 域 socket 的 server 端跑起來,如:

OpenRTCClient % python3 webrtc/build/android/fast_local_dev_server.py

(6). 編譯資源失敗

再次執(zhí)行 ninja,遇到如下編譯報(bào)錯(cuò):

[20/692] ACTION //examples:AppRTCMobile__compile_resources(//build/toolchain/android:android_clang_arm64) FAILED: gen/examples/AppRTCMobile__compile_resources.srcjar obj/examples/AppRTCMobile.ap_ obj/examples/AppRTCMobile.ap_.info gen/examples/AppRTCMobile__compile_resources_R.txt obj/examples/AppRTCMobile/AppRTCMobile.resources.proguard.txt gen/examples/AppRTCMobile__compile_resources.resource_ids python3 ../../../../webrtc/build/android/gyp/compile_resources.py --include-resources=@FileArg\(gen/examples/AppRTCMobile.build_config.json:android:sdk_jars\) --aapt2-path ../../../../webrtc/third_party/android_build_tools/aapt2/aapt2 --dependencies-res-zips=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:dependency_zips\) --extra-res-packages=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:extra_package_names\) --extra-main-r-text-files=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:extra_main_r_text_files\) --min-sdk-version=21 --target-sdk-version=29 --webp-cache-dir=obj/android-webp-cache --android-manifest gen/examples/AppRTCMobile_manifest/AndroidManifest.xml --srcjar-out gen/examples/AppRTCMobile__compile_resources.srcjar --version-code 1 --version-name Developer\ Build --arsc-path obj/examples/AppRTCMobile.ap_ --info-path obj/examples/AppRTCMobile.ap_.info --debuggable --r-text-out gen/examples/AppRTCMobile__compile_resources_R.txt --dependencies-res-zip-overlays=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:dependency_zips\) --proguard-file obj/examples/AppRTCMobile/AppRTCMobile.resources.proguard.txt --emit-ids-out=gen/examples/AppRTCMobile__compile_resources.resource_ids --depfile gen/examples/AppRTCMobile__compile_resources.d E 3273 2236 Subprocess raised an exception: Traceback (most recent call last):File "/Users/lisi/Projects/opensource/OpenRTCClient/webrtc/build/android/gyp/util/parallel.py", line 75, in __call__return self._func(*_fork_params[index], **_fork_kwargs) TypeError: 'NoneType' object is not subscriptable

這里我們通過把資源編譯的并發(fā)編譯給關(guān)掉來解決這個(gè)問題。具體來說,可以修改 webrtc/build/android/gyp/util/parallel.py 這個(gè)文件,將文件中的 DISABLE_ASYNC 設(shè)置為 True,或者導(dǎo)出環(huán)境變量 export DISABLE_ASYNC=1。

(7). aapt 可執(zhí)行文件格式錯(cuò)誤導(dǎo)致編譯失敗

再次執(zhí)行 ninja,遇到如下編譯報(bào)錯(cuò):

[36/579] ACTION //examples:AppRTCMobile__compile_resources(//build/toolchain/android:android_clang_arm64) FAILED: gen/examples/AppRTCMobile__compile_resources.srcjar obj/examples/AppRTCMobile.ap_ obj/examples/AppRTCMobile.ap_.info gen/examples/AppRTCMobile__compile_resources_R.txt obj/examples/AppRTCMobile/AppRTCMobile.resources.proguard.txt gen/examples/AppRTCMobile__compile_resources.resource_ids python3 ../../../../webrtc/build/android/gyp/compile_resources.py --include-resources=@FileArg\(gen/examples/AppRTCMobile.build_config.json:android:sdk_jars\) --aapt2-path ../../../../webrtc/third_party/android_build_tools/aapt2/aapt2 --dependencies-res-zips=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:dependency_zips\) --extra-res-packages=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:extra_package_names\) --extra-main-r-text-files=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:extra_main_r_text_files\) --min-sdk-version=21 --target-sdk-version=29 --webp-cache-dir=obj/android-webp-cache --android-manifest gen/examples/AppRTCMobile_manifest/AndroidManifest.xml --srcjar-out gen/examples/AppRTCMobile__compile_resources.srcjar --version-code 1 --version-name Developer\ Build --arsc-path obj/examples/AppRTCMobile.ap_ --info-path obj/examples/AppRTCMobile.ap_.info --debuggable --r-text-out gen/examples/AppRTCMobile__compile_resources_R.txt --dependencies-res-zip-overlays=@FileArg\(gen/examples/AppRTCMobile.build_config.json:deps_info:dependency_zips\) --proguard-file obj/examples/AppRTCMobile/AppRTCMobile.resources.proguard.txt --emit-ids-out=gen/examples/AppRTCMobile__compile_resources.resource_ids --depfile gen/examples/AppRTCMobile__compile_resources.d WARNING:root:Running in synchronous mode. Traceback (most recent call last):File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_resources.py", line 1039, in <module>main(sys.argv[1:])File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_resources.py", line 956, in mainmanifest_package_name = _PackageApk(options, build)File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_resources.py", line 759, in _PackageApkpartials = _CompileDeps(options.aapt2_path, dep_subdirs,File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_resources.py", line 619, in _CompileDepspartials = lisi(File "/Users/lisi/Projects/opensource/OpenRTCClient/webrtc/build/android/gyp/util/parallel.py", line 207, in BulkForkAndCallyield func(*args, **kwargs)File "/Users/lisi/Projects/opensource/OpenRTCClient/build/android/arm64/debug/../../../../webrtc/build/android/gyp/compile_resources.py", line 583, in _CompileSingleDepbuild_utils.CheckOutput(File "/Users/lisi/Projects/opensource/OpenRTCClient/webrtc/build/android/gyp/util/build_utils.py", line 260, in CheckOutputchild = subprocess.Popen(args,File "/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 951, in __init__self._execute_child(args, executable, preexec_fn, close_fds,File "/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 1821, in _execute_childraise child_exception_type(errno_num, err_msg, err_filename) OSError: [Errno 8] Exec format error: '../../../../webrtc/third_party/android_build_tools/aapt2/aapt2'

這是由于 webrtc/third_party/android_build_tools/aapt2/aapt2 文件實(shí)際上為 Linux 平臺(tái)的可執(zhí)行文件。

編譯資源的 template 在 webrtc/build/config/android/internal_rules.gni 中定義:

template("compile_resources") {forward_variables_from(invoker, TESTONLY_AND_VISIBILITY)_deps = [invoker.android_sdk_dep,invoker.build_config_dep,]if (defined(invoker.android_manifest_dep)) {_deps += [ invoker.android_manifest_dep ]}foreach(_dep, invoker.deps) {_target_label = get_label_info(_dep, "label_no_toolchain")if (filter_exclude([ _target_label ], _java_library_patterns) == [] &&filter_exclude([ _target_label ], _java_resource_patterns) != []) {# Depend on the java libraries' transitive __assetres target instead._deps += [ "${_target_label}__assetres" ]} else {_deps += [ _dep ]}}if (defined(invoker.arsc_output)) {_arsc_output = invoker.arsc_output}_final_srcjar_path = "${target_gen_dir}/${target_name}.srcjar"_script = "//build/android/gyp/compile_resources.py"_inputs = [invoker.build_config,android_sdk_tools_bundle_aapt2,]_rebased_build_config = rebase_path(invoker.build_config, root_build_dir)_args = ["--include-resources=@FileArg($_rebased_build_config:android:sdk_jars)","--aapt2-path",rebase_path(android_sdk_tools_bundle_aapt2, root_build_dir),"--dependencies-res-zips=@FileArg($_rebased_build_config:deps_info:dependency_zips)","--extra-res-packages=@FileArg($_rebased_build_config:deps_info:extra_package_names)","--extra-main-r-text-files=@FileArg($_rebased_build_config:deps_info:extra_main_r_text_files)","--min-sdk-version=${invoker.min_sdk_version}","--target-sdk-version=${invoker.target_sdk_version}","--webp-cache-dir=obj/android-webp-cache",]

其中會(huì)調(diào)用腳本文件 webrtc/build/android/gyp/compile_resources.py 并傳入 aapt2 的路徑作為其中的一個(gè)參數(shù)。可以看到這里引用的 aapt2 的路徑為 android_sdk_tools_bundle_aapt2。android_sdk_tools_bundle_aapt2 是一個(gè)編譯配置項(xiàng),其定義在 webrtc/build/config/android/config.gni 中,這個(gè)配置項(xiàng)有默認(rèn)值:

android_sdk_tools_bundle_aapt2_dir ="//third_party/android_build_tools/aapt2". . . . . .android_sdk_tools_bundle_aapt2 = "${android_sdk_tools_bundle_aapt2_dir}/aapt2"

我們可以通過在 args.gn 中定制 android_sdk_tools_bundle_aapt2_dir 這個(gè)配置項(xiàng)來解決這個(gè)問題。具體來說,需要將這個(gè)配置項(xiàng)設(shè)置為 Android SDK 中我們選擇的 build-tools 的路徑,如下:

android_sdk_tools_bundle_aapt2_dir = "/Users/lisi/Library/Android/sdk/build-tools/30.0.1"

再次再次執(zhí)行 ninja,可以正確編譯出各個(gè)需要的文件。

筆者在 GitHub 上建了一個(gè)倉庫,放了 WebRTC 完整的代碼以及構(gòu)建系統(tǒng),包括 WebRTC 的源碼及其依賴的第三方庫,編譯所需要的各種工具等,其中主要針對(duì) WebRTC 的 m98 版,搭建了整個(gè)的構(gòu)建環(huán)境,地址為 OpenRTCClient,有需要的朋友可以參考一些。

Done.

總結(jié)

以上是生活随笔為你收集整理的在 Mac 上为 Android 编译 WebRTC的全部?jī)?nèi)容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò),歡迎將生活随笔推薦給好友。