search for: ndk

...;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 > plan to align release between NDK and the one in Chromium. > You can rebuild it from source. Assuming $AOSP points to your android > tree. > > export NDK=$AOSP/ndk > cd $NDK > ./build/tools/download-toolchain-sources.sh /tmp/ndk-$USER/src > ./build/t...

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...

...thread.php?t=2394035 Cheers. ------------------------------ *Android ARM(32-bit) clang-kernel bring-up for Nexus 5(hammerhead)* *[Android Version Information] **&** [Battery Usage of a clang-built kernel ~ better than that of gcc-built kernel (shows one of the instances)]* *[1] Android NDK r13b [LLVM/clang + binutils(as, ld, etc)] [2] Android NDK r17 [LLVM/clang + binutils(as, ld, etc)]* *[3]** Main LLVM/clang + Android NDK r13b binutils(as, ld, etc) **[4]* * Main LLVM/clang + Android NDK r17 binutils(as, ld, etc)* *[5]** Snapdragon Qualcomm LLVM/clang + NDK r13b binutils(as, etc)...

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 taken over the NDK a year ago, and as you...

...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 one thing, but modifying source code is another. Jeff arm-linux-androideabi-g++ --sysroot=/opt/android-ndk-r8e//platforms/android-14/arch-arm -I/opt/android-ndk-r8e//sources/cxx-stl/stlport/stlport/ -Ibuild/include -O2 -D_REENTRANT -Wno-long-long -fpermissive -W -Wall -c checks/bench.cpp -o build/checks/bench.o checks/bench.cpp: In function 'void (anonymous namespace)::report_results(const string&am...

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...

...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 from the android ndk. If I do that, compilation fails with the error message at the end of this mail. 1. Do I habe to use llvm shipped with the android ndk, or does it not matter and I can use llvm from ubuntu? 2. The error message means, that the haskell calling convention is not supported, correct? Is there some goo...

...ndroid 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 version is kept up-to-date. It would be interesting to compare clang and GCC latest releases instead... that's where the future lies :p ------- Jean-Michaël Celerier http://www.jcelerier.name -------------- next part -------------- An HTML a...

...faust 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 cross-compiling LLVM for Android on my Windows Dev machine. Wondering if anyone has any advice for me? I've been trying to use the android-ndk cmake & toolchains to build LLVM so that I can cross-compile Faust against the Android LLVM build. I've managed to get Android's cmake to generate an Android Gradle Ninja project, but when I try to build it I get lots of errors that seem to indicate that the Ninja project is invalid, s...

...xec] StaticLibrary : lib0.a [exec] StaticLibrary : lib1.a [exec] StaticLibrary : lib0.a [exec] StaticLibrary : lib1.a [exec] SharedLibrary : libdmt_opus.so [exec] SharedLibrary : libdmt_opus.so [exec] SharedLibrary : libdmt_opus.so [exec] C:/android/android-ndk-r8e/toolchains/arm-linux-androideabi-4.6/preb uilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-andr oideabi/bin/ld.exe: ./obj/local/armeabi/lib0.a(analysis.o): in function run_anal ysis:jni/src/libopus/src/analysis.c:636: error: undefined reference to 'optimize _frame...

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 ru...

Hi flac-dev, When we try to build libFLAC v1.3.1 using the Android NDK, we currently are getting an error in a couple files: ../../third_party/flac/src/libFLAC/md5.c:498:25: error: use of undeclared > identifier 'SIZE_MAX' > if ((size_t)channels > SIZE_MAX / (size_t)bytes_per_sample) > I filed a bug for it on the sourceforge bug tracker: https://...

I'm fairly sure the problem is that we still support building with gcc 4.8.x, and that version of gcc did not have std::to_string. It is not just an NDK issue. -Hal On 05/17/2017 06:05 AM, Pavel Labath via llvm-dev wrote: > Hi Diana, > > I am responsible for that bot, and probably a great number of those fixups. > > The root of the problem is that android NDK comes with a libstdc++ > which does not have std::to_string. I forg...

Hi. As a follow-up on [1], I'd like to raise the question of whether it's practically possible to compile R to the Google Android mobile platform? The best way would probably be to use the Native Developer Kit [2], NDK, and in that way get a library. This could then be interfaced to by a Java-program. I know that several questions have been raised against the idea, e.g. with the input methods and all that, but I wouldn't be that hard to make an alternative input method or even a new language that could be co...

...oduleID = 'my cool jit' define double @test(double %x) { entry: %multmp = fmul double %x, 4.200000e+01 ; <double> [#uses=1] ret double %multmp } " and the use llvm-ar to compile that test.ll to a test.bc and then compile that to a .S which I can pass to the Android NDK to compile. I've tried (to cut a long day short!) Compiling llvm with the "--target=arm-eabi" and "--target=arm-elf-linux-gnu" options. Calling llc with -march=thumb and -march=arm (I'm trying to create a asm file for the android NDK gcc) I'm able to get the NDK to...

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 prese...

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 25, 2013 at 3:57 PM, James Lyon <jameslyon0 at gmail.com> wrote: > Hmmm.... following up on your point I've noticed something strange....

Hello, I am encountering a strange assertion failure using the LLVM libraries cross-compiled for Android using the Android NDK. I am using the official release of LLVM-2.9. The IR which is causing the assertion failure is the following: define void @__construct_Byte__Integer(i8* nocapture %byteLValue, i32 %integerRValue) inlinehint { entry: %0 = trunc i32 %integerRValue to i8 store i8 %0, i8* %byteLValue ret void...

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-androi...

Hi all, I can't get CELT to compile with the latest version of the Android NDK. It seems that the compiler (GNU) is rejecting any variable that starts with an underscore and then a capital letter (e.g. "_C"). I know that according to the C++ standard these are "Reserved Names" and must not be used in user code, but the Android compiler seems to be appl...