After you have created your working build environment with java and build tools and such, and you are ready to work on the android source bit, do the following:
mkdir ~/cm-11.0 ....
I had created ~/Android/cm11.0-rezound
cd ~/cm-11.0 ......
cd'd into ~/Android/cm11.0-rezound Essentially the same thing.
now copy the contents located here:
https://raw.github.com/vigor/android....0/initrepo.sh
- - - copied from https://github.com/vigor/android/blo....0/initrepo.sh Which is identical to yours.
create a new document in your cm-11.0 directory called initrepo.sh using an editor to edit the file and paste the contents you copied into it. Save it and exit.
Well, it was created when it was copied.
now launch it: . inirepo.sh ---
We did.
Your repo sync will begin. What this does is set up your cm-11.0 source where, in the future, if you do a repo sync it will sync all android source from cm, and our device tree from our vigor git.
Now here is where we/I ran into probelms. Getting it straight on where and what to execute.
Once the repo sync has completed, do the following: ...
This took a coupe of hours
cd ~/cm-11.0/build ...
We/I did a cd into the build dir, but it was ~/Androd/cm11.0-rezound/build/ .. same thing
next we did a . build/envsetup.sh
git fetch
http://review.cyanogenmod.org/CyanogenMod/android_build refs/changes/59/53559/6 && git cherry-pick FETCH_HEAD
git fetch http://review.cyanogenmod.org/CyanogenMod/android_build refs/changes/59/53559/6 && git cherry-pick FETCH_HEAD --- same thing
hit enter and it will cherry-pick the build commit
Now here is the something that was missed. Knew there was something. Now then, I should be able to perform this 'fix' with the setup that I have... right??
cd ~/cm-11.0/frameworks/native/
git fetch
http://review.cyanogenmod.org/Cyanog...meworks_native refs/changes/62/53162/5 && git cherry-pick FETCH_HEAD
hit enter and it will cherry-pick the build commit
Here we should cd back into your ~/cm11.0 and my ~/Android/cm11.0-rezound before the next line. Right??
That's it. Now time brunch vigor and you are done!
The first cherry-pick is for Metadata, the second is to fix Print screen functionality
This is a much simpler way to do it.
Re: Re: CM-11.0 Compiled simple
And I really don't want to spend another 9+ hours doing it... for nothing. It was 2hrs + 7.72hrs. With the directory setup that I have created I should be able to move into the corresponding dirs and perform the 'fixes' -or- must we do a "repo sync" before doing the fixes and then the build?? This should be like any other 'C' project. 'make' will check the files and IF none have changed it won't recompile them. Since the cherrypicks are required -before- the 'build' then I am assuming that it is changing some -but- not all source files. So only those will need to be re-compiled and we won't have to wait another 7 hours plus or minus. Anyway, that is what we are gona try first and IF that fails we will once again wipe our environment and "FULLY" try what you just described.