Hey, i just compiled my first CM7 build from sources, this is what i did:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
cd ~/android/system/device/htc/bravo/
./extract-files.sh
~/android/system/vendor/cyanogen/get-rommanager
cd ~/android/system/
repo sync
. build/envsetup.sh && brunch bravo
Click to expand...
Click to collapse
Homever, the flashable zip is called "update-cm-7.2.0-RC1-bravo-UNOFFICIAL-signed" (same in build.prop), while the latest version is RC3.
So do i actually have RC1, or RC3 and there is something wrong with build bot and it's renaming flashable .zip and build.prop incorrectly?
Anyone experienced this?
Related
Hi,
I compiled ICS by myself. At first I initialized the repo with
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.3_r1
and then I synced it and installed the binary drivers.
Then I did
Code:
source build/envsetup.sh
lunch
and I choosed number 8 (full_maguro-userdebug). After that I compiled it with:
Code:
make -j1 otapackage
After all that I get a flashable rom which runs nice on my Galaxy Nexus. But it seems the build was not complete. For example phase beam was not compiled. How can I get a full build of Ice Cream Sandwich?
I decided to give building CM a try again recently and set up a new Ubuntu VM for the task. I'm encountering some problems however. I setup my repo with the new 10.1 branch which I believe is now pulling down 4.2.2. At the end of repo sync, I receive:
Code:
info: A new version of repo is available
object 91f011ab0df9e1aa215e39b424c9ce2614bae50e
type commit
tag v1.12.1
tagger Conley Owens <[email protected]> 1360088708 -0800
repo 1.12.1
gpg: Signature made Tue 05 Feb 2013 01:25:08 PM EST using RSA key ID 338871A4
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.1'
I wasn't sure if this was actually a problem so I proceeded to get-prebuilts and the envsetup script. After that I run "breakfast maguro" but that's where I hit a wall:
Code:
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/maguro/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_maguro". Stop.
Device maguro not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_maguro
Default revision: cm-10.1
Checking branch info
CyanogenMod/android_device_samsung_maguro already exists
Syncing repository to retrieve project.
error: project device/samsung/maguro not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/maguro/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_maguro". Stop.
** Don't have a product spec for: 'cm_maguro'
** Do you have the right repo manifest?
At this point I don't have a maguro device folder so I can't proceed to the extract-files script. I don't know if my setup is wrong or if these are temporary problems since the 4.2.2 merge. Is anyone able to build right now, and if so do you know what might be wrong?
Thanks!
I'm having the very same problem. I'm thinking there's just some problems with the 4.2.2 merger.
same problem here
Okay, good to know it's not just me. Any place it should be reported or something? There are 4.2.2 nightlies for our phone so building must be possible, just not downloaded fresh, maybe it's an issue with the Github project.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Ok found it.
cd ~/android/system
cd .repo/repo
git pull -s resolve
cd ~/android/system
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo sync
. build/envsetup.sh
breakfast maguro
zorxd said:
Ok found it.
cd ~/android/system
cd .repo/repo
git pull -s resolve
cd ~/android/system
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo sync
. build/envsetup.sh
breakfast maguro
Click to expand...
Click to collapse
You rock! Worked great. Can I ask how you figured that out, just for future reference?
Thanks for the help!
found it on a german web site
this issue came down from AOSP.
I'm trying to build android from source for the htc ace (desire hd) and I don't know how to use lunch. I'm looking for a config file for this device but I can't find anything. I don't know if I have to use a generic config or adapt one from other similar device. Anyone who compiled for this device could help me?
atimus said:
I'm trying to build android from source for the htc ace (desire hd) and I don't know how to use lunch. I'm looking for a config file for this device but I can't find anything. I don't know if I have to use a generic config or adapt one from other similar device. Anyone who compiled for this device could help me?
Click to expand...
Click to collapse
Try: http://forum.xda-developers.com/showthread.php?t=2533007
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment
Code:
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/Mustaavalkosta/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Click to expand...
Click to collapse
nikt11 said:
Try: http://forum.xda-developers.com/showthread.php?t=2533007
Click to expand...
Click to collapse
Thank you!!
This may be a stupid post. I have tried to search the forum. However, I don't find any solution.
I am new to Andriod, Cm11, and git. I have background on Gcc etc.
I have installed the CM11 rom to my DHD, it works very well. So I am curious on how to build a rom from source by myself.
the ennvironment is set up. I can build the latest Andriod code without problem. BTW, the image seems quite big.
I follow the first post of this thread.
However, i encounted error with "lunch cm_ace-userdebug".
I try several different methods to retrieve DHD relevant files. but no help.
the errors are as following:
lunch cm_ace-userdebug
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/htc/ace/cm.mk]]: "device/htc/common/common.mk" does not exist。 停止。
Device ace not found. Attempting to retrieve device repository from CyanogenMod Github .
Found repository: android_device_htc_ace
Default revision: cm-11.0
Checking branch info
Default revision cm-11.0 not found in android_device_htc_ace. Bailing.
Branches found:
froyo
froyo-stable
gb-release-7.2
gingerbread
gingerbread-release
ics
cm-7.1.0
cm-7.0.3
cm-7.0.2.1
cm-7.0.1
cm-7.0.0
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/htc/ace/cm.mk]]: "device/htc/common/common.mk" does not exist。 停止。
** Don't have a product spec for: 'cm_ace'
** Do you have the right repo manifest?
How can I solve it?
thanks,
fenildf
You may want to post this in a more general development forum. You don't need to be restricted to DHDs; it'll be the same with other phones too.
Hi,
I'm just as new to building android images as you are, but, surprisingly, it worked for me just yesterday. So maybe I can help.
In the messages you posted I see only the officially supported dhd android versions. So, I guess you need to somehow enable the unofficial cm11 first. My guess is, this will do just that, but I'm not sure:
Go to the directory where your hiddden .repo directory is in (where you issued repo init), then issue this commands
Code:
mkdir .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
The commands I did are as follows (I had some problems and actually did much more, but I think this is all that's really needed):
Code:
mkdir cm11
cd cm11
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
make bacon
After that (and a loooong wait) I found this in the out directory:
Code:
out/cyanogenmod/target/product/ace/cm-11-20140505-UNOFFICIAL-ace.zip
Here you can learn how to build CyanogenMod for Xiaomi Redmi 1s [armani]
For the first time you try to build CM12.1
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_honami
Initialize the CyanogenMod source repository For CyanogenMod 12.1 [Lollipop]
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
Initialize the CyanogenMod source repository For CyanogenMod 13 [MarshMallow]
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
Get the required local manifest for CyanogenMod 12.1 [Lollipop]
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.githubusercontent.com/onano/local_manifests/cm-12.1/roomservice.xml > ~/android/system/.repo/local_manifests/roomservice.xml
Get the required local manifest for CyanogenMod 13.0 [Marshmallow]
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.githubusercontent.com/onano/local_manifests/cm-13.0/roomservice.xml > ~/android/system/.repo/local_manifests/roomservice.xml
Download the source code
Code:
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Setup the build environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast armani
Build the ROM (takes long time)
Code:
brunch armani
If the build finishes successfully, you will find the build here (change DATE into the date):
Code:
[U]~/android/system/out/target/product/armani/cm-12.1-DATE-UNOFFICIAL-armani.zip[/U]
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.githubusercontent.com/onano/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/roomservice.xml
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Build the ROM
Code:
brunch armani
If the build finishes successfully, you will find the build here (change DATE into the date):
Code:
[U]~/android/system/out/target/product/armani/cm-12.1-DATE-UNOFFICIAL-armani.zip[/U]
Some suggestions for faster builds:
* Enable ccache
* Use the fastest hdd on your pc to store the source, build output & ccache
* You can also buy an ssd, if it's not large enough to hold everything, just store the build output & ccache
Credits: Thanks to armani-dev for their hardwork on CyanogenMod and mikeionannia For His Guides.
reserved
:good: