Hi Guys,
I've never used repo before but I am trying to get hold of a copy of the cyanogenmod sources (jellybean). I followed the instructions on this page (grr no links!) wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Compile_CyanogenMod_9_(Linux) down to this section:
Code:
repo init -u git:// github.com/CyanogenMod/android.git -b ics
Now I changed "ics" at the end to "jellybean" as I assumed that was the latest branch for CM10. Then I've run:
Code:
repo sync -j4
Now I'm just wondering (as my sync has been going for hours) is this syncing all of the cyanogenmod sources? I've seen quite a lot of references scroll across the screen that relates to previous versions of android. Or is this actually just download the jellybean code?
Thanks
Oh well, scratch that. It finished about 10 minutes after asking! Sods law eh?!
Related
Hi guys, I'm new on deving and this is the first time I try to compile a rom...
I'm a sensation user, but I want to make an aokp build for my friend that has a galaxy ace with a good working cm9 rom...
now, can someone help me to understand which source use, which git sync, I am pretty confused...
I have the aokp source here https://github.com/aokp
and maclaw source (fixing things on cm9) here https://github.com/MaclawStudios
I followed a classic guide to compile aokp/cm9 fron source and I already installed all the necessary stuff (sdk, jdk ecc) to compile.
now I'm confused about how proceed with source and git...maybe if someone tells me what I have to type on the terminal and the reason why I am typing it would be great
thanks for your time
throcker said:
Hi guys, I'm new on deving and this is the first time I try to compile a rom...
I'm a sensation user, but I want to make an aokp build for my friend that has a galaxy ace with a good working cm9 rom...
now, can someone help me to understand which source use, which git sync, I am pretty confused...
I have the aokp source here https://github.com/aokp
and maclaw source (fixing things on cm9) here https://github.com/MaclawStudios
I followed a classic guide to compile aokp/cm9 fron source and I already installed all the necessary stuff (sdk, jdk ecc) to compile.
now I'm confused about how proceed with source and git...maybe if someone tells me what I have to type on the terminal and the reason why I am typing it would be great
thanks for your time
Click to expand...
Click to collapse
https://github.com/AOKP/platform_manifest/tree/ics
Read the read me there,then add your device and kernel tress then.add the proprietary files (vendor tree)
Then you should be able to compile...keyword should...
Sent from my HTC PH39100 using Tapatalk 2
ok! exactly, but I'm a bit confused about device trees, proprietary files....I don't know exactly what they are and what commands I should use to add them!...
example: ok I add the aokp repo
$ repo init -u https://github.com/AOKP/platform_manifest.git -b ics
$ repo sync
temporary fix to build:
$ install -d prebuilt/android-arm/kernel
curl -o prebuilt/android-arm/kernel/LINUX_KERNEL_COPYING -O
now? what sould I take from here https://github.com/MaclawStudios and how do I add on the source? with what commands I mean...
and I don't know which of them are the device tree and vendor tree...(but at least I understood which one is the kernel tree XD)
thanks a lot for your help
I found this command to clone git from a cm9 source
$ git clone https://code.google.com/p/cooper-cyanogen/
here https://code.google.com/p/cooper-cyanogen/source/checkout
and what if I sync the aokp repo, than clone this git?
if is possible to do, when should I add it?
I'm not sure if this is the place to ask this, but I've been playing with building AOSP over the past week. I've got everything synced, ccache, and have built it 4 times. But I have a few questions:
My process: First I "repo init -u <insert proper google url> -b android-4.2.1_r1.2" for the latest 4.2 branch as opposed to just "repo init -u <insert proper google url>" for the master branch, then I do a "repo sync", then I initiate the build "make clean -j9 otapackage".
Questions:
1. By doing repo init with the 4.2.1_r1.2 branch, when I build it, does that ensure that I am building from that branch? So you have to repo init for whatever branch you want to build and the make knows which branch to compile from?
2. If I repo init many branches, and sync those branches to my computer, I can do a make on them later without syncing, as long as I did the init command just before the make command? Of course, I may no longer be in sync with the main repository, but I'll still be building the code as it was previousely? I.e. there is no need to sync before each build as long as you are happy with the code currently on your machine?
3. How often do the branches change? It seems each day I sync and get new projects, etc.
4. Should I do "make -j1" instead of "make -j9"? The latter does the build in under an hour and the former make take several hours. Is it really likely that using multiple thread will cause errors? Could I check that by just compiling the code with "-j9" a few times in a row without a repo sync in order to compare the builds to see if they have the same md5 or something?
I'm still trying to figure out how to get my build to incorporate certain proprietary binaries that are not included in the AOSP. I know I can get these binaries from my phone, or from factory images, or elsewhere (I'm building for my Verizon galaxy nexus - toro). Can I just drop them into the flashable zip? Or is it better to incorporate them into your local code with modifications to the make files that will automate compiling them into the build and otapackage? I have been doing some research on that and think I am almost to the point where I know which make files to modify. Any clues or hints are greatly appreciated.
Also, is there a way to make the otapackage odexed? Or does the phone automatically make the odex files as you run all the apps? <-that's the impression I get after doing some reading.
hey guys just as the title says,, i want to compile jelly bean and ics for my devices,, is there a way i can download both sources at once??
winxuser said:
hey guys just as the title says,, i want to compile jelly bean and ics for my devices,, is there a way i can download both sources at once??
Click to expand...
Click to collapse
In my experience compiling AOSP from source and working with the source code you have to specify which branch of Android you want to download (Can't specfiy multiple banches to download at once) for example to download the latest version of Jelly Bean you would run the command "repo init -u https://android.googlesource.com/platform/manifest -b android-4.3.1_r1". I would recommend creating two different directories to hold your ICS source code and your Jelly Bean source code, an example might look something like the following:
Code:
mkdir ~/android/jellybean
cd ~/android/jellybean
repo init -u https://android.googlesource.com/platform/manifest -b android-4.3.1_r1
repo sync
mkdir ~/android/ics
cd ~/android/ics
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.4_r2.1
repo sync
Let me know if you still have questions.
ok cheers, so i cant sync both at the same time into different folder?
edit: well thats a bit of a b**** then
also one other thing,, what changes to a CM device tree would i need to make to build a aosp rom
winxuser said:
hey guys just as the title says,, i want to compile jelly bean and ics for my devices,, is there a way i can download both sources at once??
Click to expand...
Click to collapse
Xda university has a nice page with some repo tricks.
Shows
Code:
repo init --reference=~/android/cm -u git://github.com/AOKP/platform_manifest.git -b jb
for syncing files faster in the same android version but different sources.
But I don't think that's what you're looking for.
Btw, if you just want to simultaneously download both sources, why don't you just open another terminal window
winxuser said:
also one other thing,, what changes to a CM device tree would i need to make to build a aosp rom
Click to expand...
Click to collapse
I have only a little experience working with modifying device tree's but you shouldn't have really make any changes to the device tree to build AOSP. All you should have to do is download the Cyanogenmod device tree and use that as your device tree for compiling AOSP, what device are you compiling for?
im gonna be compiling for a couple devices,, galaxy s3 lte and huawei sonic u8650
Hi guys,
I regularly run into problems when I try to resync custom rom repos after a while. Sometimes the intended branch in a git repository changes, but a repo sync won't checkout the branch. Is this normal behaviour or a specific problem of my roms manifest?
D802 @ AOSPA 4.4
I am trying to follow this guide:
Code:
https://wiki.cyanogenmod.org/w/Build_for_h901#What_you.E2.80.99ll_need
in order to build cyanogenmod for my H901, but after the initial repo sync "completed" without error, i follow the guide through breakfast and the the file extraction, and brunch fails to build all targets. after this, doing repo sync again gives me this:
Code:
Fetching projects: 99% (524/529) Fetching project CyanogenMod/android_hardware_qcom_display
Fetching project CyanogenMod/android_hardware_qcom_display
Fetching project CyanogenMod/android_hardware_qcom_display
fatal: Couldn't find remote ref refs/heads/cm-13.0
error: Cannot fetch CyanogenMod/android_kernel_lge_pplus
error: Exited sync due to fetch errors
I want to say this is due to the v10 not being a "supported device" for CM13 yet, as it is not listed on the lunch menu. but i was running the test builds in the dev section just fine, and i'm sure it's a fairly simple matter to pull the right stuff from git, but i'm a newbie to this kind of development.
After successfully building from source, i want to build a custom rom based on CM13 and keep the LG stock camera app, and the LGSignboard second screen function, and gain all the Cyanogenmod goodies too. any help or guidance with that quest would be appreciated.
I really hope someone can answer this for you.. :/
I think, you are trying to sync cm-13.0 branch of cyanogenmod lge_pplus kernel repo in your local manifest. But this is not there. Its only the cm-12.1 branch there: https://github.com/CyanogenMod/android_kernel_lge_pplus. For cm-13 you will need a different kernel source path. Hopefully there are already cm-13 roms for your device and with sources on github, where from you can sync?
Okay, that makes sense.
I was following a guide on CM wiki to build CM13 for the v10, why would that branch not be present on github if there is a guide to build from it?
I'll poke around github and xda for available kernel source.
Sent from my LG-H901 using XDA-Developers mobile app