Guide on how I build my own CM10 test builts

hnl_dk · Jul 31, 2012

This is a follow up on my "old" "Guide on how I build my own CM9 test builts" thread.

Guide how I build CM10 for my Mango.

For the first time you try to build CM10.
Create ~/bin and download repo to that directory. Afterwards set executable bit to make it possible to ”execute”.

Code:

mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo 
chmod a+x ~/bin/repo

Now reboot the computer.

Create ~/android/system and initialize the repository.

Code:

mkdir -p ~/android/system
cd ~/android/system/ 
repo init -u git://github.com/CyanogenMod/android.git -b jellybean

Unpack the attached local_manifest.xml.bz2 and place local_manifest.xml into ~/android/system/.repo

Synchronise towards the current git repositories.

Code:

repo sync

Setup the environmental settings and initialize the Mango build.

Code:

. build/envsetup.sh
breakfast mango

Initialize the Mango build.

Code:

cd ~/android/system/device/semc/mango/
./setup-makefiles.sh

Download the prebuilts

Code:

~/android/system/vendor/cm/get-prebuilts

Check for new changes

Code:

cd ~/android/system/ 
repo sync

Setup the environment again and build the ROM (takes long time)

Code:

. build/envsetup.sh
brunch mango

You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-10-DATE-UNOFFICIAL-mango.zip

The next times you try to build it, you only need to do the following.
Delete build.prop, if not will build.prop not get generated.

Code:

rm -f ~/android/system/out/target/product/mango/system/build.prop

Syncronise the git repositories.

Code:

cd ~/android/system/
repo sync

Setup the environmental settings.

Code:

. build/envsetup.sh

Configure/build.

Code:

brunch mango

You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-10-DATE-UNOFFICIAL-mango.zip

EDIT (August 14. 2012): If the boot.img is not booting, is it most likely due to the bootloader bug.
To make it "work", do the following (replace mango with your own device)

Code:

cd out/target/product/mango/
rm -f ./boot.img ./combinedroot.cpio ./combinedroot.fs ./ramdisk.img
cp ./root/logo.rle ./root/waste_of_space1
cp ./root/logo.rle ./root/waste_of_space2
cp ./combinedroot/logo.rle ./combinedroot/waste_of_space1
cp ./combinedroot/logo.rle ./combinedroot/waste_of_space2
cd ../../../..
brunch mango

bokrug · Aug 2, 2012

just a technical: is it really necessary to reboot the computer after downloading the repo binary? and if so, why is that??

hnl_dk · Aug 2, 2012

bokrug said:
just a technical: is it really necessary to reboot the computer after downloading the repo binary? and if so, why is that??

It is only necessary on some Linux distributions, where you will not be able to execute anything from that directory, before a reboot. You can try to see if you can do it without. If it is working, do you not need it.

pikpok · Aug 2, 2012

hnl_dk said:
It is only necessary on some Linux distributions, where you will not be able to execute anything from that directory, before a reboot. You can try to see if you can do it without. If it is working, do you not need it.

There's no really need to reboot - edit .bashrc in your home directory and add

Code:

export PATH=~/bin/:$PATH

Save, then run:

Code:

source ~/.bashrc

It have to work on all distros

hnl_dk · Aug 2, 2012

pikpok said:
There's no really need to reboot - edit .bashrc in your home directory and add

Code:

export PATH=~/bin/:$PATH

Save, then run:

Code:

source ~/.bashrc

It have to work on all distros

I just want to show the "universal" way.
Not everyone is using bash

pikpok · Aug 2, 2012

hnl_dk said:
I just want to show the "universal" way.
Not everyone is using bash

If someone use another shell, e.g. zsh, then he'll know what files he have to edit

IMO rebooting is wasting time.

hnl_dk · Aug 2, 2012

pikpok said:
If someone use another shell, e.g. zsh, then he'll know what files he have to edit IMO rebooting is wasting time.

no it is not, as you do not need to edit any files. It will work automatically.
It is as much a waste of time to edit the resource-definition scripts.

pikpok · Aug 2, 2012

hnl_dk said:
no it is not, as you do not need to edit any files. It will work automatically.
It is as much a waste of time to edit the resource-definition scripts.

Reboot - about 1 min
Edit one file and paste single command in terminal - for me it's 10secs

But it comes to offtop discussion, so it would be better to end it now

@edit - now when I think about it... bin in home folder won't be added to PATH automatically, at least in Arch Linux. Maybe Ubuntu is more "intelligent" :laugh:

hnl_dk · Aug 2, 2012

pikpok said:
Reboot - about 1 min
Edit one file and paste single command in terminal - for me it's 10secs
But it comes to offtop discussion, so it would be better to end it now

@edit - now when I think about it... bin in home folder won't be added to PATH automatically, at least in Arch Linux. Maybe Ubuntu is more "intelligent" :laugh:

It does not take that long for me to make a reboot

No matter what, is it always good to have more methods to make something work.
It did the last time I tried Arch Linux... and no I am not using Ubuntu (too flashy for me

)

DeVelox · Aug 2, 2012

Assuming that there is an entry in your ~/.profile that adds ~/bin to PATH, a reboot won't do anything that logout/login wouldn't. Furthermore, logout/login (in this case) won't do anything that sourcing ~/.profile wouldn't. So, simply issuing "source ~/.profile" is sufficient on most distributions. If you are using a distribution or a shell that doesn't do this by default, then you probably already know what you need to do.

I do, however, commend hnl_dk's efforts to make things simpler for newcomers to Android and Linux, even if it's not the the "fastest" or the "best" way. Whenever you start getting into one of those "what if?" arguments, things tend to spiral out of control. Sometimes it's better to just make a few assumptions and go with what is most likely to work.

A reboot might be a bit of an overkill, though. :laugh:

ak-a · Aug 8, 2012

Can't run 64-bit prebuilts on my 32-bit Linux

I have a 32-bit Linux box so get the errors:

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file

Had a quick look around, but are there gcc etc. prebuilts for 32-bit Linux boxes?

TIA,
AK-A

hnl_dk · Aug 8, 2012

ak-a said:
I have a 32-bit Linux box so get the errors:

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file

Had a quick look around, but are there gcc etc. prebuilts for 32-bit Linux boxes?

TIA,
AK-A

Did you try to build it as described?
It is working fine on my 32bit debian machine.

If not, please describe hos you try it build it.

ak-a · Aug 8, 2012

hnl_dk said:
Did you try to build it as described?
It is working fine on my 32bit debian machine.

If not, please describe hos you try it build it.

Yeah, followed the instructions as per the first post. Will re-try and see if I missed/messed something and report back.

CosmoDroid · Aug 10, 2012

Hey !!! Do you think I should post my AOSP errors in this thread...so that its easier for us to keep track..?? :highfive:

Snoopo · Aug 10, 2012

As this is a Tutorial Thread for "how to build cm10 on your own" I don't think it makes sense posting errormessages of errm. "android open source project"? As I am writing this I recognize that I do not really understand what you mean.

hnl_dk · Aug 10, 2012

CosmoDroid said:
Hey !!! Do you think I should post my AOSP errors in this thread...so that its easier for us to keep track..?? :highfive:

Like Snoopo is saying, should that be in this thread. Compiling AOSP is not as "user friendly" as CM, as our devices are officially supported by CM and not AOSP.
If you want, can you make a new thread about compiling "AOSP - Jelly bean".

shufuking · Aug 12, 2012

i always stop at "repo sync"

i always stop at "repo sync"
and it always tell me
"Fetching projects: 21% (66/313) fatal: unable to connect to github.com:
github.com[0: 207.97.227.239]: errno=??????"
can you help me

thanks

hnl_dk · Aug 12, 2012

shufuking said:
i always stop at "repo sync"
and it always tell me
"Fetching projects: 21% (66/313) fatal: unable to connect to github.com:
github.com[0: 207.97.227.239]: errno=??????"
can you help me
thanks

Same also happens for me, then I try again and again and again and then it is working.
Lots of people are accessing github, and there is only a limited "whole" for the data to get through.

shufuking · Aug 12, 2012

hnl_dk said:
Same also happens for me, then I try again and again and again and then it is working.
Lots of people are accessing github, and there is only a limited "whole" for the data to get through.

thanks for your suggestion

finally i make it.
another question.
when i perform " brunch smultron"
i got lots of "cannot execute binary file"
and final "make: *** [out/target/product/smultron/obj/lib/crtbegin_static.o] Error 126"

do you know what it means?

hnl_dk · Aug 12, 2012

shufuking said:
thanks for your suggestion
finally i make it.
another question.
when i perform " brunch smultron"
i got lots of "cannot execute binary file"
and final "make: *** [out/target/product/smultron/obj/lib/crtbegin_static.o] Error 126"

do you know what it means?

without more details, my best guess is that you may be building it on a FAT32 or NTFS partition?
then there is a good chance that linux is not able to read the executable bits.

Guide on how I build my own CM10 test builts

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts