yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] gnarlyc:
1) Install Debian or Ubunutu Linux. This does not have the same requirements as dsixda's kitchen.

2) In fact, please correct me if I'm wrong, but you'll need to install a 64-bit Linux to build CM7. Maybe someone has worked out a work around for that, but I haven't heard.

3) More devices would be great. Party on! Let us know how it goes after you try it under linux. We'll be glad to help.
[Droid Eris Android Development] IzaacJ:
Well, could do that, but I'm not that good with linux, but I've been using Ubuntu a few times.

And as far as I know, either JDK or android SDK work on x64 Ubuntu, dont remember which one it was... Or has that changed? Been about a month since I checked last time.

EDIT: wouldn't it be easier to modify your Android Builder to include other sources? As I'm using dsixda's htc android kitchen, and AB is a plugin :P
[Droid Eris Android Development] gnarlyc:
The JDK and SDK should both work fine on either 32 or 64 bit Ubuntu. According to these pages, only Linux and Mac OS X are supported for building AOSP or CM from source.

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

http://wiki.cyanogenmod.com/index.php?title=Building_from_source

If you have it working under Cygwin, that's great! I'd love to see a list of packages that you had to install to get it to work. I've half hardly tried before by installing the listed packages as best I could, but it never quite worked.

Honestly, I have yet to build GB AOSP or CM7 myself. I've just been busy with other things. When my current class is over in May, I'll probably catch up, if not before.

Would it be easier to modify AB to add other sources? Hmmm. You could do that. ED is already setup to pull CM code though. To add another device, you should be able to replace the vendor tree and kernel code with yours. And AB doesn't have to vendor tree code in place. I'd think no, in fact. If you are pulling CM code, I'd use ED. That's just me though. Do what you feel is best. If you want to try and get ED to work in Cygwin, the needed packages are listed in the thread and in the code.
[Droid Eris Android Development] api1996:
I realize this is a little old but i cannot get this to work. My problems begin with: "line 95: repo: command not found". I have read through this thread but i dont completely follow how people got around this. I dont even have an out folder that the rom is supposed to end up in. I also have a lot of "file not found" errors because for some reason the directories that they are supposed to be in have not been created. Can someone please help me get this to work or can someone post their plain compiled cm rom from this? I really want this to work.
[Droid Eris Android Development] Conap:
Your error looks like it's not installing repo...repo installs and then repo sync's the cm source...untill you get the cm source nothing will build and there will be no out folder. If you just want the plain cm rom that you would get from this then you can use celb froyo because this uses the same source code as my rom so the result will be the same. If you are more interested in getting this to build then you need to see why repo is not installing. Are you running the script as root so the dependencies get installed?
[Droid Eris Android Development] api1996:
I'm putting sudo before it. Should I use su at the beginning instead? Does the script install repo or do I have to do that manually?
[Droid Eris Android Development] Conap:
sudo is right...the script should install it itself....you can look on your pc in folder Easydev/bin/ and see if the repo file is in there.
[Droid Eris Android Development] api1996:
It is in there. So why isn't it working?
[Droid Eris Android Development] Conap:
maybe permissions weren't set up correctly on the file...you can navigate to Easydev/bin in termainal and do chmod a+x repo ...that will set the permissions right on the file. Then go back to Easydev/ in your terminal and try :

repo init -u git://github.com/CyanogenMod/android.git -b froyo

if that gives no errors you can then try:

repo sync

That will pull the files for the cm source. If all that works then try running the script again. It should give your error in there somewhere though.

Edit: These are just the lines in the script that you are running. I was just having you do it by hand to try to narrow down where the problem is. I'm sure gnarlyc would have your problem fixed by now if he were on.
[Droid Eris Android Development] gnarlyc:
Check your $PATH variable. There was a bug in v6 that is fixed in v7. You can manually fix it until v7 is released. Sorry for the delay.

export PATH=$PATH:/path/to/repo
[Droid Eris Android Development] Conap:
see i told you he would know what to do!!!!
[Droid Eris Android Development] api1996:
Thanks guys it worked! Finally! It was the path variable that was causing my problems.
[Droid Eris Android Development] gnarlyc:
Glad to hear it.

I started serious testing of v7 today. So, have you been able to sync and compile CM6? I've had some issues that appear to be repo issues, so my thinking is to just move to CM7 instead. That's unfortunate, because I like for people to have options.
[Droid Eris Android Development] Treken:
First off, when I came across this thread I was impressed that someone would take the time to make a tool for making rom compiling easier. second, you want to make options for people, which I also thought was really cool. Now for the question of the day...i know this tool is for the droid eris, but it would be great to use it for the droid incredible. I'm a noob with compilation so if I need to change the github source and some other commands as well, which ones do I change? I hope I'm not detracting too much from the o.p.
[Droid Eris Android Development] workshed:
What, no v7 yet? i did all that hard work for nothing? lol :eek::rolleyes:;)

Watch how fast repo sync is now :D BAM!
[Droid Eris Android Development] Team ADX:
If your device is in the officially supported CM list, it shouldn't be too hard to mod v7 of the script. Don't change the repo URL. Change the lunch command and probably what the existing ROM gets named to.
[Droid Eris Android Development] Treken:
I hate to sound stupid, but what is the lunch command?
[Droid Eris Android Development] gnarlyc:
Read this: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Incredible

That page actually doesn't say to use lunch... Funny. EasyDev is based off of the instructions for CM6. Apparently, they've changed a little in CM7 and we didn't catch up. It works though. I'll look at that later, if workshed doesn't beat me to it.

To answer your question though... Lunch is used to select the device that you are building for. It either gives you a menu of available devices or you can specify the one you want when you use 'lunch'.
[Droid Eris Android Development] CondemnedSoul:
That's the standard command to give the old lady at approx. 11:30 AM :) lmao
[Droid Eris Android Development] Treken:
too funny! I use that one myself from time to time. Just hope I don't end up calling poison control for over use of that command!
[Droid Eris Android Development] Treken:
Thanks Gnarly!
[Droid Eris Android Development] workshed:
lunch is a cmd you doing after you source . build/envsetup.sh that gives you a list of supported devices to build. This is all auto in the script.

to build for the inc, you could essentially find this code in the script..

LINE: 149

and change it to...

or just change it to...

with just 'lunch' the script will stop and give you a menu of the available devices to build for. the other way will just pick the incredible for cm and start building.

This hasn't been tested at all for any devices other than the Eris, so try at your own risk :)

EDIT: Man, I was slow on this one lol, sorry ;)
[Droid Eris Android Development] Treken:
I really appreciate how helpful you guys are! Makes me wanna go out and buy an Eris! The incredible community seems a bit reclusive when asking for help.
[Droid Eris Android Development] Conap:
I have an incredible...just haven't gotten around to doing alot of dev work on it. I don't always have time to read the inc forums so if you really get stuck on something and can't get help over there feel free to pm me....
[Droid Eris Android Development] roirraW "edor" ehT:
We're adopting but you probably won't like the hazing ritual! ;) Just kidding. LOL.
[Droid Eris Android Development] morrisdan:
Nightly Build

Great job guys. Can't wait to fire up my Ubuntu VirtualBox and modify the script for a nightly build for my ERIS and Incredible. Looking forward to getting back to using it again. Thanks once again.
[Droid Eris Android Development] Treken:
Lol. that's ok, I'm wearing a football helmet and jock cup. I'm good to go!
[Droid Eris Android Development] morrisdan:
It worked flawlessly with Ubuntu 64 bit in VirtualBox on an iMac.

So is this building Workshed's GSB GingerBread ROM with just the latest CM7 source or is it a little different?

If I modify for the Inc. wouldn't the proprietary files be different though for the Inc? I realize I would not use the GSB ROM to pull the files from but the file list that are proprietary would be different too?

Super exciting you guys updated EasyDev.

Thanks.
[Droid Eris Android Development] Conap:
yes you will want to use the unzip-files script that's in the inc folder of the cm source....this has not been tested but I "think" that if you just take the script and replace every line that says desirec and put inc instead then it should work for the incredible. Just make sure you use an inc rom to pull the files from.
[Droid Eris Android Development] workshed:
stupid script is fixed, enjoy.
[Droid Eris Android Development] Treken:
If you get it modified for the inc, can you shoot it to me via pm? I don't trust myself with scripting for rom compilation yet.
[Droid Eris Android Development] Treken:
What files am I supposed to pull from the inc rom? Also, this is done via terminal will you adb phone? and if so what command must one issue to pull the needed files?

I read in the script where you place the rom in the Kitchen directory. Is this the same directory where you have the EasyDev script residing?
[Droid Eris Android Development] Conap:
if you change all the desirec's to inc then it will run the script to pull the files automatically. You can either put the rom in or plug your phone in and using adb it will pull them off the phone. If for some reason you have trouble getting the script to automatically pull the files you can navigate in the terminal to pathtothesource/device/htc/inc and then run ./extract-files.sh with the phone plugged in. Again though if you have changed all the desirec's in the script to inc it should do this all for you and put them in the correct places. It's best to do this with a cm rom or with cm loaded on your phone.
[Droid Eris Android Development] Treken:
nvr mind! I figured out this stupid question. But..vvv
[Droid Eris Android Development] Treken:
I edited the script. Here is the pastebin. Can someone just double check to see if I did it right? http://pastebin.com/CTZFBqTZ
[Droid Eris Android Development] Conap:
looks fine at a glance....only one way to find out is to run it though!! Good luck.
[Droid Eris Android Development] Treken:
Thanks Conap! I'm currently doing a fresh install of ubuntu 10.10 on a new HDD and will give it a whirl. This builds the environment as well? Or will I need to do that first?
[Droid Eris Android Development] CondemnedSoul:
Just thought I'd let you know in case you don't already. This does work fine on Linux Mint 10 as well ;)
[Droid Eris Android Development] Conap:
This should work on a fresh install. It should add all packages needed.
[Droid Eris Android Development] Treken:
Ok. Thanks!
[Droid Eris Android Development] morrisdan:
Looks like EasyDev-v8 asks which phone you have. I just tried it and selected the Inc. But I still had my ERIS ROM in the root of my folder. I better go download a Nightly Build for the Inc and drop it in there instead so it'll pull the proprietary files from an Inc ROM and not the ERIS. Now this looks even more exciting. I'll let you know what happens.
[Droid Eris Android Development] Treken:
Cool. Thanks!
[Droid Eris Android Development] Conap:
yes easydev8 does have the option...there is a small issue we are ironing out though. The inc vendor tree does not have the script in it to extract the files from the rom. Instead of putting a rom in there just make sure your phone is plugged in and it will pull the files from there instead. This is the way i do it anyway cause it just seems easier to me.
[Droid Eris Android Development] workshed:
lol... well I guess we'll be moving this out of the Eris dev section soon :D ;)
[Droid Eris Android Development] Treken:
I successfully started esaydev but it gave me an error. Can someone please look at my log file and see what I did or didn't do? Here's the pastebin link: http://pastebin.com/fELarUp6

I'm running Virtual Box with Linux 10.10 on it. My host os is Windows 7 Ultimate on a 32 bit machine. I also had my phone plugged in before I began the process.
[Droid Eris Android Development] gnarlyc:
"

E: Unable to locate package lib32z1-dev
E: Unable to locate package lib32ncurses5-dev
E: Unable to locate package lib32readline5-dev

./easydev-v8.sh: line 136: curl: command not found

The first thing that I would do is install those manually. Since ED didn't get them installed for some reason, not having them could cause the other issues.
[Droid Eris Android Development] Treken:
going to be working 7/12's for the next few months. My time is spread really thin. I need to make sure I'm not wasting what little of time I do have. I had installed ubuntu 10.10 on virtual box with windows 7 ultimate as the host. I noticed it's really lagging. I might do a wubi install istead or maybe partition for mint 10. I want to be productive and see some fruit from my labor so can you give me a recommendation so I can be solid when I try EasyDev script again?
[Droid Eris Android Development] morrisdan:
Kernel

So if I get this working with my Inc. where does it pull the Kernel from. I'd like to have it use [KERNEL] 2.6.37.4-incredikernel-03/18/11 if possible. Or does it only use the default CM Kernel? It looks like he has it out there on GitHub.
[Droid Eris Android Development] workshed:
Yes, it will use the stock cm kernel that is in the cm repo for inc.

you can package the other kernel you want to use pre-build, but repo sync will yell at you for not commiting the change before you do a repo sync.

so you can either replace the kernel in device/htc/inc and the module for wifi in device/htc/inc/modules then commit them so repo sync will still work and then compile.

OR, you can add the boot.img and the module for wifi (for the custom kernel) after building and then run squisher again to optimize and sign, done :D

if you'd rather add it after build, just go to out/target/product/inc/ delete the update-cm7-inc-kang-bla.zip and open up the other zip (cyanogen_inc-ota) and replace the boot.img and module for wifi with your custom ones and run squisher.

vendor/cyanogen/tools/./squisher

that will optimize and sign the zip, ready to flash, this will give you the update-cm7-inc-kang-bla.zip

you can rename the zip to whatever you want after.

Hope that makes sense :D

NOTE: With all that said, you could always just flash that kernel after you flash the rom, have a full boot, then reboot to flash the kernel.
[Droid Eris Android Development] api1996:
After successfully using v6, I figured I would try v8. Everything was working well for a while, then I started getting various errors, and I don really know what went wrong. Here's a pastebin: http://pastebin.com/Zk99k7rH

Hopefully someone can help me work this out.
[Droid Eris Android Development] morrisdan:
With my limited dangerous knowledge I better stick to flashing the Kernel afterward. Thanks for all the info though.
[Droid Eris Android Development] Conap:
Schedtool is not being installed. The script should install it but for some reason it is not. You can install it by running in terminal:

sudo apt-get install schedtool

then restart the script.
[Droid Eris Android Development] Treken:
After running the script in mintlinux It goes through the whole compilation and at the end I get: make: *** No rule to make target `vendor/htc/inc/proprietary/libcamera.so', needed by `out/target/product/inc/obj/lib/libcamera.so'. Stop.

make: *** Waiting for unfinished jobs....

Note: Some input files use or override a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

Your ROM should be in /home/treken/EasyDev/CM7/out/target/product/inc

I looked in the target folder but no rom. a system folder with build prop, obj folder, root folder, clean steps mk script, previous config mk script. Any ideas?
[Droid Eris Android Development] morrisdan:
In my limited knowledge of syncing with Cyanogen when they change the slightest thing on their end we get hosed. I am having a feeling there is a problem on their end but Shed and Conap could probably confirm this. I am having the same problem. I could not get the script to finish yesterday either. It was stopping at difference places in the script. I deleted my VirtualBox Image and am starting fresh again today.
[Droid Eris Android Development] workshed:
Make sure you have your phone plugged in when you run the script incase you forgot.

Make sure libcamera.so is in this dir: vendor/htc/inc/proprietary/libcamera.so

It MAY be cm repo got fubared, you'll have to try that, or wait and try again later and see if it was on cm's end. Usually that error means we don't have make files to build libcamera.
[Droid Eris Android Development] Treken:
Ok, thanks. I'll try again when I get a chance
[Droid Eris Android Development] api1996:
Ok, I did that but still i get tons of errors and no rom in the out folder.

I noticed that in the beginning I get an error:

Note, selecting 'libsdl1.2-dev' instead of 'libsdl-dev'

E: Unable to locate package lib32z1-dev

E: Unable to locate package lib32ncurses5-dev

E: Unable to locate package lib32readline5-dev

I have tried installing those manually but it just says unable to locate package.

Edit: I was able to get those packages to install by changing the "lib32" part to "lib64", but there are still errors and the rom is not built. Here is a pastebin: http://pastebin.com/LCNPT4CC
[Droid Eris Android Development] gnarlyc:
You might need to do this:

add-apt-repository "deb http://archive.canonical.com/ maverick partner"

If that works, we'll add it to EasyDev.
[Droid Eris Android Development] api1996:
Just tried that, still didn't work. Here's what I got: http://pastebin.com/zVqnKjGg
[Droid Eris Android Development] morrisdan:
EasyDev worked great that day that v7 was released. Since then I have not been able to get it to work. I'm thinking it's something on the CM end of things. Has anyone had a successful build in the last couple days since CM 7 final.

Heres what I get:

target Strip: copybit.msm7k (out/target/product/desirec/obj/lib/copybit.msm7k.so)

Notice file: hardware/msm7k/libcopybit/NOTICE -- out/target/product/desirec/obj/NOTICE_FILES/src//system/lib/hw/copybit.msm7k.so.txt

Install: out/target/product/desirec/system/lib/hw/copybit.msm7k.so

target thumb C: gps.desirec <= hardware/gpsshim/gps.c

make: *** No rule to make target `vendor/htc/desirec/proprietary/libgps.so', needed by `out/target/product/desirec/obj/lib/libgps.so'. Stop.

Your ROM should be in /root/Documents/EasyDev/CM7/out/target/product/desirec
[Droid Eris Android Development] CondemnedSoul:
I ran easydev v7 yesterday evening. Around 5pm est on linuxmint with no problems at all.

Haven't used v8 at all though..
[Droid Eris Android Development] Conap:
it seems to be having trouble finding the libgps.so in the proprietary files. This should have been pulled from an existing rom when running the script. Make sure you have an existing rom there for it to pull from or have your phone plugged in to pc so it can pull from the phone.
[Droid Eris Android Development] gnarlyc:
What version of Ubuntu are you using? Also - 32 or 64 bit?
[Droid Eris Android Development] api1996:
Ubuntu 10.10 64 bit wubi installation
[Droid Eris Android Development] morrisdan:
For the ERIS build I went back to EasyDev-v7 and used GSB.v2.7-CM7.0.0_RC4_STABLE.zip for the ROM to pull the proprietary files from and I got a successful build. Now back to playing with the Inc. build.
[Droid Eris Android Development] Conap:
oh if you are building for the incredible you will have to plug your phone in to let it pull the files from there. You can't use a prebuilt rom to pull files for inc because the inc cm dev does not have an upzip-files.sh in his tree. You don't need to do anything else besides plug the phone in through usb though when running the beginning of easydev. Once the script starts actually building the rom you won't need to leave the phone connected anymore. Only need to have it connected during the part where it says it's going to unzip the prebuilt rom.
[Droid Eris Android Development] morrisdan:
USB and VirtualBox

I finally got USB working through VirtualBox on OS X so I could pull the proprietary files from the Incredible. Had to create an empty USB filter in settings before launching the VirtualBox image. ADB now sees my device. That only took half a day. Now on to roll my own with v8.
[Droid Eris Android Development] morrisdan:
ADB and proprietary files

I am not getting the script to pull the proprietary files through ADB.

I get ./extract-files.sh: 21: adb: not found

Was I supposed to have ADB setup first myself or does the script do that too?

When the ADB command is ran in extract-files.sh should the adb command be ./adb so it gets executed.

If I copy ADB from the the SDK in there and change every line in extract-files.sh to ./adb it works.
[Droid Eris Android Development] Conap:
no the script does not set up adb...guess that's something we should put on the todo list. You shouldn't need to change the script though. You probably just need to add the sdk/tools/ or wherever you have adb at to your path. There are some pretty good guides on xda on setting up adb with linux.
[Droid Eris Android Development] morrisdan:
Linux ADB Setup

As posted in this thread:

http://xdaforums.com/showthread.php?t=537508

I just added the following to .bashrc and now the ADB command works from anywhere.

#AndroidDev PATH

export PATH=$PATH:/root/Documents/android-sdk-linux_x86/platform-tools

We be good now.
[Droid Eris Android Development] Conap:
Awesome...glad you got it working....thanks for posting the link to that guide also....
[Droid Eris Android Development] morrisdan:
Pulling Proprietary Files from Inc ROM

Hope I can explain this ok.

After reading the merged changelogs at Cyanogen it looks like the proprietary files changed enough to where I needed to grab them from my phone again but I remote into my computer at work to run my whole Ubuntu setup so I was determined to get EasyDev to pull the proprietary files from the last stable release of Cyanogen zipped file.

http://review.cyanogenmod.com/#change,4680

So I looked at how you guys did it for the ERIS and looked at what files get pulled through ADB for the Inc then just used those references and made an unzip-files.sh for the Inc and ran it and it grabbed them from a the last stable CM Inc ROM. Then ran EasyDev again and it worked fine and flashed and it works.

Does this sound like it should have worked?
[Droid Eris Android Development] gnarlyc:
Yes. You just made an unzip-files.sh for the Inc. Good work! I much prefer the unzip-files.sh to extract-files.sh, but everyone is different. (Probably because I also do most of this work in a VM on my workstation at work...)