similar to: R on Google Android

cc +andrewhsieh +loganchien On Tue, Nov 13, 2012 at 11:21 PM, Joe Abbey <jabbey at arxan.com> wrote: > Hats off to the Android NDK team! > > Thanks for including me here, but I'd like to clarify that this is all from the really hard work of Andrew Hsieh and Logan Chien, and a few other Android engineers. (I'm actually not working on Android anymore, Andrew and Logan have

Hats off to the Android NDK team! http://developer.android.com/tools/sdk/ndk/index.html Important changes: * Added the Clang 3.1 compiler to the NDK. The GNU Compiler Collection (GCC) 4.6 is still the default, so you must explicitly enable the Clang compiler option as follows: * For ndk-build, export NDK_TOOLCHAIN_VERSION=clang3.1 or add this environment variable setting

According to https://developer.android.com/ndk/guides/abis.html#x86 Android always support SSE, so there's no need to test SSE OS support. Why both __ANDROID__ and ANDROID are tested: http://stackoverflow.com/questions/15328751/android-macro-suddenly-not-defined http://stackoverflow.com/questions/6374523/how-to-detect-compilation-by-android-ndk-in-a-c-c-file

This is only available for apps that target API level 19 and up. On 18 and lower, the futimens() function won't be available via libc.so. You will need to target API 19 (KitKat) in order to actually use it. If I do an "nm -D prebuilts/ndk/9/platforms/android-19/arch-arm/usr/lib/libc.so", I can see futimens() is present. On the others, it is definitely missing. Steve On Mon, Nov

You are citing the "Android platform workflow" section, which is about sanitizing components of the Android system itself. For NDK apps, see "Android NDK workflow" in the same document. You need -eng build because preloading libraries into dalvik vm is not allowed in user builds. JellyBean includes several bugfixes in the dynamic loader that asan needs. Was there any useful

Hmmm.... following up on your point I've noticed something strange. futimens is missing from the NDK (r9b; it's not in any headers and the libc.so files are the same all the way back to android-9), which is why I thought it's missing from Android generally. The NDK is by far the easiest way to cross-compile since it provides a standalone cross-compilation toolchain. It is however

Hello, I would like to share my successful bring-up of LLVM/clang-built Linux ARM(32-bit) hammerhead kernel for Android running on my Nexus 5 smartphone. After having successfully brought up LLVM/clang-built Linux kernel(since v4.15.7 to the most recent v4.17) on x86_64, I was interested in accomplishing the same on the ARM platform of my Nexus 5 - Android smartphone. So, here is the complete

> The main advantage of the clang-built Android ARM(32-bit) hammerhead kernel for my Nexus 5 has been the better battery usage when compared to that of gcc-built kernel, with the same kernel config and hardware(my Nexus 5 Android Smartphone). Details of the same can be found below. To be fair, the GCC version which comes with the android ndk has not been updated for four years, while the clang

Hey Guys, I'm working on a project in Android related to System-level Audio DSP Effects for Tuning Android Audio. I want to leverage Faust ( https://faust.grame.fr/) to allow users to program their own filters. Faust provides a libfaust implementation which includes a JIT Compiler which leverages LLVM and seems to be the best path for me to use. Unfortunately I'm having problems

I've compiled rsync for my rooted Android (armeabi-v7a, 32-bit) device using these instructions: ``` clone_or_update rsync master git://git.samba.org/rsync.git cd rsync ./prepare-source ./configure \ --prefix=$INSTALL_ROOT/rsync \ --host=$AUTOCONF_PLATFORM \ CFLAGS="$CFLAGS -static" make -j8 && make install cd - ``` Best place for instructions to build I could find

From: http://address-sanitizer.googlecode.com/svn-history/r1624/wiki/Android.wiki > AddressSanitizer is fully supported in AOSP starting with JellyBean release. To run > applications built with ASan you'll need an -eng build of Android. > > To build any part of Android system with ASan, add > LOCAL_ADDRESS_SANITIZER:=true to the appropriate Android.mk. I don't see that

Yes, llvm-config. Thanks for the pointer to the build script - that's what I was looking for. -Greg On Thu, Jan 31, 2013 at 5:24 PM, Andrew Hsieh <andrewhsieh at google.com>wrote: > You mean llvm-config? It was deleted after the build. You can modify our > build script build-llvm.sh to get it back. > Clang/llvm-3.2 will be available in the next NDK release. There is no

Hi all. I am experimenting with building OpenSSH server for Android. The attached patch makes OpenSSH successfully build (at least) using Android NDK with libldns. The patch is mostly trivial. The biggest change perhaps is disabling password authentication code. I would like to receive feedback and hopefully get it accepted into the mainline eventually. Regards, Dmitry -------------- next

I was digging around and saw a bunch of different people have created ways of building libopus for android (even I did one back in the CELT days). Is there an official one somewhere that I missed? I even notice this is the Google sources, but it seems to be a touch long in tooth at this point: https://android.googlesource.com/platform/external/libopus/+/android-wear-5.1.1_r1 I am happy to build

Hello, As I was missing an Android port of tinc (thanks for this great tool!), I built one by myself. It's simply a cross-compiled version of tinc daemon (with very few changes), and a (basic) GUI application for Android to deploy and manage it. Both my changes to original tinc and the GUI are available on GitHub: - https://github.com/Vilbrekin/tinc - https://github.com/Vilbrekin/tinc_gui

Hi Jack, I'm almost there with Android..... I've actually got the static and dynamic libraries built. I'm choking on the test suite. Do you want to take a shot at working around Android and [embedded, lame] STLport? I would try removing the call to rend() in std::map<_Key, _Tp, _Compare, _Alloc>::rend(). But I really should not modify program code. Fiddling with a Makefile is

Hi LLVM Android NDK developers, I was curious how clang was built for this release, but didn't find the llvm-setup executable in the NDK. Can you share how your build was configured here? And I see the Chromium build distributes a separate version of clang that looks to be somewhere beyond the 3.2 release. Has there been any talk of both Android and Chromium sharing the same clang? Or is

Hey, I am trying to build a haskell cross compiler to android by building the glasgow haskell compiler with target=arm-linux-androideabi. It builds, but the executables the compiler produces segfaults on my android device. This is probably not llvm related, but I want to rule that out. I used the llvm version shipped with ubuntu 12.10 for the build. I was wondering if maybe I have to use llvm

Hi, I've battled with this now for a good many hours, and I was wondering if someone could point in the right direction. What I want to do is with the kaleidoscope tutorial code, take the IR from a run where I've just done " def test(x) 42.0*x; " resulting in the file test.ll " ; ModuleID = 'my cool jit' define double @test(double %x) { entry: %multmp = fmul

Hi, We are trying to use clang as a drop-in replacement for the gcc come with Android NDK. I found that MC/ELF doesn't not handle Thumb functions properly, e.g., bit 0 of the function name in the .symtab is not set to 1, and some thumb instructions are not generated correctly, e.g., the addresses for tBL/tBLX are not calculated right. With that attached patch, we can compile and run some