GitLab

* changes:
  Revert "Do not rely on mipsel toolchain for mips32, use mips64el instead"
  Revert "Only make mips64el standalone toolchain for mips architectures"
  Revert "Specify toolchain library path when using clang for mips32"

This reverts commit 344a55ae.

Change-Id: I90f2091c8b4835a1224e9f7e34acf080299df681
Test: ./checkbuild.py

This reverts commit 8a204653.

Change-Id: I6d2b348330de39a5db9dc59c6f13edca63aeff27
Test: ./checkbuild.py

This reverts commit 6a47a9e5.

Change-Id: I5157911e84e01bfd65579b208dd7282db75e3340
Test: ./checkbuild.py

We don't support hard float any more, and we've now finally removed
enough of the hard float crap from the headers that this is
rightfully failing.

Change-Id: I878c6334e27a5daa9abe1cb39f0bf7a829f50bfb
Test: None
Bug: None
(cherry picked from commit d3ea8154)

Some part of the crypto libraries on Windows requires some
information from our environment in order to initialize. Copy the
existing environment and add our path to it.

Test: ./checkbuild.py
Bug: https://github.com/android-ndk/ndk/issues/178
Change-Id: Ic8ddd0f6d8e78a933d64a1a1a86f79d9ad84c9cb
(cherry picked from commit fa1fd3f3)

Tests look good, so time to ship beta 2.

Change-Id: I83ea6345ffe79dc9070791add7e2e9e44ef482c5
Test: ./checkbuild.py
Bug: http://b/30980049

Apparently bfd doesn't know `-no-pie`, so it instead was parsing this
as `-n -o -pie` and writing the output to ./-pie instead of where it
should have gone.

Change-Id: I085e3b8b2b9b6bd74d4ae17cea96ef60fb35c7a0
Test: tests/run-all.py --filter static-executable --abi arm64-v8a
Bug: None
(cherry picked from commit 47375fd3)

* changes:
  Print the full test configuration.
  Include the build ID in the device info.
  Detect emulators in the test runner.

Change-Id: I2402ce8e40e4917624573d4b308dc3a4f80fba8d
(cherry picked from commit d11aff85)

Change-Id: Iaf202e050b6cf4fcf07f92d194252ee533d84fd3
Test: tests/validate.py path/to/ndk
Bug: None
(cherry picked from commit 9ddaab42)

Change-Id: I97cbdc37a9976eb3da17a3fbbb3394dbae0d24f1
Test: tests/validate.py path/to/ndk
Bug: None
(cherry picked from commit f155edaf)

Change-Id: Ib71c532cf3c2a26ec6a397347d7acfcd479546ec
Test: tests/validate.py path/to/ndk
Bug: None
(cherry picked from commit 0fd53f25)

Grab the doc and the reporting script.

Test: ./checkbuild.py --module simpleperf && unzip -l simpleperf.zip
Bug: http://b/28911532
Change-Id: I88c1aafa80041281d9211dd51e595979c909a54a
(cherry picked from commit de6cc6fc)

Bug: http://b.android.com/218293
Bug: http://b.android.com/219399
Change-Id: I57d00a1891a3a0a1e1c12dcd534938182d6dcf44

Change-Id: I44250c9bab2b0d4625250950e9f1d94064099736
(cherry picked from commit 7b0636ce)

Test: pylint checkbuild.py
Bug: None
Change-Id: Ib463fc2f041594f7a412b891c523bdac6bc0c7d3
(cherry picked from commit d441f53c)

Test: ./checkbuild.py
Bug: http://b/21420007
Change-Id: I3db68d980ce4a510902f9bc3a9647e6422d70ec7
(cherry picked from commit d72f3abe)

Test: tests/run-all.py --abi armeabi-v7a --filter signal path/to/ndk
Bug: https://github.com/android-ndk/ndk/issues/160
Change-Id: Ic9fdda0e9c244be827c7a9039ca464a656be6081
(cherry picked from commit 9463b17f)

Test: ./checkbuild.py
Bug: http://b/28911532
Change-Id: I296fcfab2cbe203ead8cfb697b3a5a338e21df6a
(cherry picked from commit c65dcf03)

The documentation suggests that this is the correct value to set
these variables:
https://cmake.org/cmake/help/v3.6/manual/cmake-toolchains.7.html#cross-compiling

Bug: https://github.com/android-ndk/ndk/issues/172
Bug: http://b.android.com/214412
Change-Id: I3447b866b7ff9b00d636ffe330a27367b2076a5c

* Direct studio bugs toward the correct tracker.
* Put back the announcement about GCC being done.

Test: None
Bug: None
Change-Id: Iaee5690a7aad48f85b3b74a5d1c3fe0d373c4392
(cherry picked from commit fb83ea8b)

I'm not really sure if this ever worked before. There's some stuff in
build/core/build-all.mk that looks like it was supposed to handle
this, but it's all bogus:
https://android.googlesource.com/platform/ndk/+/master/build/core/build-all.mk#144

`EXECUTABLES` and friends are never defined, so that does nothing.

This is a pretty minimal fix. This leaves the empty obj and libs
directories. If I could go back in time I'd just make the clean target
blow these away, but I worry about changing that at this stage in
case people are actually keeping things in there...

Test: ndk-build && find libs && ndk-build clean V=1 && find libs
Bug: https://github.com/android-ndk/ndk/issues/80
Change-Id: I1747289439612da82b5a9611076341d3052b7e8e
(cherry picked from commit 3e4f2fbd)

Test: None
Bug: None
Change-Id: I686f013af507d781715c48c1cc2f6f6c0758b359
(cherry picked from commit 220c9c5e)