Building serval mesh error

[ABDEL WAHID SABRE OUSMAN]

Hi

After i run "ant debug" the following errors occur again

root@bensabrefils-Lenovo-G570:~/src/batphone# ant debug

Buildfile: /home/bensabrefils/src/batphone/build.xml

-set-mode-check:

-set-debug-files:

-check-env:

[checkenv] Android SDK Tools Revision 22.0.0

[checkenv] Installed at /home/bensabrefils/android-sdk-linux

-setup:

[echo] Project Name: batphone

[gettype] Project Type: Application

-set-debug-mode:

-debug-obfuscation-check:

version:

[echo] Version Name: 0.90.1

[echo] Version Code: 1951

ndk-build:

BUILD FAILED

/home/bensabrefils/src/batphone/build.xml:179: Execute failed: java.io.IOException: Cannot run program "/home/bensabrefils/android-android-ndk-r8d/ndk-build": java.io.IOException: error=2, No such file or directory

at java.lang.ProcessBuilder.start(ProcessBuilder.java:488)

at java.lang.Runtime.exec(Runtime.java:610)

at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:862)

at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:481)

at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:495)

at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:631)

at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672)

at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498)

at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)

at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:616)

at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)

at org.apache.tools.ant.Task.perform(Task.java:348)

at org.apache.tools.ant.Target.execute(Target.java:390)

at org.apache.tools.ant.Target.performTasks(Target.java:411)

at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)

at org.apache.tools.ant.Project.executeTarget(Project.java:1368)

at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)

at org.apache.tools.ant.Project.executeTargets(Project.java:1251)

at org.apache.tools.ant.Main.runBuild(Main.java:809)

at org.apache.tools.ant.Main.startAnt(Main.java:217)

at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)

at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)

Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory

at java.lang.UNIXProcess.<init>(UNIXProcess.java:164)

at java.lang.ProcessImpl.start(ProcessImpl.java:81)

at java.lang.ProcessBuilder.start(ProcessBuilder.java:470)

... 23 more

Ben 

[Paul Gardner-Stephen]

Hello,

It can't find /home/bensabrefils/android-android-ndk-r8d/ndk-build to run it.

Is that where you have ndk-build and the ndk tools installed?

Paul.

--
You received this message because you are subscribed to the Google Groups "Serval Project Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.
To post to this group, send email to serval-proje...@googlegroups.com.
Visit this group at http://groups.google.com/group/serval-project-developers.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[ABDEL WAHID SABRE OUSMAN]

Yes i changed the environment, but still showing the same errors as follows:

Submodule 'jni/serval-dna' () registered for path 'jni/serval-dna'

Updated project.properties

Updated local.properties

build.xml: Found version-tag: custom. File will not be updated.

Updated file ./proguard-project.txt

$NDK_ROOT (/home/bensabrefils/android-ndk-r8d) is not a directory

And the following is where i set the environment:

export NDK_ROOT=/home/bensabrefils/android-ndk-r8d 

export SDK_ROOT=~/android-sdk-linux/tools

export ANDRIOD_SDK_ROOT=~/android-sdk-linux/platform-tools

export PATH=${PATH}:${ANDRIOD_SDK_ROOT}:${SDK_ROOT}:${NDK_ROOT}

# ~/.bashrc: executed by bash(1) for non-login shells.

# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)

# for examples

# If not running interactively, don't do anything

[ -z "$PS1" ] && return

# don't put duplicate lines or lines starting with space in the history.

# See bash(1) for more options

HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it

shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

HISTSIZE=1000

HISTFILESIZE=2000

# check the window size after each command and, if necessary,

# update the values of LINES and COLUMNS.

shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will

# match all files and zero or more directories and subdirectories.

#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)

[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)

if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then

    debian_chroot=$(cat /etc/debian_chroot)

fi

# set a fancy prompt (non-color, unless we know we "want" color)

case "$TERM" in

    xterm-color) color_prompt=yes;;

esac

# uncomment for a colored prompt, if the terminal has the capability; turned

# off by default to not distract the user: the focus in a terminal window

# should be on the output of commands, not on the prompt

#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then

    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then

# We have color support; assume it's compliant with Ecma-48

# (ISO/IEC-6429). (Lack of such support is extremely rare, and such

# a case would tend to support setf rather than setaf.)

color_prompt=yes

    else

color_prompt=

    fi

fi

if [ "$color_prompt" = yes ]; then

    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '

else

    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '

fi

unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir

case "$TERM" in

xterm*|rxvt*)

    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"

    ;;

*)

    ;;

esac

# enable color support of ls and also add handy aliases

if [ -x /usr/bin/dircolors ]; then

    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"

    alias ls='ls --color=auto'

    #alias dir='dir --color=auto'

    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'

    alias fgrep='fgrep --color=auto'

    alias egrep='egrep --color=auto'

fi

# some more ls aliases

alias ll='ls -alF'

alias la='ls -A'

alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:

#   sleep 10; alert

alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.

# You may want to put all your additions into a separate file like

# ~/.bash_aliases, instead of adding them here directly.

# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then

    . ~/.bash_aliases

fi

# enable programmable completion features (you don't need to enable

# this, if it's already enabled in /etc/bash.bashrc and /etc/profile

# sources /etc/bash.bashrc).

if [ -f /etc/bash_completion ] && ! shopt -oq posix; then

    . /etc/bash_completion

fi

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsub...@googlegroups.com.

[Paul Gardner-Stephen]

So where do you have the android ndk installed? 

Is it installed in /home/bensabrefils/android-ndk-r8d ?

from a shell run the following two commands:

ls -ld /home/bensabrefils/android-ndk-r8d 

and then

ls -l /home/bensabrefils/android-ndk-r8d 

and show us the output of those two commands.

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.