Databases
StackOverflow2013
Postsdbo
POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
    primarykey
    data
    text
    <p>Well, I have seen 4 similiar questions in stackoverflow (<a href="https://stackoverflow.com/questions/6494567/android-ndk-your-app-build-script-points-to-an-unknown-file">this</a>, <a href="https://stackoverflow.com/questions/10696005/android-ndk-your-app-build-script-points-to-an-unknown-file">this</a>, <a href="https://stackoverflow.com/questions/9359568/android-ndk-gdb-your-app-build-script-points-to-an-unknown-file-jni-android">this</a> and <a href="https://stackoverflow.com/questions/10632234/android-ndk-r8-windows-android-ndk-your-app-build-script-points-to-an-unknown">this</a>). And I tried the answers given there. I must say one answer worked for me, but the documentation clearly say not to use that method. So here I am asking..</p> <h2>My project setup</h2> <ol> <li>Running on Mac OS X Mountain Lion 10.8.2, Eclipse Juno, gcc 4.2.1, GNU Make 3.8.1.</li> <li>My project is a test project to learn NDK, targets API 16 , intending to support API 8 and above.</li> <li>My project is at path <code>~/Desktop/PROJECT/ANDROID/WORKSPACE/NDKResearch</code>.</li> <li>My NDK path is <code>~/Documents/ANDROID/android_ndk_r8a</code></li> </ol> <p>I don't know how path information helps. But I always had problems giving correct path in bash. So just posting it here.</p> <h2>What I have done?</h2> <p>In my NDKResearch project I added an <code>Android.mk</code> file (path : <code>$MY_PROJECT_PATH/jni/Android.mk</code>)</p> <pre><code>include $(CLEAR_VARS) LOCAL_PATH:= $(call my-dir) LOCAL_CPP_FEATURES += -fno-exceptions LOCAL_SRC_FILES := \ Log.c \ Calculate.c LOCAL_MODULE := libSoundTouch include $(BUILD_SHARED_LIBRARY) </code></pre> <p>Added an <code>Application.mk</code> file in <code>$MY_PROJECT_PATH/jni/Application.mk</code>.</p> <pre><code>APP_PLATFORM := android-16 APP_STL := gnustl_static APP_CPPFLAGS := -frtti -fexceptions APP_PROJECT_PATH := /Users/myusername/Desktop/PROJECTS/ANDROID/WORKSPACE/NDKResearch </code></pre> <p>And then I executed <code>ndk-build</code> in bash shell</p> <pre><code>## cd ~/Desktop/PROJECT/ANDROID/WORKSPACE/NDKResearch ## ~/Documents/ANDROID/android_ndk_r8a/ndk-build </code></pre> <p>only to get the error mentioned in title. </p> <h2>What my question is?</h2> <p>From the above linked threads, <a href="https://stackoverflow.com/questions/6494567/android-ndk-your-app-build-script-points-to-an-unknown-file/6870967#6870967">user sege's answer</a> did work for me. None of the others did. But documentation for ndk clearly states not to use this method. From Overview.html file shipped with ndk (could not find an online version).</p> <blockquote> <p>There are two ways to use an Application.mk:</p> <ul> <li><p>Place it under $PROJECT/jni/Application.mk, and it will be picked up automatically by the 'ndk-build' script (more on this later)</p></li> <li><p>Place it under $NDK/apps//Application.mk, where $NDK points to your NDK installation path. After that, launch "make APP=" from the NDK directory.</p> <p>This was the way this file was used before Android NDK r4. It is still supported for compatibility reasons, but we strongly encourage you to use the first method instead, since it is much simpler and doesn't need modifying / changing directories of the NDK installation tree.</p></li> </ul> </blockquote> <p>So my question is, Has anybody had success with the first method? Any reason why it is not working? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USKrishnabhadra
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. USTamás Szincsák
      1. VTFavorite
    1. CODo you get the problem even if you remove APP_PROJECT_PATH := /Users/myusername/Desktop/PROJECTS/ANDROID/WORKSPACE/NDKResearch from Application.mk?
      singulars
      1. POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. USRyan Maloney
    2. CO@RyanMaloney yes..
      singulars
      1. POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. USKrishnabhadra
    3. COOne thing I notice is that you are using gnustl for RTTI and exceptions but your source files end in .c which, to my knowledge, results in compilation from gcc instead of g++. I don't know if this would result in the error message you are getting but it may be worth either naming the source files to a recognized cpp extension (although there is an issue with 8, see here LOCAL_CPP_EXTENSION) or add LOCAL_CPP_EXTENSION := .c
      singulars
      1. POAndroid NDK: Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk
      1. USRyan Maloney
 

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