Untitled conversation
- User
[CXX1429] error when building with ndkBuild using E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\src\main\jni\Android.mk: Android NDK: Your APP_BUILD_SCRIPT points to an unknown file: E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\src\main\jni\Android.mk
C++ build system [configure] failed while executing: @echo off "C:\Users\BMV3\AppData\Local\Android\Sdk\ndk\25.1.8937393\ndk-build.cmd" ^ "NDK_PROJECT_PATH=null" ^ "APP_BUILD_SCRIPT=E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\src\main\jni\Android.mk" ^ "NDK_APPLICATION_MK=E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\src\main\jni\Application.mk" ^ "APP_ABI=arm64-v8a" ^ "NDK_ALL_ABIS=arm64-v8a" ^ "NDK_DEBUG=1" ^ "APP_PLATFORM=android-26" ^ "NDK_OUT=E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\build\intermediates\cxx\Debug\6h295i67/obj" ^ "NDK_LIBS_OUT=E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\build\intermediates\cxx\Debug\6h295i67/lib" ^ "APP_SHORT_COMMANDS=false" ^ "LOCAL_SHORT_COMMANDS=false" ^ -B ^ -n from E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app C:/Users/BMV3/AppData/Local/Android/Sdk/ndk/25.1.8937393/build/../build/core/add-application.mk:88: *** Android NDK: Aborting... . Stop. Affected Modules: app
Assistant
This error is occurring because ndkBuild cannot find the Android.mk file you have specified. There are a few things you can check:
- Make sure the path to Android.mk is correct. In your case, it should be:
APP_BUILD_SCRIPT=E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app\src\main\jni\Android.mk
Double check that this path exists and Android.mk is present there.
- Make sure you are running ndkBuild from the app/ directory, which is the same level as src/. So your full command should be:
cd E:\Dhruvin kheni\Backup\Backup\Pancard_pe_loan\Pancard_pe_loan\app ndk-build
-
Make sure the Android.mk file has proper syntax. You can check example Android.mk files in the NDK samples.
-
Try running ndk-build without any arguments first to make sure the basic setup is correct. Then you can add the APP_BUILD_SCRIPT argument.
-
Make sure the NDK path is set properly. You can check this by running:
echo %NDK_ROOT%
It should print the path to your Android NDK.
Let me know if any of these steps help resolve the issue. I can provide more specific help if you can share your Android.mk file contents.
- User
[{0}] Failed to resolve name. status={1}
Assistant
This error means that CMake was unable to resolve a name (likely a target name) that was used in your CMake code. Some things to check:
-
Make sure the name is spelled correctly. CMake is case-sensitive.
-
Make sure the name is in scope. If you are using an add_subdirectory() call, the names of targets in the subdirectory will not be in the parent scope. You need to prefix them with the subdirectory name.
-
Make sure the target has been created already. Forward references to targets are not allowed. Targets must be created before they are used.
-
Make sure the target is in the global namespace. If a target is added using add_library() or add_executable() without the GLOBAL keyword, it will be in the local namespace only.
-
Make sure you are not using a target that was created in a different directory. Each directory has its own scope, and names of targets in one directory do not conflict with names of targets in other directories.
-
Make sure you are not using generator expressions without properly setting up the target dependencies. Generator expressions can only be used in dependencies of targets, not standalone.
-
Double check that the name does not refer to a CMake variable or cache entry. Those have their own syntax (${VAR} and CACHE{VAR} respectively).
Some examples of resolving this error:
# Wrong, should be add_subdirectory(sub) add_subdirectory(subdir) add_executable(exe sub/target.c) # Error, sub/target.c is not in scope # Correct add_subdirectory(sub) add_executable(exe sub/target.c) # Wrong, forward reference add_executable(exe target.c) add_library(target lib.c) # Correct add_library(target lib.c) add_executable(exe target.c) # Wrong add_library(mytarget lib.c) target_link_libraries(mytarget PUBLIC ${mytarget}) # Correct add_library(mytarget lib.c) target_link_libraries(mytarget PUBLIC mytarget)Let me know if you have any other questions!
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.