遇到错误怎么办:ndk-build.cmd‘‘ finished with non-zero exit value 2

简介: 遇到错误怎么办:ndk-build.cmd‘‘ finished with non-zero exit value 2

只要是so编译有问题,都是报这个错误。


揭示错误

Execution failed for task ':libusb4javajni:ndkBuild'.
> Process 'command 'D:\SOFTWARES\DEVELOP\android-ndk-r16b/ndk-build.cmd'' finished with non-zero exit value 2
* 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.

自行编译查看具体错误

D:\Nanjing-SVN\UsbCamera-BulkTransfer\libusb4javajni\src\main\jni\libusb4java>D:
\SOFTWARES\DEVELOP\android-ndk-r16b/ndk-build.cmd
Android NDK: WARNING: APP_PLATFORM android-14 is higher than android:minSdkVersi
on 1 in D:/Nanjing-SVN/UsbCamera-BulkTransfer/libusb4javajni/src/main/AndroidMan
ifest.xml. NDK binaries will *not* be comptible with devices older than android-
14. See https://android.googlesource.com/platform/ndk/+/master/docs/user/common_
problems.md for more information.
D:/SOFTWARES/DEVELOP/android-ndk-r16b/build//../build/core/setup-app.mk:81: Andr
oid NDK: Application targets deprecated ABI(s): armeabi
D:/SOFTWARES/DEVELOP/android-ndk-r16b/build//../build/core/setup-app.mk:82: Andr
oid NDK: Support for these ABIs will be removed in a future NDK release.
D:/Nanjing-SVN/UsbCamera-BulkTransfer/libusb4javajni/src/main/jni/Android.mk:7:
D:/Nanjing-SVN/UsbCamera-BulkTransfer/libusb4javajni/src/main/jni/libuvc/android
/jni/Android.mk: No such file or directory
D:/Nanjing-SVN/UsbCamera-BulkTransfer/libusb4javajni/src/main/jni/Android.mk:7:
D:/Nanjing-SVN/UsbCamera-BulkTransfer/libusb4javajni/src/main/jni/libuvc/android
/jni/Android.mk: No such file or directory
make: *** No rule to make target `D:/Nanjing-SVN/UsbCamera-BulkTransfer/libusb4j
avajni/src/main/jni/libuvc/android/jni/Android.mk'.  Stop.


想办法解决即可。

目录
相关文章
|
2月前
|
Shell 开发工具 Android开发
详解sh ndk-build.cmd command not found
【4月更文挑战第2天】
|
2月前
|
NoSQL C语言
vscode出现 ERROR: Unable to start debugging. Unexpected GDB output from command “-exec-run“.
vscode出现 ERROR: Unable to start debugging. Unexpected GDB output from command “-exec-run“.
696 0
|
2月前
解决运行qmake:Project ERROR: Cannot run compiler ‘cl‘. Output:
解决运行qmake:Project ERROR: Cannot run compiler ‘cl‘. Output:
285 0
|
11月前
|
C语言
安装mujoco报错:distutils.errors.DistutilsExecError: command ‘gcc‘ failed with exit status 1
安装mujoco报错:distutils.errors.DistutilsExecError: command ‘gcc‘ failed with exit status 1
392 0
|
Python
Pycharm报错:Process finished with exit code -1066598274 (0xC06D007E)
Pycharm报错:Process finished with exit code -1066598274 (0xC06D007E)
340 0
|
Android开发
ndk-build.cmd‘‘ finished with non-zero exit value 2
ndk-build.cmd‘‘ finished with non-zero exit value 2
169 0
ndk-build.cmd‘‘ finished with non-zero exit value 2
首次运行Flutter失败报错(Finished with error: Gradle task assembleDebug failed with exit code 1)
首次运行Flutter失败报错(Finished with error: Gradle task assembleDebug failed with exit code 1)
330 0
首次运行Flutter失败报错(Finished with error: Gradle task assembleDebug failed with exit code 1)
|
JavaScript Linux Windows
imagemagick安装调用报错command failed
记录下通过nodejs调用imagemagick 的时候发现的一个错误,command failed -- crop .
imagemagick安装调用报错command failed
|
iOS开发
iOS linker command failed with exit code 1 (use -v to see invocation)解决方法
iOS linker command failed with exit code 1 (use -v to see invocation)解决方法
1828 0
|
Ubuntu Shell
脚本执行常见错误:build.sh: caller: not found
从Ubuntu 6.10开始,默认使用dash(theDebian Almquist Shell)而不是bash(the GNUBourne-Again Shell)但Login Shell还是bash. 原因是dash更快、更高效,而且它符合POSIX规范。Ubuntu在启动的时候会运行很多shell脚本,使用dash可以加快启动速度。
172 0