libplayer.so', missing and no known rule to make it

[aiquantong]

HI 大家编译的时候是否遇到这个问题

IDE：Android Studio Giraffe | 2022.3.1 Patch 2 JAVA： JetBrians Runtime Version 17.0

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.

• What went wrong: Execution failed for task ':app:buildCMakeDebug[arm64-v8a]'.

Build command failed. Error while executing process /Users/aiquantong/Library/Android/sdk/cmake/3.18.1/bin/ninja with arguments {-C /Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/metaplayer5_android/app/.cxx/Debug/4753253o/arm64-v8a player} ninja: Entering directory `/Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/metaplayer5_android/app/.cxx/Debug/4753253o/arm64-v8a'

ninja: error: '/Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/bin/lib_android/arm64-v8a/libmetartc5.a', needed by '/Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/metaplayer5_android/app/build/intermediates/cxx/Debug/4753253o/obj/arm64-v8a/libplayer.so', missing and no known rule to make it

• Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. ==============================================================================

2: Task failed with an exception.

• What went wrong: Execution failed for task ':app:buildCMakeDebug[x86_64]'.

Build command failed. Error while executing process /Users/aiquantong/Library/Android/sdk/cmake/3.18.1/bin/ninja with arguments {-C /Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/metaplayer5_android/app/.cxx/Debug/4753253o/x86_64 player} ninja: Entering directory `/Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/metaplayer5_android/app/.cxx/Debug/4753253o/x86_64'

ninja: error: '/Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/bin/lib_android/x86_64/libmetartc5.a', needed by '/Users/aiquantong/Documents/AndroidOpenSource/yangwebrtc/metaplayer5_android/app/build/intermediates/cxx/Debug/4753253o/obj/x86_64/libplayer.so', missing and no known rule to make it

• Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. ==============================================================================

• Get more help at https://help.gradle.org

BUILD FAILED in 6s