- 07 Nov, 2015 1 commit
-
-
Dan Albert authored
Change-Id: I34e566b0095ee4c0f574b03d6dd1eb3f9dd77ee9
-
- 05 Nov, 2015 6 commits
-
-
Dan Albert authored
-
Dan Albert authored
The prebuilt/ directory no longer contains the linux-x86_64 (or whatever) directory, so we can't use that to detect our host OS. Also need to fix up all the paths. Change-Id: Ie880fdd52d15ea76a19ecee4132b1744350d2b78
-
Dan Albert authored
-
Dan Albert authored
This is the conglomeration of all the common host tools. The way things are organized right now, these are essentially all required. Some of these things can be broken out. Android Studio users don't need GDB, Make, or Awk. Change-Id: I35f7a3bdb7eab4b9069f99b30a522062ada55342
-
Dan Albert authored
-
Dan Albert authored
This is done by the Python build now. Change-Id: I777fb26b1ead18cf16b5545bbae5385fca7cce9f
-
- 04 Nov, 2015 4 commits
-
-
Dan Albert authored
-
Dan Albert authored
-
Dan Albert authored
I had forgotten to upload my local change when I submitted https://android-review.googlesource.com/#/c/180344/ Change-Id: I0dc47ecf071595d2d478be0a6f534d4e9aca9e48
-
Dan Albert authored
-
- 03 Nov, 2015 2 commits
-
-
Dan Albert authored
Previous issue was that I had forgotten to upload https://android-review.googlesource.com/#/c/180253/ This reverts commit 6a3516c0. Change-Id: I7734954c84f7eb4343a5e74984c419717eb53fa6
-
Dan Albert authored
This doesn't cover any packages that are built from toolchain or that are installed to prebuilt/$HOST_TAG. The former will be fixed in another patch soon, but the latter is going to take some reorganization because several packages install to the same directory (and the repo.prop files will clobber each other). We need to also add the repo.prop files to each STL's .gitignore because the STLs are still building into their source directory ಠ_ಠ Bug: http://b/25417748 Change-Id: I4a666efecde192a5674e4c8b8ad835ceef80dd09
-
- 02 Nov, 2015 6 commits
-
-
Dan Albert authored
-
Dan Albert authored
When building for Windows the gcclibs module would fail because libatomic isn't built for the Windows toolchain (no idea why). Since this is purely a target module the host system is unimportant. Just use the Linux prebuilt. Change-Id: I34a368489c860c9299cab88133c9ebcfc2d8b389
-
Glenn Kasten authored
-
Dan Albert authored
-
Dan Albert authored
-
Dan Albert authored
-
- 30 Oct, 2015 1 commit
-
-
Glenn Kasten authored
Change-Id: I1fe364bdc94bddf83e4b0aa01bfdfa61ac71e00b
-
- 29 Oct, 2015 3 commits
-
-
Dan Albert authored
Android L and later uses libc++ in platform libraries, and there will be ODR issues when using libc++ in the NDK on those platforms. One destructive way this manifests is that the standard streams, which are initialized by a static constructor, get initialized twice (first by netd, then by the app), resulting in the app failing to load. This was resulting in 364 test failures when running on AOSP ToT volantis (54 remaining afterward). Change-Id: Ic2af5a570bb0b6677708801fb1aed6cc6f4f15e4
-
Dan Albert authored
Part of this patch is copying in the libc++ test runner from r244462. It includes all the work we've done upstream to make testing cross compiled targets much simpler. The one thing it drops is the use of `-include nasty_macros.h`, which is just used to make sure we don't have awful things like _A in our namespace (those are the names used by some C libraries for the ctype classes). It then adds all the Android specific testing functionality (libcxx.android) that is used in the platform. Some day the platform is actually going to be the upstream for this, but we're going to suffer through the copy for now (no modifications were needed). Finally, it adds the NDK specific testing code (libcxx.ndk). This is thankfully a pretty thin wrapper around the upstream libc++ test config (albeit with a lot of it disabled/skipped) and the Android platform test format. Exception handling doesn't work for ARM because libgcc is getting used instead of the ARM EHABI unwind library (deja vu). We don't seem to actually build a separate static library for the ARM unwinder, so we'll need to fix that separately. This doesn't link the correct versions of libatomic/libgcc. We're never linking thumb, and we're always using arm5. Current results (run on ~ToT AOSP volantis): Expected Passes : 4322 Unsupported Tests : 5 Unexpected Failures: 418 A lot of those failures are from ODR issues in iostreams (both netd and the test were trying to run the static constructors for the same object). This is a separate problem we'll have to solve. That's about all the diagnosis I've done so far. I'll look closer once this is in shape and submitted and the noise from ODR has died down. Bug: http://b/25329002 Change-Id: Ie9858120ac5aa3c872e5cc964e9792df9b3fc8fa
-
Dan Albert authored
Change-Id: I79e10b0a6877572a9fdb8e52d4f81253c0cc0249
-
- 28 Oct, 2015 1 commit
-
-
Dan Albert authored
* changes: Fix libc++ support lib for standalone toolchains. Drop GCC version from the gnustl include path. Fix toolchain locations. Make a bad error message more useful. Add a shebang to make-standalone-toolchain.sh. Add a test for make-standalone-toolchain.sh. Add a new build test type: test.py.
-
- 27 Oct, 2015 9 commits
-
-
Dan Albert authored
-
Dan Albert authored
These aren't really related to the toolchains themselves, they're information for ndk-build about how to use them. In a modular NDK, they only need to be available if ndk-build is used, so they should come with the build system. Bug: http://b/25231709 Change-Id: I92eb71f263941dee82fe6728f25a1463adbd991c
-
Dan Albert authored
libc++ always uses libc++abi, never gabi++. Change-Id: I8762ffbe0fecc171391571fe609fef0e738ed688
-
Dan Albert authored
We no longer keep these under 4.9 because we only ever have the one version now. Bug: http://b/24950607 Change-Id: I19991a97d9ac8ef8ea62cadc70d4d26878913194
-
Dan Albert authored
The host tag directory was moved to be the top level within toolchains/ some time ago, but this wasn't updated (or wasn't updated correctly). Change-Id: I35b086e6851626c40fc651528c552dfca5297d42
-
Dan Albert authored
The toolchain name wasn't invalid, make-standalone-toolchain.sh, you were looking in the wrong spot. Change-Id: Ie38e804b023294c38e99bd6ff0cae8dfafddc5a4
-
Dan Albert authored
The shell is happy to execute this directly without it, but Python isn't. Change-Id: Ib651f7491303aae0f0289b223290ca56081c876c
-
Dan Albert authored
Bug: http://b/25282754 Change-Id: I769322301a45f5451c8b610bff3bf5c62a748a1d
-
Dan Albert authored
We want to be able to run the build tests on Windows without requiring cygwin (or similar). Since we already have Python available, we can just rewrite the build.sh tests in that. This new test type makes that possible. Bug: http://b/25293074 Change-Id: I4649a79c51a44708dfefaeb2aa05e303031e80ca
-
- 26 Oct, 2015 7 commits
-
-
Dan Albert authored
-
Dan Albert authored
Bug: http://b/23362228 Change-Id: I309fdf38f2fa2107c0c07be62621b6e3fc515c50
-
Dan Albert authored
-
Dan Albert authored
This is just a temporary solution so we can run the tests. We'll want to find a cleaner solution for when we actually go to ship (as described in the bug). Bug: http://b/25231709 Change-Id: Iede46ac2c3f7bd6dfbe376d1e7bb303b5a6bdc22
-
Dan Albert authored
-
Dan Albert authored
Bug: http://b/23362228 Change-Id: Ifc36687ffa5509c97f775456a94ffaa580f7cdab
-
Dan Albert authored
-