I want to compiled cm from source
so I started with setting build environment and downloading sources
I also added vendor and device folder then
for building android I used these command
source build/envsetup.sh && brunch cyanogen_p500-eng
but after some seconds I got these error
http://pastebin.com/y27A551E
can anyone help me with solving these error
I really need help
aspee
bumping.
please I really started to feel helpless
aspee said:
bumping.
please I really started to feel helpless
Click to expand...
Click to collapse
Lol... sorry, but i cant help u here...
Ask arjen, lupohirp or adfad..
I asked bytecode he think that syncing is not correct so I deleted framework and sync again but still the same error
Sent from my LG-P500 using Tapatalk
I have been trying for 2 days now to figure out how to fix this error, but I'm stumped.
After choosing my device in the 'lunch' menu, I receive this:
Build/core/config.mk:145:***no config file found for TARGET_DEVICE. Stop.
I have seen this error here and there while searching, but no one seems to have an answer on how to fix it. I have the vendorsetup file (I say that because that's the only info I get from people is 'make a file named vendorsetup.mk and add this to it'). I have synced sbrissens fascinate and aries-common repo files, and no matter what I do, it fetches the same error.
Any help would b much appreciated. I'm at my wits end here. This is driving me nuts! (Not that i get the error, but that I can't seem to find a fix ANYWHERE)
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
triptosyll said:
I have been trying for 2 days now to figure out how to fix this error, but I'm stumped.
After choosing my device in the 'lunch' menu, I receive this:
Build/core/config.mk:145:***no config file found for TARGET_DEVICE. Stop.
Click to expand...
Click to collapse
Hi
I assume you're adding extra devices into the aosp lunch menu. All the info for finding out what's wrong is in the error message; Have you had a look at line 145 in build/core/config.mk? On my JB AOSP tree it's a check for BoardConfig.mk. At a guess I would say you are missing a BoardConfig.mk, It'd be useful if you could link to the device repo you are using
Hope that Helps
trevd said:
Hi
I assume you're adding extra devices into the aosp lunch menu. All the info for finding out what's wrong is in the error message; Have you had a look at line 145 in build/core/config.mk? On my JB AOSP tree it's a check for BoardConfig.mk. At a guess I would say you are missing a BoardConfig.mk, It'd be useful if you could link to the device repo you are using
Hope that Helps
Click to expand...
Click to collapse
Yes I added a device. And yes that's what mine is checking for too. That's why this is so confusing. I HAVE a boardconfig.mk file. It just won't seem to find it....
Here's the repo I used. Its sbrissens. It has some common files with other carrier variants, so I got the aries-common files from his repo, and the fascinatemtd files too:
https://github.com/sbrissen/android_device_samsung_fascinatemtd
That's JUST his fascinatemtd files. I have downloaded the jb branch of the aries-common files too. If u want a look at those, they're on his repo page too.
Thanks for getting back to me. I can't seem to get anyone to help. My posts get buried beneath a bunch of others' that by the time the op for the guide I'm using gets online to help out, my post is buried and most of the time isn't seen.
:thumbup::thumbup:
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
triptosyll said:
Thanks for getting back to me. I can't seem to get anyone to help. My posts get buried beneath a bunch of others' that by the time the op for the guide I'm using gets online to help out, my post is buried and most of the time isn't seen.
:thumbup::thumbup:
Click to expand...
Click to collapse
Not a problem, It took me a while to get a build that would boot on a device, it's a case of reading, then reading some more, the android building google group is a useful resource.
I've just clone the repo you linked to and successfully "lunched" it, looks like there's some hardcoded paths in there.
so you'll want to use device/samsung/fascinatemtd as the path for the device files.... It still doesn't build as it needs some vendor specific files etc, but that's your adventure.
Whenever you run into build problems the *.mk files tell all. It might be useful to read up on what it takes to add a new device as that will give you an insight into how the build system "glues" together.
Good Luck
trevd said:
Not a problem, It took me a while to get a build that would boot on a device, it's a case of reading, then reading some more, the android building google group is a useful resource.
I've just clone the repo you linked to and successfully "lunched" it, looks like there's some hardcoded paths in there.
so you'll want to use device/samsung/fascinatemtd as the path for the device files.... It still doesn't build as it needs some vendor specific files etc, but that's your adventure.
Whenever you run into build problems the *.mk files tell all. It might be useful to read up on what it takes to add a new device as that will give you an insight into how the build system "glues" together.
Good Luck
Click to expand...
Click to collapse
So could my problem b that I downloaded the files from his repo as a .zip, instead of cloning it with terminal? Cuz if that doesn't do it, I don't know why it won't lunch for me. I pulled them as a zip, unzipped it and placed it in device/samsung/ fascinatemtd. Should I try it with the terminal instead?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
triptosyll said:
So could my problem b that I downloaded the files from his repo as a .zip, instead of cloning it with terminal? Cuz if that doesn't do it, I don't know why it won't lunch for me. I pulled them as a zip, unzipped it and placed it in device/samsung/ fascinatemtd. Should I try it with the terminal instead?
Click to expand...
Click to collapse
Shouldn't really make any difference unless your permissions are at fault, I tend to live in a bash shell anyway so from your aosp tree something like this might do the trick
Code:
cd device/samsung
git clone https://github.com/sbrissen/android_device_samsung_fascinatemtd.git fascinatemtd
cd ../..
source build/envsetup.sh
lunch full_fascinatemtd-userdebug
If your still having problems though I would first make sure you can lunch one of the standard AOSP options and also make sure your using bash as I think the build system has some bashism in it.
trevd said:
Shouldn't really make any difference unless your permissions are at fault, I tend to live in a bash shell anyway so from your aosp tree something like this might do the trick
Code:
cd device/samsung
git clone https://github.com/sbrissen/android_device_samsung_fascinatemtd.git fascinatemtd
cd ../..
source build/envsetup.sh
lunch full_fascinatemtd-userdebug
If your still having problems though I would first make sure you can lunch one of the standard AOSP options and also make sure your using bash as I think the build system has some bashism in it.
Click to expand...
Click to collapse
May I ask u one thing? In your little script u wrote out for me to do, the part that says cd ../.., which directory are u talking about? The WORKING_DIRECTORY?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
triptosyll said:
May I ask u one thing? In your little script u wrote out for me to do, the part that says cd ../.., which directory are u talking about? The WORKING_DIRECTORY?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
Click to expand...
Click to collapse
Yeah he is...go back to whatever your working directory is named...he said ../.. cause he wasn't sire what you named yours
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Yeah he is...go back to whatever your working directory is named...he said ../.. cause he wasn't sire what you named yours
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Nice! Thanks guys. I'll delete the files I had, and do a github clone, see if it works. And try lunching another one of the choices, see if it will work. I'll report back in prolly around an hour.
Thx a lot guys!
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
Dammit! My internet just went down. I'll get back to u when I can clone sbrissens github. Thanks for the help guys. I'll let u know how it goes when my 'net's back up and running.
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
So, I did sync sbrissens github.....still the same error. Then I tried number 1- full_eng....same error.
Tried crespo....same error. Every lunch option gives me that error. Now I'm REALLY lost. I have no idea what the problem is. Any help?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
triptosyll said:
So, I did sync sbrissens github.....still the same error. Then I tried number 1- full_eng....same error.
Tried crespo....same error. Every lunch option gives me that error. Now I'm REALLY lost. I have no idea what the problem is. Any help?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
Click to expand...
Click to collapse
You've got me buddy, not a clue what you've done I'd be tempted to write that one off as a bad job and start again..... I wouldn't worry about syncing the fascinate repo's at first just make sure you can get a clean AOSP build..... Just for reference Google's Guide to Building the AOSP although your probably already following that.
It' is very much one step at a time with this until you get an idea of what lives where and how it all fits. I must admit it did take me a good couple of go's before I got it right myself, Thank <insert deity here> for unlimted bandwidth.
trevd said:
You've got me buddy, not a clue what you've done I'd be tempted to write that one off as a bad job and start again..... I wouldn't worry about syncing the fascinate repo's at first just make sure you can get a clean AOSP build..... Just for reference Google's Guide to Building the AOSP although your probably already following that.
It' is very much one step at a time with this until you get an idea of what lives where and how it all fits. I must admit it did take me a good couple of go's before I got it right myself, Thank <insert deity here> for unlimted bandwidth.
Click to expand...
Click to collapse
Yeah, but the LAST thing I wanna do is resync the repo. That takes SO damned long. That's all I can do tho isn't it? If I wanna start over? Delete the source, and re sync it?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
triptosyll said:
Yeah, but the LAST thing I wanna do is resync the repo. That takes SO damned long. That's all I can do tho isn't it? If I wanna start over? Delete the source, and re sync it?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
Click to expand...
Click to collapse
Unless you want to get deep inside the animals, so to speak, but I think at this stage you're probably best off starting again otherwise you may "waste" a good couple of hours chasing errors, you'll probably learn a thing or two along the way it all depends how you look at it really, every cloud etc...... I suppose you could just try deleting your WORKING_DIRECTORY/device directory and just resync that to begin with. see if that cures what ale's ya', I find repo sync -j16 speeds things up a little as well
No need to resync the repo at all. All your changes are topical. You can run a "repo forall -c "git reset HARD"".
You can also do something else. Go into your repo path folder. Hit control h to show hidden files. Ctrl a selects them all then unselect the .repo folder by holding Ctrl while clicking on it. Delete all the folders and open your terminal. Do a repo sync. Only this time you are not downloading 7 gigs of stuff. Everything already exists in that .repo folder. Removing all and resyncing just refreshes everything.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
No need to resync the repo at all. All your changes are topical. You can run a "repo forall -c "git reset HARD"".
You can also do something else. Go into your repo path folder. Hit control h to show hidden files. Ctrl a selects them all then unselect the .repo folder by holding Ctrl while clicking on it. Delete all the folders and open your terminal. Do a repo sync. Only this time you are not downloading 7 gigs of stuff. Everything already exists in that .repo folder. Removing all and resyncing just refreshes everything.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's kinda funny u just posted that, cuz I was just looking at your cm compiler thread, and saw the link to the compile jb on Ubuntu thread, where u explained how to do that.
I just left this thread to go back to ur cm compiler thread to get that link and bring it back here and post it.
http://forum.xda-developers.com/showpost.php?p=29148373&postcount=593
Good timing man. And thanks for the help guys. In a day at most, I'll get back to ya on how it went. Thank u thank u thank u!!
:thumbup::thumbup::thumbup:
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
lithid-cm said:
No need to resync the repo at all. All your changes are topical. You can run a "repo forall -c "git reset HARD"".
You can also do something else. Go into your repo path folder. Hit control h to show hidden files. Ctrl a selects them all then unselect the .repo folder by holding Ctrl while clicking on it. Delete all the folders and open your terminal. Do a repo sync. Only this time you are not downloading 7 gigs of stuff. Everything already exists in that .repo folder. Removing all and resyncing just refreshes everything.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, a lesson in repo commands is in my future I think :laugh:.... Yeah Don't listen to me, listen to this man! :good:.
trevd said:
Thanks, a lesson in repo commands is in my future I think :laugh:.... Yeah Don't listen to me, listen to this man! :good:.
Click to expand...
Click to collapse
Lithid's the MAN!!
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
And check out that link. He explains it in repo commands in the link. :thumbup:
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
Hey guys, quick question. I said earlier how there are some common files I need too, do those common files go in /device/Samsung? Or in /device/Samsung/fascinatemtd?
________________________________
Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
i followed this http://forum.xda-developers.com/showthread.php?t=1866545
i have synced cm7 sources ..then issued make -j4 otatools it gives error
Code:
[email protected]:~/android/system$ make -j4 otatools
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[vendor/cyanogen/products/cyanogen_ace.mk]]: "device/htc/ace/ace.mk" does not exist. Stop.
can i skip this step?
manoj94 said:
build/core/product_config.mk:196: *** _nic.PRODUCTS\
Click to expand...
Click to collapse
go to this" make file "and read it, see what it's asking for, you can push it through, but it may not compile correctly..plus its saying you don't have the ace.mk Do you? If so ask yourself, "why cant it find it?"
Warped420 said:
go to this" make file "and read it, see what it's asking for, you can push it through, but it may not compile correctly..plus its saying you don't have the ace.mk Do you? If so ask yourself, "why cant it find it?"
Click to expand...
Click to collapse
i tried creating ace.mk from github it keeps on asking many files
O Did you clone the whole device tree from github? If not change dir to device. CD company name. Then git clone the whole device tree. Also read my Source tut Warped420.
Warped420 said:
O Did you clone the whole device tree from github? If not change dir to device. CD company name. Then git clone the whole device tree. Also read my Source tut Warped420.
Click to expand...
Click to collapse
thanks buddy..i solved it already by removing unnecessary devices in vendor tree
Yeah , i been on cm 10.1 well a hybrid based on 10.1.. so i don't really know the setup for 7...Good job on fixin it,
Is there any way to download the android source code with torrent?
I am trying to download the jb 4.3 source code with repo tool but the speed is too slow and I got an error while saving the source code...!
so the source code folder is still empty...!
nothing is shown there...!
please update the torrent links of android sources of different versions...!
thanks in advance
You could use a download manager like DAM. this will speed up the download and rescue it if it fails.
Sent from my GT-I9505G using Tapatalk
Need a Tutorial about this ...!
or any guideline with pictures ...!
do not understand how to use it ...!
Waiting for your reply ...!
AMoosa said:
You could use a download manager like DAM. this will speed up the download and rescue it if it fails.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
R u serious?! Suppose u r talking about Download accelearate manager and that is a windows app while we stream the android source in ubuntu/linux distro/MacOSX lmao
and obviously even if ubuntu had it, we wouldn't be able to use such a 3rd party like that w terminal.
Muhammad_Ali said:
Need a Tutorial about this ...!
or any guideline with pictures ...!
do not understand how to use it ...!
Waiting for your reply ...!
Click to expand...
Click to collapse
To OP: u cant speed up tho, it depends on ur connection and my speed is slow, too. All u should do is use -f flag to force the sync to continue over broken things: for example u can use "repo sync -f -j16" or so. It will be slow and long at ur first sync and first rom source. For second source (that u may work w multiple roms later) you can use the flag --reference=~/path/to/your/first/source if they r the same android version like slimkat and beanstalk 4.4 and carbon 4.4 or so in order to save u tons of space and time.
And one more thing, u r posting in wrong section, should go to Android general question and answer tho. Will report this later that Mods can move it to the right section.
Sent from my GT-N7000 using Tapatalk
can I use this "-f" flag with the command
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.3_r2.2-cts
Is there any way to force this download without any error?
If yes then please help me...! also tell is it necessary to run these commands as root user?
Muhammad_Ali said:
can I use this "-f" flag with the command
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.3_r2.2-cts
Is there any way to force this download without any error?
If yes then please help me...! also tell is it necessary to run these commands as root user?
Click to expand...
Click to collapse
You just need it to initialize the repo. If you are going to sync it, you can stop it in every moment without breaking anything. You will just lost the progress of your currently synced project.
Hey. I am following modpunk tread on CM 12.1 build for Samsung Galaxy Alpha.
I have done almost all the steps in the README.
Now I wonder how I copy proprietary vendor files.
The README only tell me to run "./extract-files.sh", cant find where this hidden file is located.
Here is the steps in the README;
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Thanks in advance.
protruckker said:
Hey. I am following modpunk tread on CM 12.1 build for Samsung Galaxy Alpha.
I have done almost all the steps in the README.
Now I wonder how I copy proprietary vendor files.
The README only tell me to run "./extract-files.sh", cant find where this hidden file is located.
Here is the steps in the README;
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Thanks in advance.
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/Build_for_klte Just one as an example, I'm using klte.
The guide states you can find it under
SOURCECODEFOLDER/device/Samsung/CODENAME
Where SOURCECODEFOLDER is the folder where you downloaded the cyanogenmod source code (repo sync) and CODENAME is the code name for your device.
For Samsung devices, if you are getting any errors related to the building of some system applications like "TimeService.apk", I'd suggest you to use the files hoted at " TheMuppets" github repository.
I have done the "repo sync". After this big download I am going to directory:
"cyanogenmod/system/device/"
In this directory I only have these folders:
Common, Generic, Google, Qcom and Sample
protruckker said:
I have done the "repo sync". After this big download I am going to directory:
"cyanogenmod/system/device/"
In this directory I only have these folders:
Common, Generic, Google, Qcom and Sample
Click to expand...
Click to collapse
Can you put the link of the guide you are trying to follow? It seems like you are missing the step "breakfast", probably because there's no official build for your device. You are trying to port cyanogenmod, right?
Inviato dal mio SM-G900F utilizzando Tapatalk
Ciuffy said:
Can you put the link of the guide you are trying to follow? It seems like you are missing the step "breakfast", probably because there's no official build for your device. You are trying to port cyanogenmod, right?
Inviato dal mio SM-G900F utilizzando Tapatalk
Click to expand...
Click to collapse
yep, I am trying to port it.
Here is the "guide" I am following. Its just a readme with the build steps.
URL:
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
protruckker said:
yep, I am trying to port it.
Here is the "guide" I am following. Its just a readme with the build steps.
URL:
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Click to expand...
Click to collapse
Not a definitive answer, but it looks like something has gone wrong with your syncing. As you can see from the readme, the manifest should include "projects/android/android_device_samsung_slte.git" and
"projects/android/android_kernel_samsung_slte.git". By looking at the file tree of the _device_ one, there is actually a file called "extract-files.sh". Use an utility like "locate" or a search bar in your desktop manager to see if you actually have this file, as the repo sync should have cloned the git repository!
Ciuffy said:
Not a definitive answer, but it looks like something has gone wrong with your syncing. As you can see from the readme, the manifest should include "projects/android/android_device_samsung_slte.git" and
"projects/android/android_kernel_samsung_slte.git". By looking at the file tree of the _device_ one, there is actually a file called "extract-files.sh". Use an utility like "locate" or a search bar in your desktop manager to see if you actually have this file, as the repo sync should have cloned the git repository!
Click to expand...
Click to collapse
I think I have found the problem. I did spell a folder name wrong. Think thats it.
protruckker said:
The repo is about 50 Gb so should I try to sync it again?
Click to expand...
Click to collapse
50? You sure? Have you tried using the -c option while syncing? My CM 12.1 source code is working and it's "merely" 25 GBs or less.
Anyway, if you are missing *every* file from that git repo, you definetely should. Make also sure the manifest file that the readme tells you to create includes everything as shown! Check first if you are missing only some files... At the very least, you might just download the missing extract-files from that git repo.
Ciuffy said:
50? You sure? Have you tried using the -c option while syncing? My CM 12.1 source code is working and it's "merely" 25 GBs or less.
Anyway, if you are missing *every* file from that git repo, you definetely should. Make also sure the manifest file that the readme tells you to create includes everything as shown! Check first if you are missing only some files... At the very least, you might just download the missing extract-files from that git repo.
Click to expand...
Click to collapse
The problem was that I spelled the "local_manifests" folder wrong.
Now I have a "Samsung" folder in there.
Thanks
protruckker said:
The problem was that I spelled the "local_manifests" folder wrong.
Now I have a "Samsung" folder in there.
Thanks
Click to expand...
Click to collapse
Great! Have fun with your ported Cyanogenmod. Glad I could help.
We have a button dedicated just to thanks!