[LLVMdev] regarding compiling clang for different platform

Renato Golin renato.golin at linaro.org
Thu Jul 18 01:14:57 PDT 2013

On 18 July 2013 08:50, Tim Northover <t.p.northover at gmail.com> wrote:

> But then you'll hit the fun of trying to get Clang to find Android's
> headers and libraries

Some Linaro folks are also trying to build Android with Clang and they have
some wrappers to make clang work transparently (as a cross-compiler from
Intel to ARM). They all hangout on the LLVMLinux mailing list or IRC
channel (OFTC, #llvmlinux).

There are also ABI issues, since androideabi is not gnueabi which is not
aeabi and Clang/LLVM knows very little about the difference (but the Kernel
breaks because of enum sizes and other little things).

I never built it myself, but I know that it's not trivial because the
Android build system is something of a marvel of the modern world that has
GCC hard-coded all over the place. Using the Clang wrapper should work with
a standard Clang binary (if it has the ARM back-end), so the way you build
Clang shouldn't matter much.

Good luck!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130718/dd7ed084/attachment.html>

More information about the llvm-dev mailing list