[Android] Warped420:
Let's see if it works

STEP 11​

​

TIME 2 BUILD

Another time when RAM will help you out.

Whatever steps you actually took to get here all depends on how much work has been put into your phone and how much of it you were able to find..

So if you have the following things done, You can continue to build if not, you better go get them.

1. Linux 64 OS

2. Build environment

3. up to date Repo

4. device repo

5. kernel source

6. proprietary files text/ extract.sh

7. prebuilts

8. ccache

9. Build command

10 Teamwork and Patience

"But Warp, you never explained some of this stuff.."

Yep, that's why there is a step about actually building it...

This next section is pulled from PG's read me

Getting my ZTE Sequent repo

$ cd ~/android/system/device/

$ mkdir zte

$ cd zte

$ git clone https://github.com/playfulgod/androi..._zte_warp2.git warp2

Note it says ZTE, not Sony, not Samsung, ETC

Then cd to the kernel directory:

$ cd ~/android/system/kernel

$ mkdir zte

$ git clone https://github.com/playfulgod/kernel_zte_warp2.git warp2

Then prop files from stock..

$ cd

$ cd ~/android/system/device/zte/warp2

$ ./extract-files.sh

When the environment is setup, we need to grab a copy of Term.apk. This is necessary to build CM10.

$ cd ~/android/system/vendor/cm

$ ./get-prebuilts

O k so I waited to tell you about CCACHE at the end. I guess I did that, because you don't need it untill the end anyway..OR is building just the beginning

You decide...

http://ccache.samba.org/manual.html

http://manpages.ubuntu.com/manpages/intrepid/man1/ccache.1.html

Ccache

There's a wonderful tool for gcc called ccache. You can read about it at their home page.

If you're always compiling the same programs over and over again — such as trying out several kernel patches, or testing your own development — then ccache is perfect. While it may take a few seconds longer to compile a program the first time with ccache, subsequent compiles will be much, much faster.

Now that we know what it is

HOW-TO-INSTALL

http://source.android.com/source/initializing.html

Setting up ccache

You can optionally tell the build to use the ccache compilation tool. Ccache acts as a compiler cache that can be used to speed-up rebuilds. This works very well if you do "make clean" often, or if you frequently switch between different build products.

Put the following in your .bashrc or equivalent.

export USE_CCACHE=1

By default the cache will be stored in ~/.ccache. If your home directory is on NFS or some other non-local filesystem, you will want to specify the directory in your .bashrc as well.

export CCACHE_DIR=<path-to-your-cache-directory>

example: export CCACHE_DIR=$HOME/.ccache

The suggested cache size is 50-100GB. You will need to run the following command once you have downloaded the source code:

prebuilts/misc/linux-x86/ccache/ccache -M 50G

When building Ice Cream Sandwich (4.0.x) or older, ccache is in a different location:

prebuilt/linux-x86/ccache/ccache -M 50G

This setting is stored in the CCACHE_DIR and is persistent. (pulled str8 from the link)

Now, we build (system being your work directory):

$ cd ~/android/system

To build for the ZTE Sequent:

$ . build/envsetup.sh && brunch warp2

All credit to PG for his readme file...Which he updated it recently, this is the old one ,I think...