Re: 4.4 KitKat?
but initialize your repo to this: git://github.com/androidarmv6/android.git -b cm-11.0
In the base directory there'll be a hidden directory called .repo, make a directory in .repo called local_manifests. Any xml manifest file in this directory will be used to sync along with the main source. This is the 'new' way. The old way was to use a single file in .repo called local_manifest.xml. I made a file in this directory called thunderc.xml that tells repo where to sync the device specific folders for thunderc from. I used the cm10.2 branch from TheJBC. Then when you run "repo sync" the device specific folders will be synced along with the cm11 source code. They say you need about 35 gb of disk space to build android, I think the source is around 10 gigs and the build generates a ton of intermediate object files etc. in the BASE_DIR/out directories. The full source includes extra stuff like the android sdk, you end up building stuff that's not really necessary to make a rom, I don't know how to weed that stuff out yet. There's good instructions for porting TWRP in a thread on xda, I'm thinking about trying to port that. A couple of guys in the p500 thread that thewraith420 mentioned were able to get cm11 flashed and booted using twrp. Unfortunately I bricked my OV the other night so I'm waiting on a new (used) one from ebay right now. I was messing around inside the broken recovery and managed to trash the system partition while attempting to mount it from the recovery. Luckily I got another one for $1.50(!) + shipping so it wasn't too bad a loss. I'd say hacking recoveries is risky though. The "build TWRP" thread tells how to build for the sdk emulator so you can experiment more safely. You're probably going to want to max out your ram and have plenty of disk space. You should add extra swap space as well, maybe 6 or 8 gigs?
Use the info on this page: How To Build CyanogenMod Android for LG Optimus One ("p500") - CyanogenModI'm having problems figuring out how to download a repo ( I read to much info, in to many places, brain is now locked up). What repo are you using? Could you post code to download that repo? I see there is version 1.19 and 1.20
Maybe I'll try to build the latest Touch Screen ClockworkMod recovery (6) if that would help installing Kit Kat. I would then need the CyanogenMod repo I guess?
EDIT: I noticed that RAM and swap space are important, but how much hard drive space is really needed? I might need to upgrade the hard drive to something larger and get two 2GB RAM sticks (my system is expandable up to 4GB).
but initialize your repo to this: git://github.com/androidarmv6/android.git -b cm-11.0
In the base directory there'll be a hidden directory called .repo, make a directory in .repo called local_manifests. Any xml manifest file in this directory will be used to sync along with the main source. This is the 'new' way. The old way was to use a single file in .repo called local_manifest.xml. I made a file in this directory called thunderc.xml that tells repo where to sync the device specific folders for thunderc from. I used the cm10.2 branch from TheJBC. Then when you run "repo sync" the device specific folders will be synced along with the cm11 source code. They say you need about 35 gb of disk space to build android, I think the source is around 10 gigs and the build generates a ton of intermediate object files etc. in the BASE_DIR/out directories. The full source includes extra stuff like the android sdk, you end up building stuff that's not really necessary to make a rom, I don't know how to weed that stuff out yet. There's good instructions for porting TWRP in a thread on xda, I'm thinking about trying to port that. A couple of guys in the p500 thread that thewraith420 mentioned were able to get cm11 flashed and booted using twrp. Unfortunately I bricked my OV the other night so I'm waiting on a new (used) one from ebay right now. I was messing around inside the broken recovery and managed to trash the system partition while attempting to mount it from the recovery. Luckily I got another one for $1.50(!) + shipping so it wasn't too bad a loss. I'd say hacking recoveries is risky though. The "build TWRP" thread tells how to build for the sdk emulator so you can experiment more safely. You're probably going to want to max out your ram and have plenty of disk space. You should add extra swap space as well, maybe 6 or 8 gigs?