[Tutorial] Compile ICS on Ubuntu

Search This thread
By:
Advanced…
PipelinerArd

PipelinerArd

Senior Member
Aug 1, 2011
906
1,968
GB
meettomy.site
I'm very new to developing and I'm in the process of setting up my kitchen and I just wondered is it a requirement to have Ubuntu or is it just recommended? I'm running a windows pc, is that alright?
 
justlovejoy

justlovejoy

Senior Member
Dec 29, 2009
1,198
1,078
Cybertron/Earth
en.wikipedia.org
Samsung Galaxy Note 10+
Samsung Galaxy Note 20 Ultra
PipelinerArd said:
I'm very new to developing and I'm in the process of setting up my kitchen and I just wondered is it a requirement to have Ubuntu or is it just recommended? I'm running a windows pc, is that alright?
Click to expand...
Click to collapse

Your kitchen isn't an Ubuntu environment where you would follow this tutorial. If you'd like to follow this tutorial, you need to be on Ubuntu. Check the kitchen thread to find out about the specs for using kitchen. It's in here but I'm not on PC to link it easy. Go to Ubuntu website to learn more about how to install or try Ubuntu using windows. If youd wish to follow this tutorial.

Sent from my SPH-D710 using Tapatalk 2
 
Last edited:
  • Like
Reactions: PipelinerArd
D

Dreamboxuser

Senior Member
Jan 24, 2012
380
83
So I am downloading the ics branch of cyanogen and was wondering a few things. First just how big is it cause I'm at 7 gig now and its still goin strong. Also currentlly my .repo directory is in my working directory(/home/android/cyanogen) I was just wondering if someone could give me a basic rundown of the directory structure or point me in the right direction.

Sent from my GT-S5360 using Tapatalk
 
dastin1015

dastin1015

Inactive Recognized Developer
Dec 2, 2010
3,849
10,580
30
Wallops Island, VA
HTC EVO 3D
Samsung Epic 4G Touch
Dreamboxuser said:
So I am downloading the ics branch of cyanogen and was wondering a few things. First just how big is it cause I'm at 7 gig now and its still goin strong. Also currentlly my .repo directory is in my working directory(/home/android/cyanogen) I was just wondering if someone could give me a basic rundown of the directory structure or point me in the right direction.

Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse

CM is much more feature laden so it will take longer to download because there is much more to download. I don't know the exact size plus my CM source has much more because of added device repos and whatnot. All the folders will be inside the cyanogen folder when the repo sync is complete.

私のEVO 3Dから送信される。
 
  • Like
Reactions: Dreamboxuser
D

Dreamboxuser

Senior Member
Jan 24, 2012
380
83
dastin1015 said:
CM is much more feature laden so it will take longer to download because there is much more to download. I don't know the exact size plus my CM source has much more because of added device repos and whatnot. All the folders will be inside the cyanogen folder when the repo sync is complete.

私のEVO 3Dから送信される。
Click to expand...
Click to collapse

Ya I figured that was the case because the vanilla source is supposed to be around 6. Ya it was a little confusing going thru the directories in the .repo folder. I thought I missed something(ya patience).

I have seen make used with several different variables (-1 -4 -16) what is the difference and which is better for a 32 bit system.(found it. Number of jobs done at once.)

Sent from my GT-S5360 using Tapatalk
 
Last edited:
lithid-cm

lithid-cm

Inactive Recognized Developer
Jul 1, 2010
3,189
2,956
Cleveland
Dreamboxuser said:
Amazing resource. Well put together. Going to be very helpful when I get the source in a few days.. I have the slowest connection ever.

Will repo work if it is in multiple sessions because my connection dies after a few hours.

Sent from my GT-S5360 using something
Click to expand...
Click to collapse
I don't have the best connection either. There have been reports that if you are having connection issues you should do a repo sync and forcing one job "-j1". You can also edit your tcp throughput on the kernel level to help keep packets alive longer locally. Both settings in detail can be found at android.googlesource.com

Also, repo doesn't care. You can restart it as many times as you want. Doesn't break anything.
Sent from my Nexus S 4G using xda premium
 
Last edited:
  • Like
Reactions: Dreamboxuser
lithid-cm

lithid-cm

Inactive Recognized Developer
Jul 1, 2010
3,189
2,956
Cleveland
dastin1015 said:
CM is much more feature laden so it will take longer to download because there is much more to download. I don't know the exact size plus my CM source has much more because of added device repos and whatnot. All the folders will be inside the cyanogen folder when the repo sync is complete.

私のEVO 3Dから送信される。
Click to expand...
Click to collapse
This only applies to the gingerbread branch. Cm9 uses room service and not keep any extra devices local.

Sent from my Nexus S 4G using xda premium
 
D

Dreamboxuser

Senior Member
Jan 24, 2012
380
83
lithid-cm said:
I don't have the best connection either. There have been reports that if you are having connection issues you should do a repo sync and forcing one job "-j1". You can also edit your tcp throughput on the kernel level to help keep packets alive longer locally. Both settings in detail can be found at android.googlesource.com

Also, repo doesn't care. You can restart it as many times as you want. Doesn't break anything.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse

So ya the repo sync -j1 worked well seems like more things are getting completed. 8.7 gig (17,115 objects) and climbing just incase anyone was wondering. I do still have 100 gigs left for builds so I should be ok (I think).
Also can anyone direct me to info on how to modify a gingerbread kernel to run cm9. I know I read it somewhere and bookmarked it but I can't remember which device lol. I do have the manufacturers gb source.

Sent from my GT-S5360 using Tapatalk
 
Last edited:
cdesai

cdesai

Inactive Recognized Developer
Jan 16, 2011
2,296
4,089
IN YOUR HEAD
Dreamboxuser said:
Also can anyone direct me to info on how to modify a gingerbread kernel to run cm9. I know I read it somewhere and bookmarked it but I can't remember which device lol. I do have the manufacturers gb source.

Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse

Depends on the chipset, minimum changes needed are modifying the BOOTCLASSPATH in init.rc and adding the new classes, and patching the touchscreen driver
Other changes might also be needed, but that depends on the device you are building for
 
D

Dreamboxuser

Senior Member
Jan 24, 2012
380
83
cdesai said:
Depends on the chipset, minimum changes needed are modifying the BOOTCLASSPATH in init.rc and adding the new classes, and patching the touchscreen driver
Other changes might also be needed, but that depends on the device you are building for
Click to expand...
Click to collapse

Its for a samsung galaxy y and its just a project at the moment. I did see the init.rc edits and adding the classes somewhere. New to kernel development as well as building from source so i'm learning as i go. I am however pretty good t trouble shooting and try to search as much as possible before asking. Like i said... just a project for myself.

I do have a OG TF101 that i'm going to be building for so that will be the main use for compiling.

Sent from my Transformer TF101 using Tapatalk 2
 
Last edited:
You must log in or register to reply here.

Similar threads

speed_bot
  • Poll
[HELP/Q&A][SourceBuilding,AllDevices] The Source Building Q&A Help Thread
Replies
2K
Views
276K
D
DiamondJohn
Ronny927
[FIX] [SOLVED!] Play Store No Connection Error Fix!
Replies
359
Views
854K
J
Johncoool
A
  • Poll
[FIX][SOLVED]Status 7 Error with CWM or TWRP Recovery on Rooted Android!
Replies
166
Views
889K
P
pawtz
mripfreely
[Q] Acer Iconia B1 A71 Root
Replies
539
Views
377K
U
unkn0ws
K
How do install a apk from adb command line?
Replies
21
Views
478K
S
saintalfonso

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 43
    dastin1015
    dastin1015
    To compile Ice Cream Sandwich on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling.

    This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.

    Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.

    1) You need the following:
    -JDK 6 if you wish to build Ice Cream Sandwich. You can download it from java.sun.com. Or:
    Code: 
    $ sudo apt-get install sun-java6-jdk

    -Python 2.4 -- 2.7, which you can download from python.org. Or:
    Code: 
    $ sudo apt-get install python

    -Git 1.7 or newer. You can find it at git-scm.com. Or:
    Code: 
    $ sudo apt-get install git-core

    2) Install required packages. 64-bit (recommended)
    Code: 
    $ sudo apt-get install git-core gnupg flex bison gperf build-essential \
  zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
  x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
  libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
  libxml2-utils

    On newer versions of Ubuntu such as 11.10 you may need to do the following:
    Code: 
    $ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so

    3) Configure your USB.
    Code: 
    $ gksudo gedit /etc/udev/rules.d/51-android.rules

    Inside of this blank text file insert:
    Code: 
    #Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"

#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"

#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"

#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"

#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"

#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"

#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"

#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"

#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"

#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"

#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"

#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"

#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"

#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"

#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"

#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"

#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"

#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"

#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"

#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"

#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"

#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"

#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"

#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"

#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"

#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"

#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"

#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"

    4) Save the file and close it and then issue this command:
    Code: 
    $ sudo chmod a+r /etc/udev/rules.d/51-android.rules

    5) Install the repo:
    Code: 
    $ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

    6) Initialize the repo:
    Code: 
    $ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1

    7) When prompted, enter your real name and email address.

    8) Gather the files:
    Code: 
    $ repo sync

    9) Compiling:
    Code: 
    $ source build/envsetup.sh

    Or:
    Code: 
    $ . build/envsetup.sh

    10) Issue:
    Code: 
    $ lunch

    11) Pick your poison.

    12) Now issue:
    Code: 
    $ make -j1


    ~How To Add A Device To The List~

    1) Find the github for your device you wish to add. (For me it is the HTC Hero CDMA)

    2) Now navigate to the location you are going clone the device tree to:
    Code: 
    $ cd WORKING_DIRECTORY/device
$ mkdir htc

    3) Clone the github device tree from remote to local: (The heroc would be whatever you want that folder to be named so make sure it is whatever standard name would be for your device, example: Nexus One [passion], Nexus S [crespo], Motorola Droid [sholes], HTC Incredible [inc], etc.)
    Code: 
    $ git clone git://github.com/TeamICS/android_device_htc_heroc.git heroc

    4) Now navigate into the folder:
    Code: 
    $ cd heroc

    5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.

    6) Extract Device Proprietary Files:
    Code: 
    $ ./extract-files.sh

    7) Navigate back to your home directory for building:
    Code: 
    $ cd ~/WORKING_DIRECTORY

    8) Prepare To Compile:
    Code: 
    $ source build/envsetup.sh

    Or:
    Code: 
    $ . build/envsetup.sh

    9) Get your list of devices:
    Code: 
    $ lunch

    10) Pick your poison.

    11) Now compile:
    Code: 
    $ make -j1

    Or for a flashable zip:
    Code: 
    $ make -j1 otapackage

    ~NOTE~
    If you are running into issues such as:

    Code: 
    Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter".  Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter".  Stop.

** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?

    What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
    View
    5
    dastin1015
    dastin1015
    Sorrell said:
    I'm really sorry for the stupid question, but I can't seem to find the answer for this.

    I'm using Ubuntu 11.10 64bit and I'm trying to get all the dependencies together so I can start playing. I already have all the repos in the default /etc/apt/sources.list enabled and get this feedback when I run
    Code: 
     apt-get install lib32readline5-dev

    Code: 
    Package lib32readline5-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  lib32readline-gplv2-dev

E: Package 'lib32readline5-dev' has no installation candidate

    My question is do I have to get the package "lib32readline5-dev" or can I use the replacement package that apt recommends "lib32readline-gplv2-dev".

    This post seems to suggest that it will work but I just wanted to make sure before I cause a huge problem for myself. :)
    http://xdaforums.com/showpost.php?p=18631398&postcount=401

    Also here is the package information from Ubuntu

    http://packages.ubuntu.com/natty/lib32readline5-dev

    http://packages.ubuntu.com/oneiric/lib32readline-gplv2-dev

    they look like they do the same thing from the description.


    Thanks for having patience and understanding with a N00b, and for all the work that you already put into this post, the information on this site is great.
    --Sorrell
    Click to expand...
    Click to collapse

    You'd be fine using this:
    Code: 
    $ sudo apt-get install lib32readline-gplv2-dev

    I've been compiling without it and I've been fine, but I'm adding now.
    View
    3
    KnowledgeBroker
    KnowledgeBroker
    dastin1015 said:
    To compile Ice Cream Sandwich on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling.

    This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.

    Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.

    1) You need the following:
    -JDK 6 if you wish to build Ice Cream Sandwich. You can download it from java.sun.com. Or:
    Code: 
    $ sudo apt-get install sun-java6-jdk

    -Python 2.4 -- 2.7, which you can download from python.org. Or:
    Code: 
    $ sudo apt-get install python

    -Git 1.7 or newer. You can find it at git-scm.com. Or:
    Code: 
    $ sudo apt-get install git-core

    2) Install required packages. 64-bit (recommended)
    Code: 
    $ sudo apt-get install git-core gnupg flex bison gperf build-essential \
  zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
  x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
  libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
  libxml2-utils

    On newer versions of Ubuntu such as 11.10 you may need to do the following:
    Code: 
    $ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so

    3) Configure your USB.
    Code: 
    $ gksudo gedit /etc/udev/rules.d/51-android.rules

    Inside of this blank text file insert:
    For all HTC Models:
    Code: 
    #Acer
SUBSYSTEM==usb, SYSFS{idVendor}==0502, MODE=0666

#ASUS
SUBSYSTEM==usb, SYSFS{idVendor}==0b05, MODE=0666

#Dell
SUBSYSTEM==usb, SYSFS{idVendor}==413c, MODE=0666

#Foxconn
SUBSYSTEM==usb, SYSFS{idVendor}==0489, MODE=0666

#Garmin-Asus
SUBSYSTEM==usb, SYSFS{idVendor}==091E, MODE=0666

#Google
SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666

#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"

#Huawei
SUBSYSTEM==usb, SYSFS{idVendor}==12d1, MODE=0666

#K-Touch
SUBSYSTEM==usb, SYSFS{idVendor}==24e3, MODE=0666

#KT Tech
SUBSYSTEM==usb, SYSFS{idVendor}==2116, MODE=0666

#Kyocera
SUBSYSTEM==usb, SYSFS{idVendor}==0482, MODE=0666

#Lenevo
SUBSYSTEM==usb, SYSFS{idVendor}==17EF, MODE=0666

#LG
SUBSYSTEM==usb, SYSFS{idVendor}==1004, MODE=0666

#Motorola
SUBSYSTEM==usb, SYSFS{idVendor}==22b8, MODE=0666

#NEC
SUBSYSTEM==usb, SYSFS{idVendor}==0409, MODE=0666

#Nook
SUBSYSTEM==usb, SYSFS{idVendor}==2080, MODE=0666

#Nvidia
SUBSYSTEM==usb, SYSFS{idVendor}==0955, MODE=0666

#OTGV
SUBSYSTEM==usb, SYSFS{idVendor}==2257, MODE=0666

#Pantech
SUBSYSTEM==usb, SYSFS{idVendor}==10A9, MODE=0666

#Philips
SUBSYSTEM==usb, SYSFS{idVendor}==0471, MODE=0666

#PMC-Sierra
SUBSYSTEM==usb, SYSFS{idVendor}==04da, MODE=0666

#Qualcomm
SUBSYSTEM==usb, SYSFS{idVendor}==05c6, MODE=0666

#SK Telesys
SUBSYSTEM==usb, SYSFS{idVendor}==1f53, MODE=0666

#Samsung
SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666

#Sharp
SUBSYSTEM==usb, SYSFS{idVendor}==04dd, MODE=0666

#Sony Ericsson
SUBSYSTEM==usb, SYSFS{idVendor}==0fce, MODE=0666

#Toshiba
SUBSYSTEM==usb, SYSFS{idVendor}==0930, MODE=0666

#ZTE
SUBSYSTEM==usb, SYSFS{idVendor}==19D2, MODE=0666

    4) Save the file and close it and then issue this command:
    Code: 
    $ sudo chmod a+r /etc/udev/rules.d/51-android.rules

    5) Install the repo:
    Code: 
    $ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

    6) Initialize the repo:
    Code: 
    $ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1

    7) When prompted, please configure Repo with your real name and email address. To use the Gerrit code-review tool, you will need an email address that is connected with a registered Google account. Make sure this is a live address at which you can receive messages. The name that you provide here will show up in attributions for your code submissions.

    8) Gather the files:
    Code: 
    $ repo sync

    9) Compiling:
    Code: 
    $ source build/envsetup.sh

    Or:
    Code: 
    $ . build/envsetup.sh

    10) Issue:
    Code: 
    $ lunch

    11) Pick your poison.

    12) Now issue:
    Code: 
    $ make

    Please note that you have already selected your build target with lunch, and it is unlikely at best to run on a different target than it was built for.


    ~How To Add A Device To The List~

    1) Find the github for your device you wish to add. (For me it is the HTC Hero CDMA)

    2) Now navigate to the location you are going clone the device tree to:
    Code: 
    $ cd WORKING_DIRECTORY/device
$ mkdir htc

    3) Clone the github device tree from remote to local: (The heroc would be whatever you want that folder to be named so make sure it is whatever standard name would be for your device, example: Nexus One [Passion], Nexus S [Crespo], Motorola Droid [Sholes], HTC Incredible [Inc], etc.)
    Code: 
    $ git clone git://github.com/TeamICS/android_device_htc_heroc.git heroc

    4) Now navigate into the folder:
    Code: 
    $ cd heroc

    5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.

    6) Extract Device Proprietary Files:
    Code: 
    $ ./extract-files.sh

    7) Navigate back to your home directory for building:
    Code: 
    $ cd ~/WORKING_DIRECTORY

    8) Prepare To Compile:
    Code: 
    $ source build/envsetup.sh

    Or:
    Code: 
    $ . build/envsetup.sh

    9) Get your list of devices:
    Code: 
    $ lunch

    10) Pick your poison.

    11) Now compile:
    Code: 
    $ make -j1

    Or for a flashable zip:
    Code: 
    $ make -j1 otapackage
    Click to expand...
    Click to collapse

    First, thanks for gathering just about everything I needed in one place, I had gotten pretty far in the process on windows before I decided doing it in windows was a stupid idea..

    When I ran this-- 2) Install required packages. 64-bit (recommended)
    Code: 
    $ sudo apt-get install git-core gnupg flex bison gperf build-essential \
  zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
  x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
  libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
  libxml2-utils
    I got back some errors, but I think these things were already loaded, or it was because I hadn't approved the sources..? Not sure, but I'm downloading the source now so it couldn't be THAT important(yet). I'm using ubuntu 11.10 if that helps at all.

    At this point: 9) Compiling:
    Code: 
    $ source build/envsetup.sh

    Or:
    Code: 
    $ . build/envsetup.sh
    could I have done
    Code: 
    $ repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r
    and just be downloading ICS source? Because at the moment, it looks like it is downloading the source for all of the previous android source too.. isn't a bad thing, but I only made my partition 100gb in size because i was going to just work with ICS.
    I'll probably go through this thread a little more throughly and do some other research while this download is going on-- thanks again for putting this thread together!
    View
    2
    dastin1015
    dastin1015
    jschill31 said:
    Hello,

    No matter what lunch combo I pick I now get this error about desirec? I would prefer to build full heroc eng but at this point would be happy with anything... I eve resorted to reviewing Dastin's post on building for Heroc since I keep second guessing myself. I do appreciate everyone's kind help trying to teach a 40 year old a new trick!

    Lunch menu... pick a combo:
    1. full-eng
    2. full_x86-eng
    3. vbox_x86-eng
    4. full_heroc-userdebug
    5. full_heroc-eng
    6. full_heroc-user
    7. full_maguro-userdebug
    8. full_tuna-userdebug
    9. full_panda-eng
    10. TeamICS_desirec-eng
    11. TeamICS_heroc-eng

    Which would you like? [full-eng] 11
    build/core/product_config.mk:193: *** _nic.PRODUCTS.[[vendor/TeamICS/products/TeamICS_desirec.mk]]: "device/htc/desirec/full_desirec.mk" does not exist. Stop.

    ** Don't have a product spec for: 'TeamICS_heroc'
    ** Do you have the right repo manifest?


    Cheers
    Click to expand...
    Click to collapse

    We (Team ICS) use our own source for building. I'll send you a PM later on how to set it up

    私のEVO 3Dから送信される。
    View
    2
    dastin1015
    dastin1015
    dmeadows013 said:
    Well the Vigor (Rezound) was just released, so it is not yet on the CM source. Do I need the kernel source to get what I need?
    Click to expand...
    Click to collapse

    You need more than the kernel. You need vendor files as well. Vendor files tell what your phones hardware is and how to build, etc. You usually get this from CM when they support your phone.

    私のエボ3Dから送信される。
    View

New posts