similar to: (android) Re: Vorbis(ogg) and andorid

Hi, I created a extension in Asterisk, the extension has been configured in Android softphone 3cx. When I tried to call from Andorid phone to some other IP extension which is registered in Asterisk, I am not able to hear the voice, when I check the asterisk log or wireshark there is only one way RTP traffic, from Android I am connecting to Asterisk via 2G GSM network. Any idea would be

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

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

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:

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

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

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,

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

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

Evgeniy, thanks for your help. > 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. Do you have the sha1 hashes for any of those patches? I might be able to track down a build that includes them. > Was there any useful output in adb logcat when your program

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

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

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 applying this

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

Hi, I was wondering if anyone here had thought about FLAC support on the Android. It would be great for FLAC adoption. There's a bug open for it<http://code.google.com/p/android/issues/detail?id=1461>on which I've posted some details about how I think it would need to be implemented. It appears to me that it would need to be added to the OpenCore component, which is written in C.

> 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