Databases
StackOverflow2013
Postsdbo
POYour APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POYour APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
    primarykey
    data
    text
    <p>I am trying to get ndk-gdb to work but I have some problems.</p> <p>My project structure is something like this:</p> <pre><code>trunk --indiana (Here is the android_manifest) --ubravo_java ----mbravo (here is the native code) ------jni (here are the Android.mk and Application.mk) </code></pre> <p>Question 1: I understand that I probably have to run ndk-gdb from the directory where the manifest is located correct? Or I provide the --project parameter to the ndk-gdb command.</p> <p>So if I try to launch the ndk-gdb like this:</p> <pre><code>ndk-gdb --start --force --verbose --project=/home/johan/projects/indiana2/trunk/indiana </code></pre> <p>I get this output which to me indicates that it is tryin to find the Android.mk directly in the subfolder of the main project where the android_manifest file is located but I might be wrong.</p> <pre><code>Android NDK installation path: /home/johan/android-ndk-r7 Using default adb command: /home/johan/android-sdk-linux/platform-tools//adb ADB version found: Android Debug Bridge version 1.0.29 Using final ADB command: '/home/johan/android-sdk-linux/platform-tools//adb' Using specified project path: /home/johan/projects/indiana2/trunk/indiana Found package name: net.genaker.indiana /home/johan/android-ndk-r7/build/core/add-application.mk:133: *** Android NDK: Aborting... . Stop. ABIs targetted by application: Android NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk Device API Level: 10 Device CPU ABIs: armeabi-v7a armeabi ERROR: The device does not support the application's targetted CPU ABIs! Device supports: armeabi-v7a armeabi Package supports: Android NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk </code></pre> <p>My APP_BUILD_SCRIPT path in Application.mk looks like this:</p> <blockquote> <p>APP_BUILD_SCRIPT := $(APP_PROJECT_PATH)/jni/Android.mk</p> </blockquote> <p>But here I am not sure what the APP_PROJECT_PATH is referring to. I have also tried to hardcode the full path to the Android.mk file like /home/johan/projects/... etc but the error still comes out with: </p> <blockquote> <p>Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk</p> </blockquote> <p>so it seems as the path is not changed like it is not even looking at my Application.mk. </p> <p>I have tried to search the full trunk dir for references to APP_PROJECT_PATH and this parameter is only defined in this folder in this Application.mk. I just assume that I am able to create a project and debug it without having the /jni folder as a subfolder directly underneath the folder which contains the manifest file right?</p> <p>Any hints appreciated on how to get the debugging working.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjww
    1. USuser1192315
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POYour APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODid you ever find a solution to this problem?
      singulars
      1. POYour APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. USJoe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload