Building android_core [closed]

asked 2012-06-11 15:20:23 -0500

ruifei0713 gravatar image

updated 2012-06-11 15:21:20 -0500

Hello from ruifei0713,

I am using the following website to install and build android_core: http://docs.rosjava.googlecode.com/hg/android_core/html/building.html

I have done everything beforehand including installing and building rosjava_core.

I am on the line ./gradlew debug.

When I run ./gradlew debug, I get an error that reads:

Execution failed for task ':android_acm_serial_updateProject'.

A problem occurred starting command 'android'

However, I do not have a problem running the command "android" (which opens the Android SDK Manager) and it is in my working PATH as defined in my ./bashrc file. This is my export command putting android in the PATH:

export PATH=${PATH}:/home/ruifei0713/Documents/android-sdk-linux/tools:/home/ruifei0713/Documents/android-sdk-linux/platform-tools

When I run ./gradlew debug --stacktrace, there is a line that reads:

Caused by: java.io.IOException: Cannot run program "android" (in directory "/home/ruifei0713/my_workspace/android_core/android_acm_serial"): java.io.IOexception: error=2, No such file or directory

I'm not quite sure if this line is significant, but I guessed that gradlew was looking for the android executable in the wrong directory (i.e. "/home/ruifei0713/my_workspace/android_core/android_acm_serial"). However, that wasn't the case because I put a symlink in that directory and the same error appeared.

Is there any other solution to this problem or something that I'm missing?

Thanks so much!

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tfoote
close date 2015-03-03 01:53:11.710336

Comments

This seems very strange. If 'android' is in your path and you're able to execute it from your shell, this should not happen.

Have you resolved this issue?

damonkohler gravatar imagedamonkohler ( 2012-07-02 23:18:52 -0500 )edit

Can you actually open the SDK manager? If not this sort of behavior is often caused by the lack of 32-bit compatibility libraries on a 64-bit system.

tpratkanis_wg gravatar imagetpratkanis_wg ( 2012-08-21 08:33:02 -0500 )edit