Hello everyone,
I just wanted to share something I noticed today while building aosp master branch:
This commit enables clang for the whole build but when LOCAL_CLANG is set to somethinbg like 'false'.
To me, it is very nice, as I prefer clang over GCC, so what do you think ? Soon the raise of new custom clang projects ? The end of custom gcc based tc such SM or UberTC ?
@sparksco @Cl3Kener
Related
Hello, Im currently building CM 11 for hammerhead. Is there a way to build it using the Linaro toolchain instead of the normal one?
Thanks
Hello. After little researches I've successfully compiled 4.7.4 toolchain on 32-bit cpu, ubuntu 14.10. I compiled and preconfigured this toolchain for my phone/kernel..thought someone could find this useful, so..attaching 4.7.4 linaro toolchain..optimized for cortex-a8. Used latest sources from this thread as base.
Code:
- Target -> Linux Kernel 2.6.32.61
- Linaro GCC 4.7-2014.06 (4.7.4)
- Linaro Binutils 2.24.0-2014.09
- Linaro EGLibc 2.19-2014.08
- Linaro GDB 7.8-2014.09
- GMP 5.1.3
- MPFR 3.1.2
- PPL 0.11.2
- CLOOG 0.15.11
- MPC 1.0.2
- Soft float for Cortex-A8 cpu
- Multilib support for Cortex-A8 toolchains
- Compiled with -03 optimization level
- Possibility to use the alias arm-eabi- as prefix of each tool
- Misc preconfigurations...
CT_ARCH_ARCH="armv7-a"
CT_ARCH_CPU="cortex-a8"
CT_ARCH_TUNE="cortex-a8"
CT_ARCH_FPU=""(auto)
CT_ARCH_FLOAT="soft"
CT_CC_CORE_EXTRA_CONFIG_ARRAY="--with-float=soft"
CT_CC_EXTRA_CONFIG_ARRAY="--with-float=soft"
My device (SE x10) is OLD and doesnt boot with hardware float. It worked with softfp but since it's an emulation it worked so slow.. Decided to build this stuff with soft float and result is quite good. Up to 10% faster CPU operations.. This build is most probably for old, legacy or weak devices.
Get it here:
http://www.wuala.com/feravolt/misc/FeraLab_arm-cortex_a8-linux-gnueabi_Linaro_4.74_toolchain.zip/
Peace out.
Hey great work, ill definitely test this one out!
Great, but I sold my legendary X10. Hope the devs could bring this stuff to many other devices
how can i use this to my xperia live with walkman, toolchain? is it part of kernel?
moolokow said:
how can i use this to my xperia live with walkman, toolchain? is it part of kernel?
Click to expand...
Click to collapse
Hello, folks... Asking...if anybody has that zip from this link and could share it back with me..
http://www.wuala.com/feravolt/misc/FeraLab_arm-cortex_a8-linux-gnueabi_Linaro_4.74_toolchain.zip/
I lost my copy..(
Thanks in advance..
Hello guys, i've been searching this for sometime, but still can't find the answer. I'm quite new to Nexus 5, and i didn't know the history about how CAF branch was made beside aosp branch in hammerhead. The only think i know is, CAF commits was once merged by cm to aosp, but introduce many bugs. So it was divided into two branch like now. I like CAF build (the reality, i like experimental builds ) but i only found cm based roms for CAF build
TL;DR is it possible to build AOSP roms based on CAF branch ?
Thanks !
Hello
I'm building lineage 13 for my stylo 2 plus , i need some help on how to merge lg kernel source into its caf branch, i already know the caf tag that lg started working from but i don't know what's the steps i should follow to merge it into the latest caf branch i want to make it like this commit
https://github.com/MSM8916-Samsung/...mmit/42993da293d3a1497b9e6e90bcea842c1a2857d4
I have general git merge and diff knowledge but need the exact steps on how to do it
?
I'm new to the android build system but have been running stripped kernels for years. I'm working on a custom rom for a TCL A30 (MT6762/MT6765).
I've looked at the AOSP code base and TCL source, for a similar device, and it looks like the TCL source generates the needed kernel .config file with scripts. There are multiple scripts for different archs and cellphone carriers. My TCL A30 has a Bangkok_CC (ConsumerCellular) tag and I found arch/arm64/configs/bangkok_TF_defconfig (TracFone). There do not appear to be any patches in the TCL source. The source I found:
TCL-Mobile on sourceforge
Has the Tracfone TCL A3:
Tracfone TCL A3x product link
That source contains Bangkok_TF_defconfig.
I was able to adb pull /proc/config.gz directly from the device and it's running 4.19.126+ released last month.
First question: Can I generate a bangkok_CC_defconfig from /proc/config.gz in the AOSP code base? It is mosttly monolithic
Code:
cat .config | grep =m > kernel_modules.txt
CONFIG_IKHEADERS=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_SERIAL_OF_PLATFORM=m
CONFIG_BATTERY_MT6359=m
CONFIG_SND_SOC_MT6359_ACCDET=m
CONFIG_USB_DUMMY_HCD=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMSTAT_TRACER=m
At the time of this post the latest upstream is 4.19.244
Second question: Are most Android projects like Debian/RHEL where they back patch kernel vulnerabilites? Would the most up-to-date kernel result from the latest AOSP source and would building it just be a matter of dropping in my /proc/config.gz and setting the build environment that I found in the TCL source?
I suspect that AOSP is contributing back to kernel.org. Third question: AOSP vs Kernel.org source? Does Google backport like RHEL/Debian? Or would I get a more recent,, secure kernel using upstream kernel.org source?.
Last question Clang vs GCC. I've just setup my Arch Linux build box w/ arm64_gcc. Speed is less important to me than stable builds. What are the arguments for one compiler over another?