HI, I'm trying to compile cyanogen's kernel for mako
however with the compiler I used to compile AOSP sources, cm won't compile without modification to source code.
Can anyone tell the toolchain used by CM for it's releases so I can do a successful complication without source code modification?
Anyone willing to tell the toolchain?
Related
I invite all community members with experience in compilation, testing with Linaro 4.7.1 toolchain,
know that the previous version and instability caused incopatibilidad CM9, but I think the new Linaro 4.7.1 toolchain is compatible,
Here is a link as a reference for a dev to compile your kernel and CM9, and works great.
http://forum.xda-developers.com/showthread.php?t=1630023
I think this may be possible, those who support this project by CM9 rom faster and have the benefits Linaro.​
LINARO INFORMATION​
Kernels can be compiled with Linaro toolchain, really nothing new. CM9 source code needs to be modified to compile with Linaro, IMO it isn't worth it. Also, why in the hell do we need any OpenWRT-related Linaro patch?
Hi, I wanted to build a CM12 kernel. I used CM kernel source and built a basic one that booted. Now i want to add features. I referred to guides and understand how to cherrypick using commits but instead of doing git fetch, I git cloned it. Now i have a folder of my kernel and other kernel. How do i cherrypick from that folder into my kernel?
Whilst compiling Cyanogenmod I got this error:
Code:
ccache: FATAL: Could not find compiler "arm-eabi-gcc" in PATH.
Based on the manifest
https://github.com/LineageOS/android/blob/cm-12.1/default.xml#L542
the compiler is platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
from
https://android.googlesource.com/pl...inux-x86/arm/arm-eabi-4.8/+/android-5.1.1_r37
If I add that full path to my PATH variable I can compile the ROM successfully.
However, that seems wrong to me.
The compiler is already part of the source tree.
Shouldn't something in one of the make files or build scripts be setting this rather than me setting it manually?
Note: I am not using a custom toolchain, it is the standard one from aosp.
opticyclic said:
Whilst compiling Cyanogenmod I got this error:
Code:
ccache: FATAL: Could not find compiler "arm-eabi-gcc" in PATH.
Based on the manifest
https://github.com/LineageOS/android/blob/cm-12.1/default.xml#L542
the compiler is platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
from
https://android.googlesource.com/pl...inux-x86/arm/arm-eabi-4.8/+/android-5.1.1_r37
If I add that full path to my PATH variable I can compile the ROM successfully.
However, that seems wrong to me.
The compiler is already part of the source tree.
Shouldn't something in one of the make files or build scripts be setting this rather than me setting it manually?
Note: I am not using a custom toolchain, it is the standard one from aosp.
Click to expand...
Click to collapse
Toolchains aren't automatically set, at least for now. Possible causes being...
There are multiple versions of Toolchain that are synced together, and it isn't necessary that the newer version of the same toolchain "must" compile the code with success, which was properly compiled by an older version.
Also, by this, the developer has complete freedom to change the ROM/Kernel toolchain.
Coming to the Question in Thread Title, If you're building a ROM, then toolchain has to be added in PATH
Arvind7352 said:
Toolchains aren't automatically set, at least for now. Possible causes being...
There are multiple versions of Toolchain that are synced together, and it isn't necessary that the newer version of the same toolchain "must" compile the code with success, which was properly compiled by an older version.
Also, by this, the developer has complete freedom to change the ROM/Kernel toolchain.
Coming to the Question in Thread Title, If you're building a ROM, then toolchain has to be added in PATH
Click to expand...
Click to collapse
Thanks for clarifying.
Ideally it should scan the source tree for the compiler by default so it has something to fall back to in case a custom one is not specified.
What confused me is that I don't see this nugget of information specified in any of the guides I read about compiling ROMs.
I have a linux environment, kernel source, but no toolchain to compile it with.
Can someone guide me on how to compile a kernel for the device? :good:
So Google removed all source code for Android support and Androidx libraries from the AOSP distribution.
I already have a compiled AOSP on my machine, and now I have downloaded and compiled AndroidX separately as well from the AndroidX googlesource website.
So now I want to include these AndroidX compiled libraries with my AOSP distribution, so that when I compile the AOSP source code, it (AOSP) will get compiled with the locally compiled AndroidX libraries. How do I achieve this?