dulshi989

I am doing a project where we have to use the Android Terminal Emulator. I downloaded the the Jackpal Android Terminal Emulator from github and using the instructions in the document to build the terminal emulator.

https://github.com/jackpal/Android-Terminal-Emulator/blob/master/docs/Building.txt

I am having trouble installing the package in the first step itself, i.e. building the ndk shared libraries.

According to the instructions provided:

Build the shared library:

cd <the-android-terminal-emulator-directory>
<path-to-the-android-ndk>/ndk-build


Accordingly, I typed the following in my cmd

C:\>cd androidterm
C:\androidterm>android-ndk-r6b/ndk-build

I got the following error message:
'android-ndk-r6b' is not recognized as an internal or external command,
operable program or batch file.

I am still learning Android and have never worked with the command line before. Could someone please help me? Is it a problem with the way I have typed the command?

Please help. I am really confused.

jiminaus

Those instructions assume your using a Unix-like environment. In a Unix-like environment, forward slashes (/) are used to separate the names in a path; eg android-ndk-r5/ndk-build. On Window, back blashes (\) are used instead; eg. android-ndk-r5\ndk-build.

The path android-ndk-r5\ndk-build was just an example in those instructions. You need to put the actual path to the NDK.

Have you downloaded the NDK, in additional to the SDK? If not, head to Android NDK | Android Developers, download the .zip file, and extract it somewhere.

Let's say your have revision 6b of the NDK extracted to C:\android-ndk-r6b. Then for you the steps to buiding the shared library would be:

C:\> cd \androidterm
C:\androidterm> \android-ndk-r6b\ndk-build

Last edited by jiminaus; November 2nd, 2011 at 03:20 AM. Reason: Removed the reference to the .dll, it would of course still be an .so even on Windows.

dulshi989

Thank you, I did this too but it still gives the same error message:

C:\>cd \androidterm

C:\androidterm> C:\android-ndk-r6b\ndk-build
'C:\android-ndk-r6b\ndk-build' is not recognized as an internal or external comm
and,
operable program or batch file.

Any help would be greatly appreciated!

jiminaus

What is the output of these two commands?

C:\> dir C:\ /w
C:\> dir C:\android-ndk-r6b /w

dulshi989

Here it is..

C:\>dir C:\ /w
Volume in drive C has no label.
Volume Serial Number is BA10-BF0A

Directory of C:\

[.android] [android-ndk-r6b] [android-sdk-windows]
[androidterm] [BigFishGamesCache] [dell]
[Intel] [NST] [PerfLogs]
[Program Files] [Program Files (x86)] [Users]
[Windows] [xampp]
0 File(s) 0 bytes
14 Dir(s) 63,532,199,936 bytes free


C:\>dir C:\android-ndk-r6b/w
Volume in drive C has no label.
Volume Serial Number is BA10-BF0A

Directory of C:\android-ndk-r6b

[.] [..] [build]
[docs] documentation.html GNUmakefile
ndk-build ndk-gdb ndk-stack.exe
[platforms] README.TXT RELEASE.TXT
[samples] [sources] [tests]
[toolchains]
7 File(s) 197,342 bytes
9 Dir(s) 63,532,208,128 bytes free

Last edited by dulshi989; November 3rd, 2011 at 08:48 PM.

jiminaus

Huh?! Why's there no extension on ndk-build in C:\android-ndk-r6b?!

jiminaus

Damn, I'm glad I don't use Windows.

So despite having a Windows .zip download, the NDK has not really been ported to Windows.

ndk-build is Bash script. Hence the lack of an extension and the inability for cmd.exe to run it.

You need to download and install the latest version of Cygwin. This is will give you the Unix environment you need to be able to use the NDK under Windows.

After you've done that you should have a something like a Cygwin shell icon on the desktop or in your start menu. When you run that, you'll get a text shell window kinda like the command prompt, except you'll be inside a bash shell where you can issue unix command. (Yes, I'm talking very loosely here.)

Once you're in a bash shell, try these commands.

Last edited by jiminaus; November 4th, 2011 at 01:54 AM.

dulshi989

Thank you so very much for your help and effort!

Errgh! Windows is such a mess:s! I feel like switching straight to Linux.

So just one more question: what would be the best Linux O/S for a developer?

jiminaus

Mac OS X.

If you're new to Linux, you'll probably get up and running the quickest with Ubuntu.