"no rule to make target" when compiling only one .c file with ndk-build.cmd launched from gradle [36991389]

Fixed

Bug

[AOSP] Released

[AOSP] FutureRelease

Migrated-Tools-Studio

Status Update

No update yet.

Description

xh...@novetys.com

created issue #1

Mar 10, 2014 04:13PM

Version of Android Studio (available in the about box): 0.5.1
OS version: Windows 8.1
Java JRE/JDK version: 1.7.0_51 64bits

gradle version: 1.11
android-plugin version: 0.9.0
NDK version: r9d 64bits

When building ndkJniLib sample from the gradle-samples-0.9 on windows I get this error:
make.exe: *** No rule to make target `C:\Users\xhallade\Desktop\ndkJniLib\lib\build\ndk\release\obj/local/armeabi-v7a/objs/hellojni/C_\Users\xhallade\Desktop\ndkJniLib\lib\src\main\jni', needed by `C:\Users\xhallade\Desktop\ndkJniLib\lib\build\ndk\release\obj/local/armeabi-v7a/objs/hellojni/C_\Users\xhallade\Desktop\ndkJniLib\lib\src\main\jni\hello-jni.o'.
Stop.

If I create a new empty .c file aside hello-jni.c and run gradle again, the .so files are getting generated correctly.
In fact instead of calling gradle again, I can edit myself the generated Android.mk and add the second file to fix this.
When I re-run the ndk-build command line issue by gradle everything compiles fine, so the root cause seem to come from the NDK and not from the build system.

The command issued by gradle:
C:\Android\ndk\ndk-build.cmd NDK_PROJECT_PATH=null APP_BUILD_SCRIPT=C:\Users\xhallade\Desktop\ndkJniLib\lib\build\ndk\release\Android.mk APP_PLATFORM=android-19 NDK_OUT=C:\Users\xhallade\Desktop\ndkJniLib\lib\build\ndk\release\obj NDK_LIBS_OUT=C:\Users\xhallade\Desktop\ndkJniLib\lib\build\ndk\release\lib APP_ABI=all

The generated Android.mk:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)

LOCAL_MODULE := hellojni
LOCAL_SRC_FILES := \
C:\Users\xhallade\Desktop\ndkJniLib\lib\src\main\jni\hello-jni.c \

LOCAL_C_INCLUDES += C:\Users\xhallade\Desktop\ndkJniLib\lib\src\main\jni
LOCAL_C_INCLUDES += C:\Users\xhallade\Desktop\ndkJniLib\lib\src\release\jni

include $(BUILD_SHARED_LIBRARY)

They are the same in both cases - only the reference to the other .c file is added in Android.mk when it's there.

The sample is attached.

ndkJniLib.zip

195 KB

Download

Comments

xa...@android.com <xa...@android.com> Mar 10, 2014 05:41PM

Assigned to an...@google.com.

ch...@gmail.com <ch...@gmail.com> #2Mar 31, 2014 10:02PM

Hi,

would you try to boot emulator with this command line flag:

-feature -Vulkan

and let us know if it fixes the issue for you? Also would you tell us what graphics card you are using and what is the graphics driver version?

dm...@gmail.com <dm...@gmail.com> #3Aug 6, 2014 09:02AM

The feature flag did solve the issue for me. Thank you very much. I don't use a dedicated graphics card. Only the internal one from the CPU.

pa...@gmail.com <pa...@gmail.com> #4Mar 13, 2015 10:38AM

Your integrated GPU is supposed to support Vulkan 1.2. I would need more work to figure out why it crashes without that flag.

xa...@android.com <xa...@android.com> #5Mar 18, 2015 09:49PM

Status: Won't Fix (Obsolete)

If there is more information that I can provide please let me know.

an...@google.com <an...@google.com> #6Apr 7, 2015 09:17AM

Marked as fixed.

Thanks. Would you help me to try some more runs to isolate the root cause? Please try to run the emulator with this flag:

-feature -GLDirectMem,-GLDMA,-GLDMA2

I am suspecting the Vulkan direct memory access and coherent mapping is causing the issue.

Issue 36991389