Keep in mind when you read this that I am a complete noob at building android in general, I just can't wait to use this rom. I have successfully built CyanogenMod before, but that's it.
So, I've got my Ubuntu VM which I've built CyanogenMod in before, and I'm attempting to init a repo with the command (repo init -u git://github.com/omnirom/android.git), and it creates a bunch of tags, then I get an error "Error: revision refs/heads/master in manifests not found". Each subsequent time I try to run the command I get "Error: manifest required for this command -- please run init". It also appears that the .repo folder is pretty empty as compared to my cyanogen one.
Am I doing something wrong? Or am I just jumping the gun and the rom isn't ready to build yet.
Or they named the manifest different, or it needs to be updated first I think, I got the same error.
Sent from my Nexus 7 using XDA Premium 4 mobile app
legomaster181 said:
Keep in mind when you read this that I am a complete noob at building android in general, I just can't wait to use this rom. I have successfully built CyanogenMod before, but that's it.
So, I've got my Ubuntu VM which I've built CyanogenMod in before, and I'm attempting to init a repo with the command (repo init -u git://github.com/omnirom/android.git), and it creates a bunch of tags, then I get an error "Error: revision refs/heads/master in manifests not found". Each subsequent time I try to run the command I get "Error: manifest required for this command -- please run init". It also appears that the .repo folder is pretty empty as compared to my cyanogen one.
Am I doing something wrong? Or am I just jumping the gun and the rom isn't ready to build yet.
Click to expand...
Click to collapse
Archaic1881 said:
Or they named the manifest different, or it needs to be updated first I think, I got the same error.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this, after looking in the omnirom/android sub you will see there is a branch option which you must supply in the repo init command thru the -b command line parameter
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.3
it's working for me, downloading source as we speak.. If I can get a successful build for my N4 I will post any findings / issues that I come across that can possibly help others to build also..
VoiD_Dweller said:
Try this, after looking in the omnirom/android sub you will see there is a branch option which you must supply in the repo init command thru the -b command line parameter
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.3
it's working for me, downloading source as we speak.. If I can get a successful build for my N4 I will post any findings / issues that I come across that can possibly help others to build also..
Click to expand...
Click to collapse
I think they must've fixed it, because I swear I tried that before, but it's working now. Thanks!
Same here. At least it works now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
legomaster181 said:
I think they must've fixed it, because I swear I tried that before, but it's working now. Thanks!
Click to expand...
Click to collapse
Yeah, I originally tried it without the branch specified and got the same error..
I faced similar problem, found a workaround
VoiD_Dweller said:
Yeah, I originally tried it without the branch specified and got the same error..
Click to expand...
Click to collapse
In repo sync I faced similar problem.
...
Fetching projects: 68% (11/16) Fetching project css/scripts.git
Fetching projects: 75% (12/16) Fetching project linuxbsp/u-boot.git
Fetching projects: 100% (16/16), done.
error: manifest required for this command -- please run init
After analyzing a bit, I found for one of the git repo the checkout folder is created and it is empty.
(originally It happend because the branch I was trying to checkout was not existing)
I deleted the empty folder and ran repo sync again. problem was solved.
May be a bug in repo to be fixed?
another option is to use an "strace" for instance when i have problems downloading i will use this $ strace repo sync -f" it will show you the path of the missing file which can easily be removed for a resync
Related
First, follow these instructions to get your system setup for build:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Sholes
You'll need at least 15GB of disk space. Once you've got all the prerequisites installed:
Code:
mkdir ~/android
cd ~/android
repo init -u git://github.com/Mioze7Ae/android.git -b froyo
repo sync -j 2
. build/envsetup.sh
lunch cyanogen_sholest-eng
vendor/cyanogen/get-rommanager
make -j 2 bacon
If everything goes well, the update package will be something like out/target/product/sholest/update-cm-6.1.2-0.10-11.08.08-MilestoneXT720-signed.zip
This is my current understanding of the voodoo:
repo init : sets up your repository and downloads a manifest file that identifies other repositories
repo sync : downloads all the repositories and checks out a working copy
. build/envsetup.sh : parses all the makefiles and such to create a menu of available devices to build
lunch : configures the source tree to build a specific device (run lunch with no arguments to get a menu)
get-rommanager : apparently needed for some reason
make bacon : actually builds everything and creates the ota package. You may want to consider something like "make -j 8 bacon >build.out 2>build.err"
repo sync takes either metric or imperial eons (whichever is larger) (-j N can help by opening multiple concurrent downloads if you have a fast uplink). On a dual AMD Opteron 248 machine with 6GB build takes about 3 hours (Ubuntu 11.04 64-bit). On a dual Xeon [email protected] (8 cores total) with 16GB RAM running debian lenny 64-bit, build takes ~15 min. You want to pick the -j to be 1-2 times the number of CPUs (I used -j 2 on the AMD and -j 8 on the Xeon). The android build system does a pretty good job at pegging your CPUs.
I don't currently know how to tag the state of the entire tree, so when nadlabak or milaq or anyone else updates repositories that I didn't fork, there's a chance it may break things from time-to-time. I'm currently waiting for a build from a fresh checkout to complete. Hopefully it's not broken...
Edit: Fresh compile succeeded, update applied and booted. Happy hacking!
Feel free to peruse my repositories at http://github.com/Mioze7Ae
See also: http://android.doshaska.net/cm6build
Thanks: nadlabak, milaq, stlifey, #milestone-modding
Thanks, will add cm6 to mine build server. =)
Maybe we should make todo list and make changes that we need?
Then move it to main build tree?
fjfalcon said:
Thanks, will add cm6 to mine build server. =)
Maybe we should make todo list and make changes that we need?
Then move it to main build tree?
Click to expand...
Click to collapse
Im on it.. flashing once i have finished uploading XT720 XDA Special Hellmonger Edition, il collect data and proc
i was able to compile configs.ko
so we can dump the config of the running moto kernel
Code:
insmod configs.ko
zcat /proc/config.gz
attached is tar with module and dumped config from Central Europe kernel...
so may be finally we will be able to "debug" why on the singapore kernel it is stated that tvout works, and did not work on other kernels....
So please do:
Code:
adb push configs.ko /tmp
adb shell
/system/bin/insmod /tmp/configs.ko
exit from adb shell
Code:
adb pull /proc/config.gz
and post
Which Kernel (e.g. Central European, Korean, Singapore, Cincinaty etc....) is used
and the corresponding config.gz
edit: forget to attache
badly.... it is not the runing kernel config, but the config i have compiled.... sorry
du -h .repo - how much it has?
fjfalcon said:
du -h .repo - how much it has?
Click to expand...
Click to collapse
$ du -hs .repo
4.2G .repo
$ du -hs .
12G .
FYI, I just merged updates from milaq's repo and broke the build. Will update when I get it sorted again.
Mioze7Ae said:
FYI, I just merged updates from milaq's repo and broke the build. Will update when I get it sorted again.
Click to expand...
Click to collapse
It's working again. I'm still getting the hang of this repo/git stuff. What appears to have happened is that when I first forked milaq's repo a few weeks ago I happened to fork after the first part of a two-part commit. So, now the tree is sync'd up with milaq's latest (0.12--screenshot in powermenu, w00t!). It installs and boots but it's minimally tested.
Maybe you can archive android dir and paste it to some speed hosting?
Cause i still getting it at build server at mine work that currently free....
fjfalcon said:
Maybe you can archive android dir and paste it to some speed hosting?
Cause i still getting it at build server at mine work that currently free....
Click to expand...
Click to collapse
Hmm. I'm I'll see about that, but .repo is 4GB... and android is 12GB... that's going to be slow nomatter what... and those stupid rapid/multi/whatevers don't seem to handle resume... after the initial repo sync, the next sync is much faster.
Is repo sync still down? Or rather, is android.git.kernel.org still down? I tried repo syncing from RC2 to RC3, so I could implement a patch for Exchange security features (more on this later, I will update when I get it working).
For now, I will try the compile on RC2.
I do know it was down last Friday, but I haven't had a chance to try more recently.
Hi,
I'm going to port Firefox OS to my I9082 but I have some problems after "./config.sh i9082".
It can't get some repositories from android.git.linaro.com and after that it stuck at "Fetching objects: 25% (20/78)" and after this, I waited for 8 hours!!!!! :crying:
after this, i closed the terminal.
I tried again using "repo sync" to continue but there is a new problem! It says that some of repos not found! for example i can't get "platform/external/freetype" and "platform/external/dbus" from linaro git.
Can anybody help me?
Delete broken projects and sync again
DataUnit said:
Hi,
I'm going to port Firefox OS to my I9082 but I have some problems after "./config.sh i9082".
It can't get some repositories from android.git.linaro.com and after that it stuck at "Fetching objects: 25% (20/78)" and after this, I waited for 8 hours!!!!! :crying:
after this, i closed the terminal.
I tried again using "repo sync" to continue but there is a new problem! It says that some of repos not found! for example i can't get "platform/external/freetype" and "platform/external/dbus" from linaro git.
Can anybody help me?
Click to expand...
Click to collapse
Delete all folder expect .repo and start over.
arky_r said:
Delete all folder expect .repo and start over.
Click to expand...
Click to collapse
I did this action 4 times and when I executed the command again, it will stop at another project! :crying:
DataUnit said:
I did this action 4 times and when I executed the command again, it will stop at another project! :crying:
Click to expand...
Click to collapse
Did you reading the repo tips at xda-universityDOTcom ?
Syncing a full new source tree in minutes!
Time might come when you’ll need to work with several full source trees. For example, you may want to have an AOKP source tree as well as a CM tree.
Obvisouly, you could repeat the same steps, to repo init and then repo sync -j 8 -c for both. But that would be twice as time consuming.
There is an alternative that should be much faster. Lets say that you have already initialized and synced a CM source tree, in ~/android/cm.
Now, we will prepare a new repo for AOKP tree, in ~/android/aokp. Here comes the trick: We will use the --reference flag of repo init to indicate to repo that we already have a local repository that it can take information from, instead of downloading everything from Internet again:
mkdir ~/android/aokp cd ~/android/aokp repo init --reference=~/android/cm -u git://github.com/AOKP/platform_manifest.git -b jb
1
2
3
mkdir ~/android/aokp
cd ~/android/aokp
repo init --reference=~/android/cm -u git://github.com/AOKP/platform_manifest.git -b jb
You should notice a big time diference, from hours for a full repo sync, down to minutes using this trick!
I've got my repo synced to the pac-4.4 branch, but now that the team has switched repos to Pinky Inky and Clyde, my repo syncs have been failing. Can somebody help walk me through the steps to set everything back up using the new repo?
numel007 said:
I've got my repo synced to the pac-4.4 branch, but now that the team has switched repos to Pinky Inky and Clyde, my repo syncs have been failing. Can somebody help walk me through the steps to set everything back up using the new repo?
Click to expand...
Click to collapse
What device are you trying to build for, what is the error you're getting, what is the contents of your roomservice file?
Sent from my Xperia Ray using Tapatalk
Langes said:
What device are you trying to build for, what is the error you're getting, what is the contents of your roomservice file?
Sent from my Xperia Ray using Tapatalk
Click to expand...
Click to collapse
I will be building for the HTC LTE aka Jewel
Fatal error message was: Fetching projects: 80% (355/443) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Full log can be found here: http://pastebin.com/G9UbGBuG
Roomservice.xml inside .repo/local_manifests is:
<manifest><project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0"/><project name="Pinky-Inky-and-Clyde/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0"/></manifest>
Click to expand...
Click to collapse
numel007 said:
I will be building for the HTC LTE aka Jewel
Fatal error message was: Fetching projects: 80% (355/443) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Full log can be found here: http://pastebin.com/G9UbGBuG
Roomservice.xml inside .repo/local_manifests is:
Click to expand...
Click to collapse
roomservice is 100%
Delete the default.xml file in .repo folder and do the init repo command again. This should fix you up as the pacman folder was renamed and your repo did not update that somehow.
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Langes said:
roomservice is 100%
Delete the default.xml file in .repo folder and do the init repo command again. This should fix you up as the pacman folder was renamed and your repo did not update that somehow.
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Click to expand...
Click to collapse
Deleting the file and rerunning the command causes an immediate fatal error since the default.xml file can not be found. Should I restore it and just delete everything inside the file?
[email protected]:~/PacRom-4.4$ repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
[email protected]:~/PacRom-4.4$
Click to expand...
Click to collapse
numel007 said:
Deleting the file and rerunning the command causes an immediate fatal error since the default.xml file can not be found. Should I restore it and just delete everything inside the file?
Click to expand...
Click to collapse
My bad, you should delete manifest.xml inside the ~/PacRom-4.4/.repo folder and init again.
Langes said:
My bad, you should delete manifest.xml inside the ~/PacRom-4.4/.repo folder and init again.
Click to expand...
Click to collapse
File deleted, terminal restarted. Initiated repo again, ran repo sync, same failure as before unfortunately. Looks like somehow my repo isn't updating even after manifest.xml was deleted.
numel007 said:
File deleted, terminal restarted. Initiated repo again, ran repo sync, same failure as before unfortunately. Looks like somehow my repo isn't updating even after manifest.xml was deleted.
Click to expand...
Click to collapse
Do you have any other xml files in .repo and in .repo/local_manifests? If you do, delete them all.
Do you have an android or a pacman folder in the top folder of you source tree? Or both?
Langes said:
Do you have any other xml files in .repo and in .repo/local_manifests? If you do, delete them all.
Do you have an android or a pacman folder in the top folder of you source tree? Or both?
Click to expand...
Click to collapse
Any and all xmls? And yes I have an Android folder in root of files.
Edit: Did a search for all xml files and deleted roomservice and manifest. Had to keep default to make the repo init still run. Repo sync ended with one error less. Still can not retrieve from pac. I also deleted the default.xml in the android folder.
Fetching project platform/external/lzma
Fetching projects: 99% (434/438) fatal: Not a git repository: '/home/derek/PacRom-4.4/.repo/projects/pacman.git'
error: Cannot fetch pacman
error: Exited sync due to fetch errors
numel007 said:
Any and all xmls? And yes I have an Android folder in root of files.
Edit: Did a search for all xml files and deleted roomservice and manifest. Had to keep default to make the repo init still run. Repo sync ended with one error less. Still can not retrieve from pac. I also deleted the default.xml in the android folder.
Fetching projects: 99% (434/438) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Click to expand...
Click to collapse
ok, delete all folders and files in your source folder except .repo (the source code you have downloaded is in .repo so you will not have to re-download everything)
then run the init command again and sync again
Langes said:
ok, delete all folders and files in your source folder except .repo (the source code you have downloaded is in .repo so you will not have to re-download everything)
then run the init command again and sync again
Click to expand...
Click to collapse
Deleted everything but .repo and ran init again. Repo sync still can't fetch from pac. Maybe I should just do a fresh start and reset the entire build envirnment.
numel007 said:
Deleted everything but .repo and ran init again. Repo sync still can't fetch from pac. Maybe I should just do a fresh start and reset the entire build envirnment.
Click to expand...
Click to collapse
Compare the contents of manifests.xml inside the .repo folder to this: https://github.com/PAC-man/pacman/blob/pac-4.4/default.xml
Line 499 should read:
Code:
<project path="pacman" name="pacman" remote="pac" revision="pac-4.4" />
Langes said:
Compare the contents of manifests.xml inside the .repo folder to this: https://github.com/PAC-man/pacman/blob/pac-4.4/default.xml
Line 499 should read:
Code:
<project path="pacman" name="pacman" remote="pac" revision="pac-4.4" />
Click to expand...
Click to collapse
Yes line 499 read that. But to play it safe, I deleted the entire file and replaced it with a straight paste from that link you gave me. Repo init again, then repo sync, same failure. Out of ideas yet? lol
rm -rf .repo/projects/device/*
repo sync
arrrghhh said:
rm -rf .repo/projects/device/*
repo sync
Click to expand...
Click to collapse
Thank you. Unfortunately I already deleted my entire source code and redownloaded. Thankfully everything works now. Thanks for the input, both of you.
Sent from my EVO
Docker template for building CyanogenMod
Building CyanogenMod requires quite a lot of work. You will need to install a large number of dependencies, and you will need to read through lots of documentation.
Docker is a rather new software to automate the deployment of applications inside a software container.
Here is a Docker container for running an environment which contains everything that is needed to compile CyanogenMod. It will be very easy to install, and it will just work! The Github page contains some further information on how to get started.
NOTE: You will need to install Docker to proceed: https://www.docker.io/gettingstarted/
How to run:
Code:
git clone https://github.com/stucki/docker-cyanogenmod.git
cd docker-cyanogenmod
./run.sh
How to build CyanogenMod for your device:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
repo sync
source build/envsetup.sh
brunch <device codename> # example: brunch grouper
Download:
Github URL: https://github.com/stucki/docker-cyanogenmod
ChangeLog:
see https://github.com/stucki/docker-cyanogenmod/blob/master/CHANGELOG.md
Questions and Answers:
see http://forum.xda-developers.com/android/help/qa-docker-template-building-cyanogenmod-t3173025
Any feedback is welcome. Enjoy!
michael_ch said:
Docker template for building CyanogenMod
Building CyanogenMod requires quite a lot of work. You will need to install a large number of dependencies, and you will need to read through lots of documentation.
Docker is a rather new software to automate the deployment of applications inside a software container.
Here is a Docker container for running an environment which contains everything that is needed to compile CyanogenMod. It will be very easy to install, and it will just work! The Github page contains some further information on how to get started.
How to build:
Code:
git clone https://github.com/stucki/docker-cyanogenmod.git
cd docker-cyanogenmod
./build.sh
How to run:
Code:
cd docker-cyanogenmod
./run.sh
How to build CyanogenMod for your device:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo sync
source build/envsetup.sh
breakfast <device codename> # example: breakfast grouper
brunch <device codename> # example: brunch grouper
Download:
Github URL: https://github.com/stucki/docker-cyanogenmod
ChangeLog:
Code:
2014-02-16
* Initial release
Any feedback is welcome. Enjoy!
Click to expand...
Click to collapse
seems interesting!!!!
Awesome !!! Thanks a lot OP
michael_ch said:
Docker template for building CyanogenMod
Click to expand...
Click to collapse
:good: nice.......
You missed one point though .....
Code:
BUILD_HOST_32bit=1 (Cyanogenmod needs 32 bit binaries to compile)
and you can incorporate this in your code
Code:
RUN apt-get purge openjdk-\* icedtea-\* icedtea6-\*
RUN add-apt-repository ppa:webupd8team/java
RUN apt-get update && sudo apt-get install oracle-java6-installer
This installs the correct jdk for cyanogenmodand resolves the incorrect jre errors some people will get..Just my 2 cents!!..
There is scope for expansion, I have a built a similar tool but not getting the time anymore to push new updates..,,,anyways keep up the good work..
Wow. This is superb. ! This will really reduce our most of the work. Thanks op
Dark Wraith said:
:good: nice.......
You missed one point though .....
Code:
BUILD_HOST_32bit=1 (Cyanogenmod needs 32 bit binaries to compile)
Click to expand...
Click to collapse
32bit libraries are installed on the system. Just try it out, I successfully built images for i9100 and grouper without specifying this line...
Dark Wraith said:
and you can incorporate this in your code
Code:
RUN apt-get purge openjdk-\* icedtea-\* icedtea6-\*
RUN add-apt-repository ppa:webupd8team/java
RUN apt-get update && sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
Again, I don't get those errors. Anyone else encountering these problems?
Dark Wraith said:
This installs the correct jdk for cyanogenmodand resolves the incorrect jre errors some people will get..Just my 2 cents!!..
There is scope for expansion, I have a built a similar tool but not getting the time anymore to push new updates..,,,anyways keep up the good work..
Click to expand...
Click to collapse
Thank you! I will do my best...
I get this error when running
"./build.sh"
./build.sh: 10: ./build.sh: docker: not found
Dasmikko said:
I get this error when running
"./build.sh"
./build.sh: 10: ./build.sh: docker: not found
Click to expand...
Click to collapse
Well. You will need to install Docker, of course, see https://www.docker.io/gettingstarted/#h_installation.
Sorry, I thought it's clear. But I will update the post accordingly...
very interesting. will try
ubuntu 32 bit not works for this???
michael_ch said:
Well. You will need to install Docker, of course, see https://www.docker.io/gettingstarted/#h_installation.
Sorry, I thought it's clear. But I will update the post accordingly...
Click to expand...
Click to collapse
Works now
So does this create a local_manifest.xml(which is needed) for you if you're trying to build for an unsupported device
sent from my JEDI ELITE Note 3
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
markbencze said:
So does this create a local_manifest.xml(which is needed) for you if you're trying to build for an unsupported device
Click to expand...
Click to collapse
Nope, the manifest is created by running the "breakfast" command. Check the 1st post for more info.
I have also used this box to successfully build an image for the Motorola Moto G. As this is not part of the CyanogenMod project yet, I had to install the manifest using the steps described on the following Github page: https://github.com/razrqcom-dev-team/android_local_razrqcom
Code:
# see https://github.com/razrqcom-dev-team/android_local_razrqcom
mkdir .repo/local_manifests
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
curl -L -o .repo/local_manifests/msm8226.xml -O -L https://raw.github.com/razrqcom-dev-team/android_local_razrqcom/msm8226-kk/msm8226.xml
curl -L -o .repo/local_manifests/vendor.xml -O -L https://raw.github.com/razrqcom-dev-team/android_local_razrqcom/msm8226-kk/vendor.xml
# after that, sync all repositories
repo sync
# start building falcon (that's the codename for the Moto G)
source build/envsetup.sh
brunch falcon
Kudos for this goes to @dhacker29 and his team!
michael_ch said:
Nope, the manifest is created by running the "breakfast" command. Check the 1st post for more info.
I have also used this box to successfully build an image for the Motorola Moto G. As this is not part of the CyanogenMod project yet, I had to install the manifest using the steps described on the following Github page: https://github.com/razrqcom-dev-team/android_local_razrqcom
Click to expand...
Click to collapse
Ok well maybe I'll give it a whirl then. I was trying to build beanstalk for the n3 and I init the repo referencing the cm repo I already had synced, then sunced repo etc. When I tried breakfast there was no option to choose my device.
So by using this tool and following your directions will it allow me to do so then?
sent from my JEDI ELITE Note 3
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
Is this only cyanogenmod restricted or we can use on other ROMs also?
Sent from my GT-I9100 using XDA Premium 4 mobile app
I get permission denied?
safariking said:
I get permission denied?
Click to expand...
Click to collapse
Run with sudo
markbencze said:
So by using this tool and following your directions will it allow me to do so then?
Click to expand...
Click to collapse
This is not a tool, it is just a script which creates a virtual machine with all that is needed for building CyanogenMod.
koolkunz said:
Is this only cyanogenmod restricted or we can use on other ROMs also?
Click to expand...
Click to collapse
Looking at the build requirements for OmniROM, I think it will also work for other ROMs: http://docs.omnirom.org/Setting_Up_A_Compile_Environment
In case that something is missing, just update the Dockerfile and run build.sh to rebuild the image.
michael_ch said:
This is not a tool, it is just a script which creates a virtual machine with all that is needed for building CyanogenMod.
Looking at the build requirements for OmniROM, I think it will also work for other ROMs: http://docs.omnirom.org/Setting_Up_A_Compile_Environment
In case that something is missing, just update the Dockerfile and run build.sh to rebuild the image.
Click to expand...
Click to collapse
OK..thanks...I wanna build omni
Sent from my GT-I9100 using XDA Premium 4 mobile app
I just did a build for grouper, but I can't find the builded file.. Where does it go? and does it output a zip file?
michael_ch said:
Docker template for building CyanogenMod
Building CyanogenMod requires quite a lot of work. You will need to install a large number of dependencies, and you will need to read through lots of documentation.
Docker is a rather new software to automate the deployment of applications inside a software container.
Here is a Docker container for running an environment which contains everything that is needed to compile CyanogenMod. It will be very easy to install, and it will just work! The Github page contains some further information on how to get started.
NOTE: You will need to install Docker to proceed: https://www.docker.io/gettingstarted/
How to build:
Code:
git clone https://github.com/stucki/docker-cyanogenmod.git
cd docker-cyanogenmod
./build.sh
How to run:
Code:
cd docker-cyanogenmod
./run.sh
How to build CyanogenMod for your device:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo sync
source build/envsetup.sh
breakfast <device codename> # example: breakfast grouper
brunch <device codename> # example: brunch grouper
Download:
Github URL: https://github.com/stucki/docker-cyanogenmod
ChangeLog:
Code:
2014-02-16
* Initial release
Any feedback is welcome. Enjoy!
Click to expand...
Click to collapse
bro can this be used to make unofficial ports too???
Hey everyone, hope someone can help
When I run the command "breakfast hlte"
I get:
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_hlte
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/msm8960-common/msm8960.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
[email protected]:~/android/system$
Click to expand...
Click to collapse
Also, if I proceed and try to extract the proprietry blobs with "extract-files.sh" I get:
Extracting /system/etc/firmware/a330_pfp.fw ...
37 KB/s (2212 bytes in 0.058s)
Extracting /system/etc/firmware/a330_pm4.fw ...
91 KB/s (9220 bytes in 0.098s)
Extracting /system/vendor/lib/libmm-color-convertor.so ...
87 KB/s (9308 bytes in 0.103s)
Extracting /system/lib/cdma/libsec-ril.so ...
remote object '/system/lib/cdma/libsec-ril.so' does not exist
Click to expand...
Click to collapse
Any help would be appreciated
EDIT: the line where it fails is pointing the wrong place :/ I found it in root explorer so I'll see what I can do
EDIT: fixed the cdma/libsec-ril.so
but now it's complaining it can't find a gsm version...
Use the blobs from the GitHub repo TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/hlte. Unfortunately I can't post a direct link due to onerous XDA restrictions on new user's posts. I am having the same problem with not being able to extract all the propietary blobs from my Note 3 device.
CW03 said:
Hey everyone, hope someone can help
When I run the command "breakfast hlte"
I get:
Also, if I proceed and try to extract the proprietry blobs with "extract-files.sh" I get:
Any help would be appreciated
EDIT: the line where it fails is pointing the wrong place :/ I found it in root explorer so I'll see what I can do
EDIT: fixed the cdma/libsec-ril.so
but now it's complaining it can't find a gsm version...
Click to expand...
Click to collapse
Did you ever get this figured out? I am trying to build right now and am having the same problem. I got the blobs from that github repository, and am still running into this same error.
[email protected]:~/android/system$ breakfast hlte
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/msm8960-common/msm8960.mk" does not exist. Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-11.0
Checking branch info
CyanogenMod/android_device_samsung_hlte already exists
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_hlte
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/msm8960-common/msm8960.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
[email protected]:~/android/system$
Click to expand...
Click to collapse
iamdanhenry said:
Did you ever get this figured out? I am trying to build right now and am having the same problem. I got the blobs from that github repository, and am still running into this same error.
Click to expand...
Click to collapse
Do you have device/samsung/msm8960-common/msm8960.mk? If you did used "lunch", it should add this repo (and a few others) to your .repo/local_manifests/roomservice.xml. The repos are defined in device/samsung/hlte/cm.dependencies, which should already be there.
If it doesn't fetch the repos automatically, you can do this with "repo sync".
For the proprietary blobs, you only need to add the samsung repo from TheMuppets github to your .repo/local_manifests/whatever.xml and "repo sync" to pull it in. No need to try to extract anything from your device.
jisoo said:
Do you have device/samsung/msm8960-common/msm8960.mk? If you did used "lunch", it should add this repo (and a few others) to your .repo/local_manifests/roomservice.xml. The repos are defined in device/samsung/hlte/cm.dependencies, which should already be there.
If it doesn't fetch the repos automatically, you can do this with "repo sync".
For the proprietary blobs, you only need to add the samsung repo from TheMuppets github to your .repo/local_manifests/whatever.xml and "repo sync" to pull it in. No need to try to extract anything from your device.
Click to expand...
Click to collapse
After I posted I went and downloaded msm8960-common repository and extracted it into the build directory, it then got the same error for some qualcomm libraries that were missing so I downloaded those as well. I then added the proprietary files from the "TheMuppets" repo.
It would appear things are going better now, but still can't build because of some errors with the kernel not being there. I am going to go download the kernel source and try to get it figured out. If I can't I will make a new thread.
Thank you for your help!