I'm sorry if this has been asked before but I need help to try to get CM-13.0 or 14.0 building successfully with UBER toolchains on both system and kernel.
That's all. No special changes. Just the ability to do that is all I'm looking for.
I have the sources setup for standard compiling of CM already. Just trying to switch toolchains from stock.
An help would be greatly appreciated.
I keep getting an error about libatomic.a not existing. If that's any help
Related
Hi all,
I've managed to properly build CM9 so far, but I noticed somehow CM settings aren't included. Does anyone know how to add this to the build? What I tried so far:
Downloaded the source files for CMParts from CM github, placed them in /packages/apps/CMParts/ and added CMParts to the core.mk file in build/../.
It starts compiling, but always returns an error complaining about deprecated API's.
Hope someone can give some advice here! Been searching like crazy the past few days, but cannot seem to find the answer. Thanks in advance...
(oh, and while I'm at it: after a build I have to manually add a couple of libs to /system/vendor/firmware/ -bcm4330 and some others-. Is there anyway to include them in the source so that they are automatically added? Thanks! )
I want to build a linaro optimized build of stock JROOR0 or whatever the number was again. I know how to compile and build a rom. is it as easy as syncing with a repo? cans omsoen help me with this?
i found these maguro instructions
https://android-build.linaro.org/bu...xus-jb-gcc47-aosp-blob-12.08-release/#build=1
would it be as simple as replacing the maguro imgs with toro imgs?
From what I can gather, it's not quite that straight forward, but not far off...
http://forum.xda-developers.com/showthread.php?t=1859470
I like the PA rom but i would want to have the Rom Control / Similar tweaks into PA.
Can someone help me with this.
Thanks
husytcs said:
I like the PA rom but i would want to have the Rom Control / Similar tweaks into PA.
Can someone help me with this.
Thanks
Click to expand...
Click to collapse
build from source. there's a thread about aosp building stickied in general. learn git and its various functions. you'll need linux or mac osx (only builds on master branch, afaik).
explore rom's source you wish to kang @github (or any other git repository). enjoy the beauty of open source. learn how to (at least) read, cherry-pick and merge code.
naturally, after you get your build running, you can't (or shouldn't) ask for help, you need to know how to debug, and how to get yourself out of trouble.
sent from my i9250
I'm trying to build AOKP for the 5110 and I'm stuck after syncing the repo. How do I go about adding the proper device tree and actually beginning the build? The things have tried seem to work improperly and I just get lots of errors. If any dev out there wants to help me with this, it would be greatly appreciated.
Cheers, 64kb.
Alright so I've built and modified both LOS and RR a bit and it went pretty well. Tutorials o'plenty when it comes to building those roms.
However I now want to try and build a rom from scratch and I'd like to base it on CAF.
I've *I think* correctly synced up with the latest msm8996 tag, but I may have ****ed that up as well.
My problem is is that I literally can not find any resource for building with CAF sources, and I can't even find my local_manifests/roomservice, so I have no idea where to start.
If any of you have any resources or want to share a bit of your knowledge it would be greatly appreciated.
Thanks.
Anyone?
Hey, check out AOSP-CAF(https://github.com/AOSP-CAF). This is all you'll ever need and it's updated regularly. The dev has already added all the necessary stuff(HALS) and also has CM's build system so all you need to do is fork some device tree , sync it's dependencies and you should be good to go.
INT3NSE07 said:
Hey, check out AOSP-CAF(https://github.com/AOSP-CAF). This is all you'll ever need and it's updated regularly. The dev has already added all the necessary stuff(HALS) and also has CM's build system so all you need to do is fork some device tree , sync it's dependencies and you should be good to go.
Click to expand...
Click to collapse
Thanks! I've synced up with it and also synced with the OnePlusOSS device tree. The builds are failing however because the pull_library.sh script they give doesn't work anymore. Is there another device tree you would recommend? And how could I go about finding the dependencies?
Thanks for your help