Re: NDK_PROJECT_PATH

[RichardC]

Is your jni folder directly under your project root:

your_android_project\

    asset

    jni

    res

    src

?

On Wednesday, April 10, 2013 5:27:18 PM UTC+1, Stefano Bodini wrote:

Hi .. I spent quite some time looking around but I didn't find anything about, I hope to be in-topic here.

I usually work with Eclipse (Version: 4.2.2 Build id: M20130204-1200) under Linux (Ubuntu 10.04 LTS), so I integrated the NDK compilation in it and so far it worked perfectly.

After some recent update to Eclipse and SDK, when I create a new project, the call to ndk-build fails because the variable NDK_PROJECT_PATH is empty.

I have to deduct that something is wrong in Eclipse now and is not setting up this system variable.

I can workaround it forcing it in the ndk-build line.
So basically, if before my assignment for NDK in Eclipse CDT plugin  was :

${ANDROID_NDK}/ndk-build -B

now I have to set up :

${ANDROID_NDK}/ndk-build NDK_PROJECT_PATH=/my_product_path -B

When and how Eclipse is supposed to set up such variable ?

And I don't know if it is a related problem, but Eclipse is unable to look for updates now.

Thanks for any suggestion !

C'ya

  STeve

 

[David Turner]

I don't think that the Eclipse plugin sets up NDK_PROJECT_PATH, instead it probably tries to change the "current directory" to your project's top-level before invoking ndk-build.

I can only assume that Eclipse is using the wrong current directory. Adding an explicit NDK_PROJECT_PATH allows you to build your project succesfully, but may explain why other things are failing with the plugin. I don't really have a solution though.

On Wed, Apr 10, 2013 at 6:27 PM, Stefano Bodini <steve...@gmail.com> wrote:

Hi .. I spent quite some time looking around but I didn't find anything about, I hope to be in-topic here.

I usually work with Eclipse (Version: 4.2.2 Build id: M20130204-1200) under Linux (Ubuntu 10.04 LTS), so I integrated the NDK compilation in it and so far it worked perfectly.

After some recent update to Eclipse and SDK, when I create a new project, the call to ndk-build fails because the variable NDK_PROJECT_PATH is empty.

I have to deduct that something is wrong in Eclipse now and is not setting up this system variable.

I can workaround it forcing it in the ndk-build line.
So basically, if before my assignment for NDK in Eclipse CDT plugin  was :

${ANDROID_NDK}/ndk-build -B

now I have to set up :

${ANDROID_NDK}/ndk-build NDK_PROJECT_PATH=/my_product_path -B

When and how Eclipse is supposed to set up such variable ?

And I don't know if it is a related problem, but Eclipse is unable to look for updates now.

Thanks for any suggestion !

C'ya

  STeve

 

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ndk...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-ndk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Stefano Bodini]

Hi Richard

Yes of course.

Consider that "at least" is more than one year I use that system.

It is after a routinely update to SDK and plugins that I started to experience the problem.

Thanks

  Steve

[Stefano Bodini]

Thanks

I was just wondering if somebody else experienced this problem and eventually if someone had an idea about the process performed by Eclipse to assign system variables or at least the project path.

Something happened, I don't know just what :)
Probably I'll try to remove and re-install everything .. not exactly an activity I like to do :)

Steve