[DEV] Building CM from scratch (the easy way)! - *nix Shell Script

Search This thread

nocomp

Senior Member
Feb 3, 2007
926
120
argonay
all right i get it now
at least i get some time to get familiar with it.
how do you do for create a new version of the mod, like if you want to create a new rom name?

thx for your time
herve
 

nocomp

Senior Member
Feb 3, 2007
926
120
argonay
hi,
just tried my today build, and gosh what a nightmare.
clock has been set to jan 6 1980 .... live wallpaper is frame per frame, terribly slow.
i don t do a full wipe, can it be the cause?
i just did a build not a complete andromake, is it still update?

thxx for your help

herve
 

nicandris

Inactive Recognized Developer
Jan 5, 2009
1,141
215
Amsterdam
plus.google.com
hi,
just tried my today build, and gosh what a nightmare.
clock has been set to jan 6 1980 .... live wallpaper is frame per frame, terribly slow.
i don t do a full wipe, can it be the cause?
i just did a build not a complete andromake, is it still update?

thxx for your help

herve

androidmake its just for the first time. my builds are terribly slow also actually... sux big time. try cd ~/android/system and then make clean. after that build again. probably though it should be teamdouche fixing stuff that y its getting slower
 

nocomp

Senior Member
Feb 3, 2007
926
120
argonay
one question,
i am re fetching the whole tree, and i was wondering, if you want ot build froyo based or else, how do you proceed?
thx for helping
rv
 

drigerott

Senior Member
Jan 1, 2010
335
72
36
Torino
ah ok... is not just me then ^^ thx nicandris ^^ but why nightly is normal and manual build not? some problem in repo?
 
Last edited:

ch33kybutt

Retired Recognized Developer
Oct 25, 2008
635
812
Is there any difference if built using x86 vs x64? I get the same weird graphics & slow-motion problems and I'm using x86.
 

redstar3894

Retired Recognized Developer
Jun 3, 2010
428
119
Chicago, IL
redstar.euroskank.com
not sure if the repo for froyo is still there (i think it is). if you want the froyo tree, try
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
Its all still there, just no one has touched it for about 3 months, so it might be a little dusty... :p
Is there any difference if built using x86 vs x64? I get the same weird graphics & slow-motion problems and I'm using x86.
No difference between building on 32 or 64 bit.... at least there shouldn't be... :rolleyes:
 

nocomp

Senior Member
Feb 3, 2007
926
120
argonay
hi,
i ve finally resync all tre, and build new rom, but still same disaster......
can t belive they didn t fixed it :/
can t we pull the last "working "tree ?
any luck with V2 ?
thx for your time
 

Top Liked Posts

  • There are no posts matching your filters.
  • 107
    <BACON>

    This will Allow you to build CM7-Nightlies or "Kangs" at any time you please.

    Compatible with Ubuntu or rpm distros

    It's a bash/sh script for automation, as simple as a double click.

    it's downloading and installing all files/repos/sdk/adb/fastboot and compiles. (If you already have some of this installed, it prompts before installing)

    -------

    Please test it, and report bugs here (files attached)
    No donations wanted, just click that THANKS button ;)

    Github: https://github.com/nicandris/CM-from-scratch


    Screenshot-1.png


    -------


    new build.sh menu
    Screenshot-Terminal.png


    just unzip on ubuntu/linux and run ./douchebuild.sh
    if ./douchebuild.sh is not recognized as an executable, just
    Code:
    sudo chmod 775 douchebuild.sh
    You will be asked for sudo pass (since you edit repos and add adb in bin) and some info for git.

    after completing you can always create a fresh build from the Desktop shortcut build.sh

    ofcourse i don't take any credits for cm, all credit goes to cyanogen and teamdouche. the script is just a shell compilation of the cm wiki.

    </BACON>
    12
    Reserved

    If you want to set only udev try this script
    View attachment udev.zip
    unzip and
    Code:
    chmod 755 udev.sh

    -----

    If you already used the main script and want to have the new build.sh menu, run this script
    View attachment buildshcreator.zip
    -----

    if you don't want all the files for all the devices to be synced, follow this!
    12
    Reserved

    CHANGELOG

    v1
    Supporting only Nexus One (initial release)

    v2
    Supporting all cyanogenmod official devices. Added menu selection for device

    v2.0.1
    Fixed some nohup issues. Changed some code lines. fixed an if statement

    v2.0.2
    HD2/Leo support added

    v2.1
    Various Bugfixes
    New build menu

    v2.2
    Few bug fixes
    Some name changes
    MORE options in build.sh!!

    v2.3
    Minor Bug Fixes

    Added new devices:
    Motorola Cliq XT
    LG G2x
    LG Optimus 2X
    Samsung Captivate
    Samsung Vibrant
    Barnes & Noble - Nook Color support

    Added udev support for Nook Color


    v2.3.2

    Fixed selection list
    Added HTC Incredible 2 Support

    v2.4.1
    Added Samsung Galaxy S II and Fascinate support
    Added Motorola Droid X support
    udevs fixed

    v2.4.3
    Added HTC Tattoo

    v2.5.1
    Updated Android SDK to v13
    Forced repo to sync from github and not from kernel.org (since kernel.org is down for maintenance)
    Bugfix


    v2.5.2
    Added Nexus S 4G

    v2.5.3/2.5.4
    minor bugfix x4 :p
    changed repo fetch URL


    v2.7.1
    RPM compatibility
    Small bugfix
    5
    You'll actually need to edit android/default.xml and copy your modified file to .repo/manifests/default.xml. Next repo sync, you should see less projects. Mine is now down to 198 from 234.

    WARNING:
    If CM team does make any changes to upstream manifest (add or remove new/obsolete projects), these changes will not be synced to your machine, since default.xml has been modified. To force re-sync with upstream manifest, you'll have to do this ...
    $ cd android
    $ git reset --hard
    $ cd ..
    $ cp android/default.xml .repo/manifests/default.xml
    $ repo sync

    In fact, to discard ALL changes you've made to ALL projects/repositories, do this ...
    $ repo forall -c git reset --hard
    $ repo sync

    5
    Very useful guide! Appreciate hard work!