<div dir="ltr"><div>Hi Renato,</div><div><br></div>On Mon, Nov 11, 2013 at 9:35 PM, Renato Golin <span dir="ltr"><<a href="mailto:renato.golin@linaro.org" target="_blank">renato.golin@linaro.org</a>></span> wrote:<br>
<div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
Hi Folks,<div><br></div><div>I know you guys have buildbots and stuff, but I couldn't find a place where I could download the Android kernel zip, so I can flash a phone and boot to terminal. Or maybe that's asking too much for the moment... :D</div>
<div><br></div><div>Basically, what I need is a Clang-compiled Android kernel that I can at least boot on some (any) device. The idea being that, once we have that on one device, we'll be able to run other tests with it, and eventually adding other Clang-compiled Android pieces to it, incrementally.</div>
</div></blockquote><div><br></div><div>We have it for Nexus 7. The documentation is on this wiki <a href="http://llvm.linuxfoundation.org/index.php/Nexus_7">http://llvm.linuxfoundation.org/index.php/Nexus_7</a></div><div>
I don't know if this is the default procedure know but I have seen that AOSP is building the kernel OUTSIDE of Android build system and just adding the binary file to the build system. On the other hand CyanogenMod do exactly the opposite.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>I'd also want to incrementally add new devices, so that other people could test at home, or at their offices, CI systems, etc.</div>
<div><br></div><div>I'm asking you guys because:</div><div> 1. I don't have the expertise for building the Android kernel for specific devices</div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div> 2. You guys already have patches that make the kernel compile at all (right?)</div></div></blockquote><div><br></div><div>Yeap. Nexus 7.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div> 3. Checking out from a tree with the patches applied is ok, but would be good to know after which merge from AOSP, the tree is compiling, and I'm assuming the buildbots will tell you that.</div></div>
</blockquote><div><br></div><div>We have some "checkpoints" which we know that the builds are ok. We would need to build and see if the HEAD is working (following the Wiki documentation without the checkpoint step).</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Did I get it right? Or am I just making things up?</div>
</div></blockquote><div><br></div><div>You got it. But one thing that we would need to do is change Android build system to use Clang and get a patched kernel. I dunno if it would be good for AOSP inherit all LLVMLinux build system to handle the kernel.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Let me know,</div><div>--renato</div>
</div>
<br>_______________________________________________<br>
LLVMLinux mailing list<br>
<a href="mailto:LLVMLinux@lists.linuxfoundation.org">LLVMLinux@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux</a><br></blockquote></div><div class="gmail_extra"><br></div><br>Regards,</div>
<div class="gmail_extra">Tinti<br clear="all"><div><br></div>-- <br><div dir="ltr">Simplicity is the ultimate sophistication<br></div>
</div></div>