I'm trying to learn how to modify certain android components but I'm having trouble compiling from source.
I downloaded Launcher2 from cyanogen git://github.com/cyanogen/android_frameworks_base.git but Eclipse says it can't resolved some classes.
Some of these classes belong to other repositories like android_framework_base core and graphics. Do I need to bring the sources for these too? will these get compiled into -the Launcher making it huge? What is the correct configuration for eclipse to compile individual apps?
Thank you in advance.
i have the same problems with u~
yes, you need the whole android tree.
then do:
make Launcher2
hope that helps.
I'm looking to compile the stock Calendar app. I'm not quite sure how to do this. Do I have to download the whole Android tree? Can I download only the Calendar repository & compile from there?
You can pull the source code for the single application and compile it using an IDE.
Hey I'm looking into compiling an apk from the app source provides in Cyanogen but I'getting errors in eclipse
Correct me if I'm wrong but do we need to sync the entire repo of cyanogen just to compile a single apk
Hi, this is the first time that i try to compile a rom from source! Now I downloaded the source from google, but if I want to compile the aosp with UbertTC, what should I do? Thanks I use Ubuntu with Virtual machine.
Hello,
I recently compiled CyanogenMod 14.1 for my Android device using the official sources and want to compile Omni 7.1 for the same device and use the device tree and kernel from the official CM sources because there's no device tree for Omni. Is there a way to "convert" the CM device tree to work with the Omni sources? My exact problem is the compiler doesn't know my device so I can't run something like "brunch [device]" or "make [device]", although I already downloaded all device-specific repositories to the same subdirectory as I'd do it on CM.
Thanks in advance,
Oebbler
Oebbler1 said:
Hello,
I recently compiled CyanogenMod 14.1 for my Android device using the official sources and want to compile Omni 7.1 for the same device and use the device tree and kernel from the official CM sources because there's no device tree for Omni. Is there a way to "convert" the CM device tree to work with the Omni sources? My exact problem is the compiler doesn't know my device so I can't run something like "brunch [device]" or "make [device]", although I already downloaded all device-specific repositories to the same subdirectory as I'd do it on CM.
Thanks in advance,
Oebbler
Click to expand...
Click to collapse
You have to go to your android_device_manufacturer_yourphonecodename repo and rename cm.mk to omni_codename.mk, open it and change cm_codename to omni_codename.
You have also to rename cm.dependencies to omni.dependencies, but the repos included in that file may not be in omnirom source, so you would need to manually sync those repos in your android sorce tree.
You might have to make other minor changes, take a look at the rest of code in that repo.
For further info: https://docs.omnirom.org/Porting_Omni_To_Your_Device
Thank you, but I think I won't succeed in building Omni for my device because I always get strange errors.
Probs will get annoyed, cmsdk, cmhw, and cm encryption are significantly annoying. Also they moved their build dir, generally include useless common subtrees, and named dtbtool with CM suffix. Their build tree might be the most significant hindrance to unified building on Android, not only for the many unnecessary additions and dependencies they have for devices, but also they generally lack a community presence to answer or respond to users, so a lot of us get stuck with cleaning up their mess.
Notice how TWRP has a community presence here and are helpful. I'm not hating on cm, they have been doing this longer than most of us, but for ease id recommend using your rom choices tree.
Also the immensely significant annoyance of having to track devicesettings and the unwillingnes to nuke cmactions, combine it with cmsdk, or at least remove it's dependency in most trees is almost certainly going to cause you errors.
Sent from my One using XDA-Developers Legacy app