GitLab

This fixes the Cygwin installation check within ndk-build to
handle install paths containing spaces.

Note that the script itself doesn't check for spaces in the
path, but this is done later in the GNU Makefile itself.

Change-Id: Icfe2aaab2fac1a5621d4e649dad62436c768c579

Change-Id: Idd50aeaf20f7992ffd9ca208eefd4ed92dd1a198

Change-Id: I695ea8e09e55a48ddb23f35cd26c91e96966cb6a

It looks like that many NDK developers on Windows have some sort of other GNU
Make program installed in their path (e.g. because they installed another IDE
or Developer Environment), and that conflicts badly with our build scripts.

Also fix a tiny bug where the debuggable flag was lost when building
the modules.

Change-Id: I2d26131b08cf19959122abdefec9a22955d2a89c

This is a helper script used to launch a native debugging session.
To use it, follow these steps:

1. Make your application debuggable
2. Build the machine code with 'ndk-build'  (make APP=<name> is not supported)
3. Build the package with ant or the ADT Eclipse plugin
4. Install it on your device/emulator
5. Launch it
6. Run 'ndk-gdb' from your application project directory.

Change-Id: Ie3b0557e70cefa0080075a34ad0ca46bebef3c42
NOTE: To work properly, a modified gdbserver binary must be used
      (one that binds to Unix sockets instead of TCP ones). Patch
      upcoming.

There is no need to modify $NDK/apps anymore to build an application.

Now all you need to do is launch $NDK/ndk-build from the project path,
or any of its sub-directory, and the build scripts will handle everything
automatically.

You can also place an optional Application.mk under $PROJECT/jni, but
by default the NDK will build all modules listed in your Android.mk for
the 'armeabi' ABI.

+ Update the documentation

Change-Id: I235c4051d7f00f37d50e6b4bb0e796c0bdaa001d

Change-Id: I9b1d6f39fd33f5b7cbc2e875a292f5901780ce26