Michael Trimarchi wrote:
> I send all the patches one month ago and write the ril for freerunner,
> I never seen
> any patches agaist the ril and I work alone in that direction. I stop
> to push my changes
> on git because there are not people work on it but use it. My patches?
> I send patches on the kernel, and the android changes are few things
> that I have posted. The code is android and nothing else. Porting my
> changes on cupcake
> just require one day, because I'm working on other stuff and not just
> on android. Everyone
> can fix somenhing on different part on android, I just changes few
> things on it. The different
> is the kernel and the ril. Koolu decides to use Sean McNeil code and
> I'm very happy and I provides patches agaist that repository when I
> have time and continue to change my version.
>
> Michael
Well, propably because it's quite hard to build the whole thing?
I'm using an altered manifest.xml, checked into a local git,
"../tools/repo init -u ../manifest -b master -m manifest.xml", alter
./build/core/prelink-linux-arm.map, change references to the old ril,
build it, mount your image to get your altered init, get all the ugly
scripts to build a system image, clean stalled sdcard cache files (I've
missed that one), see what's broken.
Or did I miss some other unreleased parts?
Oh, plus the koolu manifest doesn't work. It's currently broken. So a
full manifest.xml rewrute is needed.
I'm trying (again) to rebuild a manifest.xml around the
android.git.kernel.org version, alter it with koolu repos and your repo,
but I wouldn't expect any results except another 3h wasted.
I'm wondering how anyone is able to release something within such an
environment.
Regards,
RT
_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
