Related
Compiling Gummy on Ubuntu 10.04
All work here is done from Ubuntu 10.04.. Newer releases may require slightly different packages.
Installing dependencies:
Install Ubuntu 10.04 and install all updates
Install Java SDK (type or copy the commands into the terminal exactly as you see them here )
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner”
Code:
sudo apt-get update
Code:
sudo apt-get install sun-java6-jdk
Install Git
Code:
sudo apt-get install git-core
Install the rest of the needed files
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 pngcrush
Setting up and syncing Gummy’s Repo
Enter the commands in the terminal exactly as they are displayed to setup your PATH
Code:
mkdir ~/bin
Code:
PATH=~/bin:$PATH
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Create your Gummy source directory and then go to that directory
Code:
mkdir ~/Gummy
Code:
cd ~/Gummy
Initialize and sync the Gummy repo (where X is put the number of cores for your CPU such as “repo sync -j4” for a quad core)
Code:
repo init -u https://github.com/teamgummy/platform_manifest.git -b master
Code:
repo sync -jX
Take a break and enjoy an ice cold beer
Go to the fridge
Pull out your favorite brand of beer
Open with care
Drink with pleasure
Otherwise its going to take a while ( a long while )
Preparing to Gummy and compiling
Get prebuilts (Term)
Code:
cd ~/Gummy/vendor/Gummy
Code:
./get-prebuilts
Code:
cd ~/Gummy
Compile (dont forget the . and also make sure you again change the X to the number of cores you have)
Code:
. build/envsetup.sh && lunch Gummy_toro-userdebug && make gummy -jX
_____________________________________________________________
Compiling Gummy on Ubuntu 11.10
Some of these instructions were taken directly from here..
First up:
Install Ubunutu 11.10 and install all the updates
Installing java:
Download the java JDK make sure you select accept the licence agreement and grab the jdk-6u30-linux-x64.bin
enter these commands exactly as they are listed
Code:
sudo chmod a+x ~/Downloads/jdk-6u30-linux-x64.bin
Code:
sudo cp ~/Downloads/jdk-6u30-linux-x64.bin /usr/lib
Code:
cd /usr/lib
Code:
sudo ./jdk-6u30-linux-x64.bin
Code:
sudo mv /usr/lib/jdk1.6.0_30/ /usr/lib/jvm/
Determine if any other JVMs are installed, and count how many, if any
Code:
sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_30/jre/bin/java 1
Code:
sudo update-alternatives --config java
Be sure to select /usr/lib/jvm/jdk1.6.0_30/jre/bin/java (number 2 in my build environment)
We need create symbolic links to a few Java binaries in /usr/bin
Code:
cd /usr/bin
Code:
sudo ln -s /usr/lib/jvm/jdk1.6.0_30/bin/javac
Code:
sudo ln -s /usr/lib/jvm/jdk1.6.0_30/bin/jar
Code:
sudo ln -s /usr/lib/jvm/jdk1.6.0_30/bin/javadoc
We need to ensure that the AOSP build process can locate the JDK, so we will set a variable it uses to locate the JDK.
Code:
nano ~/.bashrc
Add the following lines at the botton:
ANDROID_JAVA_HOME=/usr/lib/jvm/jdk1.6.0_30
export ANDROID_JAVA_HOME
pres CTRL + X then Y to save your changes
Installing dependencies:
Enter these commands exactly as they are listed
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 lib32readline-gplv2-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc pngcrush
Just to be sure reboot
Setting up and syncing Gummy’s Repo
Enter the commands in the terminal exactly as they are displayed to setup your PATH
Code:
mkdir ~/bin
Code:
PATH=~/bin:$PATH
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Create your Gummy source directory and then go to that directory
Code:
mkdir ~/Gummy
Code:
cd ~/Gummy
Initialize and sync the Gummy repo (where X is put the number of cores for your CPU such as “repo sync -j4” for a quad core)
Code:
repo init -u https://github.com/teamgummy/platform_manifest.git -b master
Code:
repo sync -jX
Take a break and enjoy an ice cold beer
Go to the fridge
Pull out your favorite brand of beer
Open with care
Drink with pleasure
Otherwise its going to take a while ( a long while )
Preparing to Gummy and compiling
Get prebuilts (Term)
Code:
cd ~/Gummy/vendor/Gummy
Code:
./get-prebuilts
Code:
cd ~/Gummy
Compile (dont forget the . and also make sure you again change the X to the number of cores you have)
Code:
. build/envsetup.sh && lunch Gummy_toro-userdebug && make gummy -jX
Thanks for the guide I will try to play with this
Sent from my Galaxy Nexus using xda premium
You realize steps 2.3, 3.1 and 4.1 can all be combined into one?
I have added the lucid partner repo, did apt-get update and the extra needed packages still don't want to install. It says they're missing. On Ubuntu 10.04 everything is updated.
donlad said:
I have added the lucid partner repo, did apt-get update and the extra needed packages still don't want to install. It says they're missing. On Ubuntu 10.04 everything is updated.
Click to expand...
Click to collapse
are you using 10.04 64 bit?? I know stupid questions but I need to ask.
kejar31 said:
are you using 10.04 64 bit?? I know stupid questions but I need to ask.
Click to expand...
Click to collapse
Nope I'm using 32-bit
Edit: I also checked in software sources to make sure the repo was added correctly and it was.
donlad said:
Nope I'm using 32-bit
Edit: I also checked in software sources to make sure the repo was added correctly and it was.
Click to expand...
Click to collapse
you will need to use 64 bit... Sorry I should have included that in the OP... Will update now.
To compile android on anything above 2.3 you need to compile it on a 64 bit OS
kejar31 said:
you will need to use 64 bit... Sorry I should have included that in the OP... Will update now.
To compile android on anything above 2.3 you need to compile it on a 64 bit OS
Click to expand...
Click to collapse
Well that's a bit of a letdown..because I went ahead and let it sync your repo last night. lol.
Oh well...
donlad said:
Nope I'm using 32-bit
Edit: I also checked in software sources to make sure the repo was added correctly and it was.
Click to expand...
Click to collapse
Ive heard that youll need a 64-bit to do this from TMartin...
Sent from my Galaxy Nexus
ok updated the original OP to include how to compile on Ubuntu 11.10..
As an fyi you should always use the 64bit version of Ubuntu
Overview
The following steps will help you to setup a complete build environment for the webos-ports project.
WE DO NOT CURRENTLY SUPPORT webos-image PLEASE BUILD webos-dev-image
Setup the build environment
Code:
$ sudo apt-get install gawk
$ sudo apt-get install diffstat
$ sudo apt-get install chrpath
$ sudo apt-get install texinfo (if not on Ubuntu or Debian it will be makinfo instead of texinfo)
$ cd into-your-build-directory
$ mkdir webos-ports && cd webos-ports
$ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh
$ sudo sh prerequisites.sh
$ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
$ make setup-webos-ports
Before you can build, you will need some tools. If you try to build without them, bitbake will fail a sanity check and tell you about what's missing, but not really how to get the missing pieces.
This has been tested on Gentoo (shr-chroot) and Ubuntu-12.04 amd64 and should work almost everywhere where valid toolchain is provided.
You need a lot of RAM to link webkit-webos, make sure you have at least 6GB (it's OK when some of that is swap, because it's used only for short part of build).
Webkit needs so much ram to link because it's linking with debug symbols (huge files) which are stripped later in do_package after creating -dbg packages.
You can add extra 2GB of swap file like this:
Code:
$ dd if=/dev/zero of=swap_2gb.img bs=1024k count=2048
$ mkswap swap_2gb.img
$ sudo swapon swap_2gb.img
If you want it permanently add it to your /etc/fstab.
Building
To configure to build for tuna (notice '.' which is actually bash 'source' command):
Code:
$ cd into-your-build-directory/webos-ports/webos-ports
$ . ./setup-env
To update metadata
Code:
$ make update
# or if it shows warning about different bblayers.conf or layers.txt
$ make update-conffiles && make update
# you can also add UPDATE_CONFFILES_ENABLED = 1 to config.mk
# if you never want to have any uncommited changes in your checkouts RESET_ENABLED = 1 in config.mk
To build the webos-image for the gnex device:
Code:
$ MACHINE=tuna bb webos-ports-image
# or for the webos development image
$ MACHINE=tuna bb webos-ports-dev-image
If you get an error about missing qmake-palm, try this:
Code:
$ MACHINE=tuna bitbake -c cleansstate -f qt4-webos
If you get an error about missing QtWebKit #261, try this:
Code:
$ MACHINE=tuna bitbake -c cleansstate -f webkit-webos
If you get an error "The BBPATH variable is not set", then you forgot to call:
Code:
$ . setup-env
After the build completes, you will find your image in <build env>/tmp-eglibc/deploy/images/tuna/
==Speeding up the build==
You can tune bitbake to use more of your processor. Edit webos-ports/conf/local.conf and uncomment the PARALLEL_MAKE and BB_NUMBER_THREADS lines. PARALLEL_MAKE should be set to the number of processor cores you have (or the number you have made available to the VM in the case of a VM) and BB_NUMBER_THREADS can be set from one to two times that, depending upon RAM, processor speed, other tasks running and Hyper-threading support. Example values:
Code:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"
I'm not in charge of this port. This thread is just here to help you, and discuss about this port made by team WEBOS-PORT.
Thanks for their work.
Installing and running the image
Once you have built the image, you'll likely want to install it and run it on your Nexus. See Testing Gnex for further details on that process.
Source and updates : http://webos-ports.org/wiki/Galaxy_Nexus_Build_Setup
Videos
Pictures
More Pictures : http://webos-ports.org/wiki/Galaxy_Nexus
Thanks for this, just having a go at this now
Edit: Damn it seems it doesn't like Ubuntu 10.10
Suppose I needed an excuse to update........
It would be pretty cool to have web os as a port for the Nexus. Wish you all the best
Sent from my Galaxy Nexus using Tapatalk 2
Nice, I hope webOS will be a succes on our Galaxy Nexuses!
Good luck!
nice work there ...
Really excited about this. Can't wait for a relatively stable port of the WebOS
So awesome, can't wait to see how this progresses.
Sent from my Galaxy Nexus using Tapatalk 2
The source was specified for Gnex, wasn't it?
Sent from my Galaxy Nexus using xda app-developers app
woot woot. niceeeee
Sound good....
Sent from my Galaxy Nexus using xda app-developers app
Awesome dude! Can't wait for a release. Hopefully in the future we can get this to dual boot with android, that would be awesome!
possibly to get instructions for toro?
waiting this on my gnex
New video added to post #2
exciiting stuff
Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.
#1 updated with Latest revision as of 23:58, 10 October 2012
sounds interesting.. cant wait for build that i can flash
Bread Pitta said:
Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.
Click to expand...
Click to collapse
Same here. Finally got it to build without errors, but no clue what to do next. My best Google sleuthing couldn't find any hints either
PecanCM ROM COMPILE GUIDE
Kindly post only something useful,do not spam.
Here is Quick Guide Setting Up Your Computer For Development Computer :
For Using Ubuntu 10.04 64 bit For Development Use this Link :
Download Ubuntu For Your Computer From here : http://releases.ubuntu.com/lucid/ubuntu-10.04.4-desktop-amd64.iso
Click to expand...
Click to collapse
For Using Ubuntu 10.10 64 Bit For Development Use this Link :
Download Ubuntu 10.10 For Your Computer From Here : http://releases.ubuntu.com/maverick/ubuntu-10.10-desktop-amd64.iso
Click to expand...
Click to collapse
For Using Ubuntu 11.04 64 Bit For Development Use this Link
Download Ubuntu 11.04 For Your Computer From Here : http://releases.ubuntu.com/natty/ubuntu-11.04-desktop-amd64.iso
Click to expand...
Click to collapse
For Using Ubuntu 11.10 64 Bit For Development Use this Link :
Download Ubuntu 11.10 For Your Computer From Here : http://releases.ubuntu.com/oneiric/ubuntu-11.10-desktop-amd64.iso
Click to expand...
Click to collapse
For Using Ubuntu 12.04 64 Bit For Development Use this Link :
Download Ubuntu 12.04 For Your Computer From Here : http://releases.ubuntu.com/precise/ubuntu-12.04-desktop-amd64.iso
Click to expand...
Click to collapse
For Using Ubuntu 12.10 64 Bit For Development Use this Link :
Download Ubuntu 12.10 For Your Computer From Here : http://releases.ubuntu.com/quantal/ubuntu-12.10-desktop-amd64.iso
Click to expand...
Click to collapse
UBUNTU 10.04 is Recommended for building! You can use other OS too!
I hope you all know how to install ubuntu! but still i'm giving you all what should your partitions like
HOME DRIVE : 30-50 GB or More
SWAP : It should be twice of your RAM if it is 2 GB than it should be 4 GB SWAP
SYSTEM [ FILE SYSTEM ] : 6 GB
Click to expand...
Click to collapse
Please try not to use WUBI
Setting up the COMPUTER for Android Development!
Configuring Your PC for Android Development
We will today install things JAVA 6 , Python , Make 3.81 and Dependencies used for compiling pecancm roms!
NOTE : TERMINAL MAY ASK YOU SEVERAL TIMES ABOUT YOUR SUDO PASSWORD
Python:
1. Type CTRL+ALT+T
2. Terminal will pop up
3. Apply the below given codes by copy/pasting
Code:
sudo apt-get install build-essential gcc
wget http://www.python.org/ftp/python/2.5.6/Python-2.5.6.tgz
tar -xvzf Python-2.5.6.tgz
cd Python-2.5.6
./configure --prefix=/usr/local/python2.5
make
sudo make install
sudo ln -s /usr/local/python2.5/bin/python /usr/bin/python2.5
4. Python is Installed
Click to expand...
Click to collapse
JAVA:
See There are Several different ways of installing JAVA!
If you are using Ubuntu 10.04 , 10.10 , 11.04 and 11.10
Follow these commands!
1. Open Terminal [ CTRL+ALT+T ]
2. Copy/Paste below given commands
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
java --version
3. If this all goes all right! JAVA is installed
If you are using Ubuntu 12.04 , 12.10.
Follow these commands
1. Open Browser
2. Download JDK 6 From here
3. Accept the Terms and conditions
4. Download jdk-6u38-linux-x64.bin
5. Open Terminal [ CTRL+ALT+T]
6. Copy/Paste below given commands
Code:
cd ~/Downloads
chmod +x jdk-6u38-linux-x64.bin
sudo ./jdk-6u38-linux-x64.bin
sudo mv jdk1.6.0_38 /usr/lib/jvm/
sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_38/bin/java 1
sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_38/bin/javac 1
sudo update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk1.6.0_38/bin/javaws 1
sudo update-alternatives --install /usr/bin/jar jar /usr/lib/jvm/jdk1.6.0_38/bin/jar 1
sudo update-alternatives --install /usr/bin/javadoc javadoc /usr/lib/jvm/jdk1.6.0_38/bin/javadoc 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws
sudo update-alternatives --config jar
sudo update-alternatives --config javadoc
7. Now your Java should be installed
To verify installation of java:
Code:
java -version
Output should be
Code:
java version "1.6.0_38"
Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
Click to expand...
Click to collapse
GNU MAKE 3.81
1. Open Terminal [ CTRL+ALT+T]
2. Copy/Paste the below commands
Code:
wget http://ftp.gnu.org/gnu/make/make-3.81.tar.gz
tar -xvzf make-3.81.tar.gz
cd make-3.81
./configure
make
sudo make install
3. GNU Make is installed
Click to expand...
Click to collapse
DEPENDENCIES:
1. Open Terminal [ CTRL+ALT+T]
2. Now Apply the below commands on all ubuntu versions:
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 lib32readline-gplv2-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc gedit git schedtool
3. Now Apply the below command too if you are using ubuntu 10.10
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
4. Now Apply the below command too if you are using ubuntu 11.04
Code:
sudo apt-get install libx11-dev:i386
5. Now Apply the below commands too if you are using ubuntu 12.04 and Ubuntu 12.10
Code:
sudo apt-get install libncurses5-dev:i386 libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 zlib1g-dev:i386
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
6. Now you are finished! configuring dependencies!
Click to expand...
Click to collapse
ADB & FASTBOOT:
1. Open terminal [CTRL+ALT+T]
2. Copy/Paste Below commands
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
3. Now your ADB and Fastboot is Installed
4. Now we need to configure udev rules
Code:
sudo -i
echo "SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"" >> /etc/udev/rules.d/51-android.rules
echo "SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"" >> /etc/udev/rules.d/99-android.rules
exit
sudo chmod a+r /etc/udev/rules.d/99-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo adb kill-server
sudo adb start-server
5. Now connect your LG P350, ensure that USB Debugging is enabled!
6. Type following commands on terminal
Code:
adb devices
7. If it shows output like below:
Code:
List of devices attached 0123456789ABCDEF device (SIMILAR TO THIS )
8. Now your ADB is installed and configured
Click to expand...
Click to collapse
REPO:
1. Open Terminal [CTRL+ALT+T]
2. Copy/Paste below given commands
Code:
sudo -i
cd /bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > /bin/repo
chmod a+x /bin/repo
exit
Click to expand...
Click to collapse
Now, Development COMPUTER is Ready to Start Syncing ANDROID SOURCES and Compile them!:victory:
Syncing and Building ICS Source Code
Syncing & Building PecanCM ICS Source Code
Syncing the PecanCM ICS Source Code
1. Open Terminal [CTRL+ALT+T]
2. Copy/Paste below given commands
Code:
mkdir pecancm_ics
cd pecancm_ics
repo init -u git://github.com/PecanCM/android.git -b ics
repo sync -j8
3. It will take few hours according to your internet connection! It is of several gb's!
Click to expand...
Click to collapse
Building the PecanCM ICS Source Code
1. Open Terminal [CTRL+ALT+T]
2. Copy/Paste below given commands
Code:
cd pecancm_ics
cd vendor/cm
./get-prebuilts
cd ../..
. build/envsetup.sh && brunch p350
3. Now Build should be started!
4. It will take few hours or even minutes according to your computer hardware!
5. When build is done it will give you ZIP of your ROM check the terminal output! at the end path of the ZIP should be given
6. Enjoy your Own PecanCM ICS Which is build by your own
Click to expand...
Click to collapse
Syncing and Building Jellybean Source Code
Syncing & Building PecanCM Jellybean Source Code
Syncing the PecanCM Jellybean Source Code
1. Open Terminal [CTRL+ALT+T]
2. Copy/Paste below given commands
Code:
mkdir pecancm_jellybean
cd pecancm_jellybean
repo init -u git://github.com/PecanCM/android.git -b jellybean
repo sync -j8
3. It will take few hours according to your internet connection! It is of several gb's!
Click to expand...
Click to collapse
Building the PecanCM Jellybean Source Code
1. Open Terminal [CTRL+ALT+T]
2. Copy/Paste below given commands
Code:
cd pecancm_jellybean
cd vendor/cm
./get-prebuilts
cd ../..
. build/envsetup.sh && brunch p350
3. Now Build should be started!
4. It will take few hours or even minutes according to your computer hardware!
5. When build is done it will give you ZIP of your ROM check the terminal output! at the end path of the ZIP should be given
6. Enjoy your Own PecanCM Jellybean Which is build by your own
Click to expand...
Click to collapse
Syncing and Building Jellybean4.2 Source Code
Syncing & Building PecanCM Jellybean4.2 Source Code
Syncing the PecanCM Jellybean4.2 Source Code
1. Open Terminal [CTRL+ALT+T]
2. Copy/Paste below given commands
Code:
mkdir pecancm_jb4.2
cd pecancm_jb4.2
repo init -u git://github.com/PecanCM/android.git -b cm-10.1
repo sync -j8
3. It will take few hours according to your internet connection! It is of several gb's!
Click to expand...
Click to collapse
Building the PecanCM Jellybean4.2 Source Code
1. Open Terminal [CTRL+T]
2. Copy/Paste below given commands
Code:
cd pecancm_jb4.2
cd vendor/cm
./get-prebuilts
cd ../..
. build/envsetup.sh && brunch p350
3. Now Build should be started!
4. It will take few hours or even minutes according to your computer hardware!
5. When build is done it will give you ZIP of your ROM check the terminal output! at the end path of the ZIP should be given
6. Enjoy your Own PecanCM Jellybean4.2 Which is build by your own
Click to expand...
Click to collapse
Disclaimer
Disclaimer:
THINGS YOU SHOULD KNOW BEFORE RELEASING YOUR COMPILED PECANCM ROM
1. Remember if you are going to release your build, Please Add " [KANG] " TAG at your title of the thread
2. Please Give Credits to Whole PecanCM TEAM i.e kD , RonG , antdking and osamabinary
Pushing your patches to Gerrit
Pushing your patches to PecanCM Gerrit
If you have any patches or fixes to source codes you could surely send it to PecanCM Gerrit and We will Review it and Maybe we get you in the Team!
So Question Must Arise in your Mind! How to Push Patches?? !! Well So I'm Writing Small Guide Here For Pushing Patches to PecanCM Gerrit!
First of All I would like to tell you ! you must have bit knowledge about git
Now Let's Start!
First of all go to PecanCM Gerrit and on the top you could see register! You can Register via Google Account , Yahoo Account and OpenID! So Now Register your account!
Now You Need to Give your SSH Public Key to Gerrit for Authenication. First of all you need to generate SSH Keys If you haven't done it so far!
For Generating your SSH Keys Follow This Command in your Shells [ Terminals ]
ssh-keygen -t rsa -C "[email protected]"
Here you need to change your email with the email id your registered with
Click to expand...
Click to collapse
Now Just Press Enter Follow the Process Now you will get your id_rsa.pub file in your ~/.ssh/id_rsa.pub ! [ It May Change if you didn't go to normal process ]
Now Open your ~/.ssh/id_rsa.pub and Copy the Whole text
Now Open PecanCM Gerrit and Login and Now Go to Settings > SSH Public Keys > Add Keys
Now Paste your Whole Text here! and Save it
Now You Must be Authenicated !
Now You Can Push to any PecanCM Repo like
First do your commits.
Now Time to Push your Commits for Review
git push ssh://[email protected]:6117/PecanCM/reponame HEAD:refs/for/branch [ branch = name of branch ]
Now it should be pushed! and you should be given link to review on terminal!
Well Maybe You Should Find my Guide Tough lol You Could also See Better Guide Here http://review.pecancm.org/Documentation/user-upload.html
I hope you guys enjoyed my guide and it was easy! forgive me if i had any grammer mistakes! I'm not Native english man! I've tried to make the guide as much easy as possible! but still bit using of mind is needed! you need to bear with it
Love you all!
Great Dude
yajnab said:
Great Dude
Click to expand...
Click to collapse
thanku
Very helpful guide. Thank you so much
Sent from my LG-P350 using xda app-developers app
tydell said:
Very helpful guide. Thank you so much
Sent from my LG-P350 using xda app-developers app
Click to expand...
Click to collapse
I'm glad you find it useful
Great guide dude!
Just 2 questions;
Syncing the PecanCM Jellybean4.2 Source Code
1. Open Terminal [CTRL+T]
2. Copy/Paste below given commands
Code:
mkdir pecancm_jb4.2
cd pecancm_jb4.2
repo init -u git://github.com/PecanCM/android.git -b cm-10.1
repo sync -j8
3. It will take few hours according to your internet connection! It is of several gb's!
Click to expand...
Click to collapse
How many gb's are? Cause my connection is too slow and i wanna know how many time will take. And if can i translate your guide and post it in other comunity, i'll give you the credits i just wanna translate it
Thanks you in advance..
DiegoConD said:
Great guide dude!
Just 2 questions;
How many gb's are? Cause my connection is too slow and i wanna know how many time will take. And if can i translate your guide and post it in other comunity, i'll give you the credits i just wanna translate it
Thanks you in advance..
Click to expand...
Click to collapse
It is around 8-9 gb ! and have a go in translating my guide but just give link to my guide and give credits
Hi! Thanks a lot for your guide, finally It's worked for me!
About syncing is all perfect (in both cm9 and cm10.1), and compiling, only in cm10.1 . In ICS, i'm having the next trouble:
[email protected]:~$ cd pecancm_ics
[email protected]:~/pecancm_ics$ . build/envsetup.sh && brunch p350
bash: [: =~: se esperaba un operador binario
including device/htc/runnymede/vendorsetup.sh
including device/lge/p350/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
device/lge/p350/p350.mk:1: *** falta un separador. Alto.
Device p350 not found. Attempting to retrieve device repository from PecanCM Github (http://github.com/PecanCM).
Found repository: android_device_lge_p350
PecanCM/android_device_lge_p350 already exists
Syncing repository to retrieve project.
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
device/lge/p350/p350.mk:1: *** falta un separador. Alto.
** Don't have a product spec for: 'cm_p350'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
[email protected]:~/pecancm_ics$
Click to expand...
Click to collapse
Any ideas? Thanks for your time
yaymalaga said:
Hi! Thanks a lot for your guide, finally It's worked for me!
About syncing is all perfect (in both cm9 and cm10.1), and compiling, only in cm10.1 . In ICS, i'm having the next trouble:
Any ideas? Thanks for your time
Click to expand...
Click to collapse
It seems Anthony removed cm.dependencies so you are getting the issue! Im having my exams going on i will back after 9th april! Ask Anthony to fix it up! He will do it
Sent from my LG-P350 using xda premium
KD, cm.dependencies wasn't the problem, it was p350.mk (The trouble was in the first line,"# Inherit from those products. Most specific first" so I deleted and now It's fine),but now my problem it's about the kernel (Maybe by the change to 3.0). Do you know hot to solve?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for your time!
Anyway, The problem was that I hadn't p350's 3.0 kernel
missing file
Hi
when i try to compile latest cm 10.1 i got an error - libC2D2.so isn't in place.
File is missing after repo sync -j8, it is also missing in github i've checked already.
*** No rule to make target `vendor/lge/p350/proprietary/lib/libC2D2.so', needed by `/Volumes/android/cm10.1/out/target/product/p350/system/lib/libC2D2.so'. Stop.
make: *** Waiting for unfinished jobs....
Thanks
bjcb said:
Hi
when i try to compile latest cm 10.1 i got an error - libC2D2.so isn't in place.
File is missing after repo sync -j8, it is also missing in github i've checked already.
*** No rule to make target `vendor/lge/p350/proprietary/lib/libC2D2.so', needed by `/Volumes/android/cm10.1/out/target/product/p350/system/lib/libC2D2.so'. Stop.
make: *** Waiting for unfinished jobs....
Thanks
Click to expand...
Click to collapse
Fixed
...
PecanCM said:
Fixed
Click to expand...
Click to collapse
Ron Can help here ?
http://forum.xda-developers.com/showthread.php?t=2296505
Hello guys since there is no Cyanogenmod for this device only an custom recovery (no custom roms) or any really development except for stripping stockrom and tweaking it a bit i decided to make it for an friend and since 3 people of my class have this phone i am founding it pretty an unstable phone with all the stock crap bloatware.
I could make my friends phone hang with whatsapp spamming messages what is pretty pathetic.
So i contacted Corsicanu for the sourcecode of recovery what is an very important piece of the source code for not to brick you people´s phone and i also received some in/complete source code from adytzu33. I am trying to make the compiling work i am almost done with making it to completely work but i don´t have always time so if you can fix everything by yourself do it and upload it to here so i can adjust the guide for future developers for the fame. Watchout cause this sourcecode is for the galaxy fame p s6810p so far as i know.
If my tutorial broke yourphone from flashing an build then its not my fault
Check good or the partitions are good before flashing. Since i dont have the phone i cant test it.
Preparation:
What you need for building.
An decent PC with enough space i recommend like 80gb
Internet connection
Time and Patience
Up to date running Ubuntu/linux system i am using 14.04
IMPORTANT: INSTALL EVERYTHING AS A NORMAL USER. DON'T INSTALL AS ROOT!
Installation of the required packages to compile:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils schedtool pngcrush xsltproc zlib1g-dev:i386
Settings the links to the files:
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Step 2 Installing java:
You need the java development kit for building cm10 the most recommended is the one from sun jdk 6 update 38.
1. Download the jdk-6u38-linux-i586.bin from the Oracle/Sun Java Download Area. If you are on 64-bit Ubuntu as I am, you should grab jdk-6u38-linux-x64.bin
http://www.mediafire.com/download/wyb4xmxbsb7pabm/jdk-6u38-linux-x64.bin (mirror for 64bit)
2. Go to your Download location and execute this command below.
Code:
chmod +x jdk-6u38-linux-x64.bin
3. Extract the bin file:
Code:
$ ./jdk-6u38-linux-x64.bin
4. Move the extracted folder to this this location:
Code:
$ sudo mv jdk1.6.0_38 /usr/lib/jvm/./jdk-6u38-linux-x64.bin
5. Install the new Java source in system:
Code:
$ sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/javac 1
$ sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/java 1
$ sudo update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/javaws 1
$ sudo update-alternatives --install /usr/bin/javadoc javadoc /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/javadoc 1
$ sudo update-alternatives --install /usr/bin/javah javah /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/javah 1
$ sudo update-alternatives --install /usr/bin/javap javap /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/javap 1
$ sudo update-alternatives --install /usr/bin/jar jar /usr/lib/jvm/jdk-6u38-linux-x64.bin/bin/jar 1
6. Select the default Java version for your system:
Code:
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javaws
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config javah
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config jar
7. Check Java version:
Code:
$ java -version
8. Verify the symlinks. Javac, Java, Javaws, Javadoc, Javah, Javap and Jar should all point to the new Java location and version:
Code:
$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar
Step 3: The sources
Install repo:
Repo is a tool that makes it quite easy to download and maintain the sources of Cyanogenmod.
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl [url]https://dl-ssl.google.com/dl/googlesource/git-repo/repo[/url] > ~/bin/repo
$ chmod a+x ~/bin/repo
Create working directory:
Code:
$ mkdir ~/cm10
$ cd ~/cm10
Initialize Repo:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b jellybean
and enter your credentials.
Download the sources:
Code:
$ repo sync
Wait until it's finished (takes a lot of time! depending on your internet connection)
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
Tip from ethansp: If you are running into a lot of syncing errors the reason might be that the 'repo sync' command is establishing four threads automatically. This might be too much. So try to change the command to run with one thread only by using
Code:
$ repo sync -j1
Initialize the environment
Code:
$ . build/envsetup.sh
Go to your Cm10 Repository folder and press CTRL+H
Go to .Repo/local_manifests and create local_manifest.xml
Paste these lines into it and repo sync after it again.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="wulsic/android_device_samsung_nevisp.git" path="device/samsung/nevisp" remote="github" revision="master"/>
<project name="wulsic/android_vendor_samsung_nevisp.git" path="vendor/samsung/nevisp" remote="github" revision="master"/>
<project name="corsicanu/android_kernel_samsung_nevisp.git" path="kernel/samsung/nevisp" remote="github" revision="master"/>
<project name="wulsic/android_frameworks.git" path="framework/" remote="github" revision="master"/>
</manifest>
Download the neccesary Cyanogenmod prebuilts:
Code:
~/cm10/vendor/cm/get-prebuilts
Step4: Building the rom
Now try to build it.
Code:
Brunch nevisp
And now the building process starts. Building takes from an half hour( very fast pc) to 2 hour on very slow pc´s maybe even more.
When everything gone fine (Can´t the guide is not finished there are still some little errors in compiling i need to fix or maybe you dev´s.) you can find the flashable zip in ~/cm10/out/target/product/nevisp
It would be called cm-10-DATE-UNOFFICIAL-nevisp-zip. You can directly flash it cause it is already an flashable zip.
Step5:Rebuilding with newest sources:
Code:
$ cd ~/cm10
$ repo sync
$ . build/envsetup.sh
$ brunch nevisp
The building should now take a lot less time cause it only rebuilds it and its using old parts what haven´t changed.
For more Handy tips see this link where i based the guide off http://forum.xda-developers.com/showthread.php?t=1971645
Credits:All credits goes to Raum1807 for making the guide i only edit it for people so its easier for compiling for the fame.
And to corsicanu for giving me the sourcecode from adytzu33t and the cm10.1 recovery what could be also handy for beginning cm10.1 but first cm10 and also for his uploaded kernel sourcecode on github.
and adytzu33 for the sourcecode from cm10 but unfortunatly he was last online in march.
If you have problems then post it here in the thread i can help you to get compiling so far as i am since i now have the knowledge again for cm10 and you guys can help me.
If you have the same error like me here what i will solve today after like 12hours when i standup again then you have the same progress like me.
Going to sleep now just bring the old devs back to life on this forum cause its almost completely death if you ask me.
Reserved for Progress:
Code:
target Strip: libvariablespeed (/home/wulsic/cm10/out/target/product/nevisp/obj/lib/libvariablespeed.so)
Install: /home/wulsic/cm10/out/target/product/nevisp/system/lib/libvariablespeed.so
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::EmitFunctionHeader():external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:477: error: undefined reference to 'llvm::DwarfDebug::beginFunction(llvm::MachineFunction const*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::EmitFunctionBody():external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:685: error: undefined reference to 'llvm::DwarfDebug::beginInstruction(llvm::MachineInstr const*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::EmitFunctionBody():external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:727: error: undefined reference to 'llvm::DwarfDebug::endInstruction(llvm::MachineInstr const*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::EmitFunctionBody():external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:788: error: undefined reference to 'llvm::DwarfDebug::endFunction(llvm::MachineFunction const*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::doFinalization(llvm::Module&):external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:895: error: undefined reference to 'llvm::DwarfDebug::endModule()'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::doFinalization(llvm::Module&):external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:897: error: undefined reference to 'llvm::DwarfDebug::~DwarfDebug()'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::doInitialization(llvm::Module&):external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:205: error: undefined reference to 'llvm::ARMException::ARMException(llvm::AsmPrinter*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::doInitialization(llvm::Module&):external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:208: error: undefined reference to 'llvm::Win64Exception::Win64Exception(llvm::AsmPrinter*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::doInitialization(llvm::Module&):external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:202: error: undefined reference to 'llvm::DwarfCFIException::DwarfCFIException(llvm::AsmPrinter*)'
/home/wulsic/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/wulsic/cm10/out/target/product/nevisp/obj/STATIC_LIBRARIES/libLLVMAsmPrinter_intermediates/libLLVMAsmPrinter.a(AsmPrinter.o): in function llvm::AsmPrinter::doInitialization(llvm::Module&):external/llvm/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:195: error: undefined reference to 'llvm::DwarfDebug::DwarfDebug(llvm::AsmPrinter*, llvm::Module*)'
collect2: ld returned 1 exit status
make: *** [/home/wulsic/cm10/out/target/product/nevisp/obj/SHARED_LIBRARIES/libbcc_intermediates/LINKED/libbcc.so] Error 1
make: *** Waiting for unfinished jobs....
Thanks for give us guide, I want to try
After I download ubuntu
Sent from my GT-S6810 using XDA Premium 4 mobile app
EDIT:
Compiling problems fixed thanks to corsicanu, he fixed the boardconfig.mk and the recovery.fstab so without him i would still be figuring out what to edit by those files.
Now we only need testers to log the problems from boot so we can fix those problems.
Here is staying the compiling guide and it will stay in update with the repository so i will push fixes to the repo and merge fixes from people who review the sourcecode.
I will create a new thread in the Original android development thread since its not modified stock but it will be the first cyanogenmod 10 for the fame.
The build wasn´t really on time it was 18 minutes later posted then i said i would make it but that doesn´t matter i think.
Development Thread:
http://forum.xda-developers.com/showthread.php?p=52756482
I can compile and install on my GT-6810B?
I am Brazilian and I'm using Google Translator
Well you can compile it but i am still finding out or everything is compatible with each other so i mean all the fame phones since i do not own it and i still need to dig In the specifications and threads here i cant promise anything. We are still trying to make logcat work on the s6810/p so i just want to say that its better that you will first wait till we have hammered out all the problems. Else you might be able to compile it but it wil not boot. Hold an Eye on the thread mentioned above for progressieve.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
Thanks, I think it best to wait
John Blueh said:
Thanks, I think it best to wait
Click to expand...
Click to collapse
Maybe you can help him on this thread http://forum.xda-developers.com/showthread.php?t=2755948
Sent from my GT-S6810 using XDA Premium 4 mobile app
Thanks [emoji4]
Отправлено с моего GT-S6810 через Tapatalk
Misha_android if you got problems with compiling just post it here or send a message tot me.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
CM11 coming soon.
Hello guys,
I really want to build cm10 but i can't test it because i have this phone but i really DON'T want to root it, i can fix some errors by myself because when building pac 4.4.4 for my device i was getting TONS of errors so i start building today.
EDIT: I looked at the local_manifest.xml but i don't see any line that points to the kernel,device and vendor tree.
I can't say that im right because the repo sync is still in progress but i only thnk
Sorry for bad english
EDIT 2: I see nobody has started building cm11 for this device.. i can start doing it but i need the device,vendor and kernel source if anyone has a link please give it.
Hello guys, since I don't have the time of the world to finish easily the cm11 project because of school I am posting here the updated guide to compile CM11 so Fame Dev's could like finish the project and make an fully working cyanogenmod :good:
Overview
I. Preparation
II. Installation of the required packages
III. Installing Java
IV. The sources
V. Building the ROM
VI. Rebuilding with newest sources
VII. Galaxy Fame Build menu
I. Preparation
Things you need for building:
A computer
An internet connection
An open mind
Time
Patience
First of all, you need a running up-to-date Ubuntu/Linux system. I am using Ubuntu 14.04 64-bit.
Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.
IMPORTANT: INSTALL EVERYTHING AS A NORMAL USER. DON'T INSTALL AS ROOT!
II. Installation of the required packages (Ubuntu 13.10 64-bit)
Install packages:
Code:
$ sudo apt-get install bison build-essential curl flex \
g++-multilib gcc-multilib git-core gnupg gperf \
lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev \
libesd0-dev libncurses5-dev libsdl1.2-dev \
libwxgtk2.8-dev libxml2 libxml2-utils lzop \
openjdk-6-jdk openjdk-6-jre pngcrush schedtool \
squashfs-tools xsltproc zip zlib1g-dev
III. Installing Java
[/FONT]
You need a version 6 Java Development Kit for building CM11.0. Usually, the SUN JDK 6 is recommended. But there is another way: you can use the OpenJDK 6. When you installed the required packages as described above, you will just need to configure your Java installation.
Check your Java version:
Code:
$ java -version
Verify the symlinks. Javac, Java, Javaws, Javadoc, Javah, Javap and Jar should all point to the right Java location and version:
Code:
$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar
If they are pointing to the wrong versions you have to change that to OpenJDK6.
Select the default Java version for your system:
Code:
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javaws
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config javah
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config jar
That's it.
IV. The sources
Install repo:
Repo is a tool that makes it quite easy to download and maintain the sources of Cyanogenmod.
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Create the working directory:
Code:
$ mkdir ~/cm11
$ cd ~/cm11
Initialize Repo:
Code:
$ repo init -u http://github.com/CyanogenMod/android.git -b cm-11.0
and enter your credentials.
Download the sources:
Code:
$ repo sync
Wait until it's finished - takes some time to download the hefty 15-35 GB of source code!
Have a break, have a KitKat!
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
If you are running into a lot of syncing errors the reason might be that the 'repo sync' command is establishing four threads automatically. This might be too much. So try to change the command to run with one thread only by using
Code:
$ repo sync -j1
Initialize the environment
Code:
$ . build/envsetup.sh
Obtain the proprietary files:
create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml
Paste the following lines to the editor
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="wulsic/android_device_samsung_nevisp.git" path="device/samsung/nevisp" remote="github" revision="cm-11.0"/>
<project name="wulsic/android_vendor_samsung_nevisp.git" path="vendor/samsung/nevisp" remote="github" revision="master"/>
<project name="wulsic/android_kernel_samsung_nevispcm11.git" path="kernel/samsung/nevisp" remote="github" revision="master"/>
<project name="wulsic/android_patchesnevisp.git" path="patches" remote="github" revision="cm-11.0"/>
</manifest>
Save the file.
Run
Code:
$ repo sync
again to get the files needed.
Download the necessary prebuilts from cyanogenmod by running
Code:
$ cd ~/cm11/vendor/cm
$ . get-prebuilts
$ croot
And you're done!
V. Building the ROM
Now build it:
Code:
$ brunch nevisp
And the building process starts. Now have patience. Building takes around half an hour on fast systems and a lot more on older and slower machines.
When everything worked as it should you will find your new ROM-image in ~/cm11/out/target/product/nevisp
It is called cm-11-DATE-NIGHTLY-nevisp-zip. You can flash it via CWM
VI. Rebuilding with newest sources
Whenever you like to update your sources and build a new version you have to run these four simple commands:
Code:
$ cd ~/cm11
$ repo sync
$ . build/envsetup.sh
$ brunch nevisp
Compiling takes less time than it took for creating the ROM the first time because it's only building new parts while reusing old parts that haven't changed.
VII. Galaxy Fame Build menu
Now that you know how building works but for full functionality on the fame we also need to apply patches. We are going to do this using a simple menu I made to spare time and mistakes.
https://github.com/wulsic/Personalscripstrepository/blob/master/build-nevisp_simple.sh
Open the link and Right click on the raw button and
Save the file in your CM11 directory and rename it to build-nevisp.sh or whatever name is easier/better for you as it doesn't matter.
You can execute this menu by making it executable by going to properties, permissions and allow executing file as program.
or you can open a terminal in the CM11 root folder and execute it by typing:
Code:
. build-nevisp.sh
Usefull addon if you have ubuntu so you can Open terminal in every folder by only right clicking in the folder and selecting open terminal. To get it you have to install it with:
Code:
sudo apt-get install nautilus-open-terminal
Happy building![/QUOTE]
Big thanks to Raum1807 Since this is his guide but modified for the Fame Dev's/People to keep it easier. I had his permission for this.
Stop by his thread and thank him for his guide:good: http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Thanks to Google for android and Cyanogenmod well for Cyanogenmod ofcourse ;p
Reserved:
You can flash the cm11 builds by flashing the Selinux enabled Clockworkmod recovery:https://drive.google.com/file/d/0B1u3mnq0nstfWFd5eGVlbHNkaTg/edit?usp=sharing
Or compile a new clockworkmod recovery by yourself since you are already compiling android :good: but I believe this is already automatically done.
Does it work on S6810B?
Sorry my english, I'm Brazilian and do not speak well in English.
by: Google Translate
John Blueh said:
Does it work on S6810B?
Sorry my english, I'm Brazilian and do not speak well in English.
by: Google Translate
Click to expand...
Click to collapse
try it,,yyou just need to change the repo
John Blueh said:
Does it work on S6810B?
Sorry my english, I'm Brazilian and do not speak well in English.
by: Google Translate
Click to expand...
Click to collapse
John blueh I am not sure, the S6810B is dualsim model right? The only thing you have to change then is maybe device model and somethings in the ramdisk related to the device model.
But I could not make cm11 boot yet, probably an ramdisk issue since I am doing it blindly its going harder especially with school.
I hope you could maybe also invest your time in it a bit and make an fully working cm11 only problems so far are related to the kernels ramdisk so far as I know.
I hope google translates this good for you.
i got problem :/ ,,see below
wulsic said:
Hello guys, since I don't have the time of the world to finish easily the cm11 project because of school I am posting here the updated guide to compile CM11 so Fame Dev's could like finish the project and make an fully working cyanogenmod :good:
Overview
I. Preparation
II. Installation of the required packages
III. Installing Java
IV. The sources
V. Building the ROM
VI. Rebuilding with newest sources
I. Preparation
Things you need for building:
A computer
An internet connection
An open mind
Time
Patience
First of all, you need a running up-to-date Ubuntu/Linux system. I am using Ubuntu 14.04 64-bit.
Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.
IMPORTANT: INSTALL EVERYTHING AS A NORMAL USER. DON'T INSTALL AS ROOT!
II. Installation of the required packages (Ubuntu 13.10 64-bit)
Install packages:
Code:
$ sudo apt-get install bison build-essential curl flex \
g++-multilib gcc-multilib git-core gnupg gperf \
lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev \
libesd0-dev libncurses5-dev libsdl1.2-dev \
libwxgtk2.8-dev libxml2 libxml2-utils lzop \
openjdk-6-jdk openjdk-6-jre pngcrush schedtool \
squashfs-tools xsltproc zip zlib1g-dev
III. Installing Java
[/FONT]
You need a version 6 Java Development Kit for building CM11.0. Usually, the SUN JDK 6 is recommended. But there is another way: you can use the OpenJDK 6. When you installed the required packages as described above, you will just need to configure your Java installation.
Check your Java version:
Code:
$ java -version
Verify the symlinks. Javac, Java, Javaws, Javadoc, Javah, Javap and Jar should all point to the right Java location and version:
Code:
$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar
If they are pointing to the wrong versions you have to change that to OpenJDK6.
Select the default Java version for your system:
Code:
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javaws
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config javah
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config jar
That's it.
IV. The sources
Install repo:
Repo is a tool that makes it quite easy to download and maintain the sources of Cyanogenmod.
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Create the working directory:
Code:
$ mkdir ~/cm11
$ cd ~/cm11
Initialize Repo:
Code:
$ repo init -u http://github.com/CyanogenMod/android.git -b cm-11.0
and enter your credentials.
Download the sources:
Code:
$ repo sync
Wait until it's finished - takes some time to download the hefty 15-35 GB of source code!
Have a break, have a KitKat!
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
If you are running into a lot of syncing errors the reason might be that the 'repo sync' command is establishing four threads automatically. This might be too much. So try to change the command to run with one thread only by using
Code:
$ repo sync -j1
Initialize the environment
Code:
$ . build/envsetup.sh
Obtain the proprietary files:
create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml
Paste the following lines to the editor
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="wulsic/android_device_samsung_nevispcm11.git" path="device/samsung/nevisp" remote="github" revision="master"/>
<project name="wulsic/android_vendor_samsung_nevispcm11.git" path="vendor/samsung/nevisp" remote="github" revision="master"/>
<project name="wulsic/android_kernel_samsung_nevispcm11.git" path="kernel/samsung/nevisp" remote="github" revision="master"/>
</manifest>
Save the file. (Replace the device revision with Testing if you want to get my Testing branch.)
Run
Code:
$ repo sync
again to get the files needed.
Download the necessary prebuilts from cyanogenmod by running
Code:
$ cd ~/cm11/vendor/cm
$ . get-prebuilts
$ croot
And you're done!
V. Building the ROM
Now build it:
Code:
$ brunch nevisp
And the building process starts. Now have patience. Building takes around half an hour on fast systems and a lot more on older and slower machines.
When everything worked as it should you will find your new ROM-image in ~/cm11/out/target/product/nevisp
It is called cm-11-DATE-UNOFFICIAL-nevisp-zip. You can flash it via CWM
VI. Rebuilding with newest sources
Whenever you like to update your sources and build a new version you have to run these four simple commands:
Code:
$ cd ~/cm11
$ repo sync
$ . build/envsetup.sh
$ brunch nevisp
Compiling takes less time than it took for creating the ROM the first time because it's only building new parts while reusing old parts that haven't changed.
Happy building!
Click to expand...
Click to collapse
Big thanks to Raum1807 Since this is his guide but modified for the Fame Dev's/People to keep it easier. I had his permission for this.
Stop by his thread and thank him for his guide:good: http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Thanks to Google for android and Cyanogenmod well for Cyanogenmod ofcourse ;p
I hope this Guide is good since I screwed up my ubuntu again... Please report to me if there is a mistake in the OP.[/QUOTE]
If By Chance I Took Build On A Virtual Machine ... Would Take To Build It?
PS :. I am Brazilian, translated to English by Google Translate.
@NickyClouD this guide is good but you have to replace the master revision by device_samsung_nevispcm11 to Testing.
I dont know were you screwed it up but this guide is good
I dont know howlong it would take to build it since I am triplebooting.
So change master to Testing. Goodluck :good:
EDIT: Could you also unquote the OP please since it takes alot of space
For the one who cares about building roms for the fame community I adjusted the guide a bit again and added the repository with all the patches needed for the fame to the local_manifest.xml part.
I also added a new part to the guide called:
VII. Galaxy Fame Build menu
It includes a link to a simple build script which I made so that you compilers can compile/update/clean your builds easier without the need of wasting more time then needed and it also includes a feature so you can see how long the build went or how long repo sync took.
Also an addon/package for ubuntu variants which allows you to open the terminal in the folder by only right clicking in the folder and selecting open terminal menu. This addon spares you ALOT of time when you are busy with these kinds of things.