| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
We don't need to be archiving these build artifacts in their extracted
form on the build server. Build and install to $TMPDIR, but still
package that tarball into $PACKAGE_DIR.
Change-Id: Iba42c19e0f7b49f2da608b577579fcc8871eb85c
|
|
|
|
|
|
|
| |
This used to be handled by package-release.sh, but we now need to
perform the full build/package step here rather than in ndk/.
Change-Id: Ia8a1662fd5c6adec72f83d15374af6f4bfa04afd
|
|
|
|
| |
Change-Id: Iff7e294f5bf08048d019f39465d377cfb9782866
|
|
|
|
|
|
|
| |
This is unused and we already get this from libgcc.
Change-Id: I1b1a405662294a3395928bc42e395271f758c40a
(cherry picked from commit c622d534cf0921bd22c4afe5060520f8fdd49d08)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently we've been packing an empty tarball of the toolchain since
I split up the toolchain build because the script defines the install
path in a few different places.
Fix the toolchain install path to match the format we expect
(toolchains/$HOST/$TOOLCHAIN/prebuilt), improve logging, and actually
fail the build if we can't package the toolchain.
Change-Id: I093ca747af13b5ed093cb43499ea1fdb9aed0430
(cherry picked from commit dd4155a395690bbe0372cf9ec63dd2ed85e7b81c)
|
|
|
|
|
|
|
|
|
|
| |
We're building against an old version of libc to check this already,
and the script doesn't seem to be checking the right things anyway (we
don't support older than 2.11). To top it all off, we haven't been
checking this for failure anyway.
Change-Id: I67e6b03cf7c3cce66cfb4c69dd18d8b9a6f31806
(cherry picked from commit 13185e44b81bb04268394f30efa7b0649c43e8ce)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using the build scripts from prebuilts/ndk makes the edit/compile
cycle complicated since we have to either edit in ndk/ and copy to
prebuilts/ or vice versa.
The prebuilt NDK build scripts should really just be whatever build
scripts we end up shipping with the modular NDK (i.e. anything that
supports ndk-build or the tests rather than things used to build the
NDK itself).
Change-Id: Id995397d6272f1539037a19287cc8a69fdb4b8a1
(cherry picked from commit 79ee432e58c7b1a4ae92aa2886ecd96173acbdf6)
|
|
|
|
|
|
|
|
|
|
|
|
| |
We should be doing this for the others, but there are still some build
issues to work out.
Note that this change was made to ndk/, but that was done after I had
copied build-gcc.sh here and I mistakenly forgot to apply it here as
well.
Change-Id: I2289c9d4da41eee8ce1d75324ccabf30adb7bd01
(cherry picked from commit da6ed85636572e47535ffd4fe6ab4790921c6508)
|
|
|
|
|
|
|
|
|
| |
We don't seem to need this. It was only used when configuring gcc, and
that isn't necessary. This is probably here as a relic from when we
used to build the gdb stub in this file.
Change-Id: Ieaa2f3c0200b9f569842caec2157f98d3e1a9c64
(cherry picked from commit 7ab70b0aa76254c36bdbf071e2463409115ab875)
|
|
|
|
|
|
|
|
| |
We have an out directory. Install GCC there rather than to $NDK (by
any of its many names).
Change-Id: I772ffc9230d3b1123a3cc25ebd9adc01e354c17f
(cherry picked from commit 7f738ff0092916749c3cde03c9403e3467eb0d13)
|
|
First, the platform toolchains building with the NDK build scripts
was odd.
Second, this moves us toward a more modular NDK. The path forward is
building GCC separately, installing it to prebuilts/ndk, and then
using it directly from there when building other NDK components.
Bug: http://b/23362228
Change-Id: I21448e470b4c3353bd49a1fec7d187a8376f3d82
(cherry picked from commit 51f25cab1eccd079214b9e08f5fe1bbe9368e1b0)
|