Actually both armv7-a (vfpv3-d16 no neon, and softfp) and yes AArch64 (arm64-v8a).
armv7-a is working great for us on android with current stock Google NDK which is using clang-8... but we seem to be experiencing an ivar alignment or offset bug on arm64-v8a. We had to rework SmallObjectClasses assembly reference because android will not load any library that has any text relocations in a library. (I believe we can probably get around that by using the GOT to get to SmallObjectClassess but we have just removed for now). But ya, Ideally I want to run the test suite on an actual android device to figure out this ivar issue on AArch64. So, hmmmmmm, I guess I'll try and think of some way to get the test executable main()s onto an actual android device for testing... Jordan > On Jan 25, 2019, at 3:18 PM, David Chisnall <gnus...@theravensnest.org> wrote: > > On 25 Jan 2019, at 19:46, Jordan Schidlowsky <jor...@noodlecake.com> wrote: >> >> Is there an easy or recommended way to run the libobjc2 tests when cross >> compiling with cmake? > > Nothing trivial. There is something in ctest that can let you define a > remote environment, but I’ve never used it. > > That said, each one is a separate binary that exits with code 0, so just > copying them all to your target and running them with a 3-line shell script > should work. What’s the target? For AArch64, I did the builds and testing > in QEMU and, even on my laptop, it was fast enough (not something I’d like to > do regularly though!). > > David > _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep