• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 Development (moved to upp)

to clarify, the ril files are still in place in the frameworks dir from our successful cm10 build, is that good?
 
[HIGH]Export includes file: external/webkit/Android.mk -- /home/superr/android/out/target/product/arthur/obj/STATIC_LIBRARIES/libangle_intermediates/export_includes
make: *** No rule to make target `/home/superr/android/out/target/product/arthur/obj/lib/libv8.so', needed by `/home/superr/android/out/target/product/arthur/obj/SHARED_LIBRARIES/libwebcore_intermediates/LINKED/libwebcore.so'. Stop.[/HIGH]
 
can someone PLEASE give us a working directory tree for the original warp??? i can do this, i just need to start from something that isnt broken in the first place
 
Well...not sure what to do now...sounds like you are coming to a standstill as well.
 
yep, my brain is fried, untill we can get some working source to begin with i cant really do anything
once we get the source to build for the warp we should be good but untill we can at least get that we are screwed
 
you could always ask that dm guy where to find the working version of their device tree or what is going wrong with the build process. he said hes got it and he did manage to make a build... if he has a device tree that works right for the warp i can modify it for us
 
i suppose we could build aosp instead. Far fewer features, but pure google isn't too bad :)
 
basically just someone please find me a working device tree, i dont care where it came from as long as it builds a usable cyanogenmod 9 or 10 for the warp. once i have access to that, it should only take me a day to get something booted
 
it says on the repo page:
Zte Warp Device Tree To build ICE CREAM SANDWICH using Pure Google AOSP Source -Non CyanogenMod.
 
and if it works out, i think you get the idea of how to modify it for our phones, go to town. just gotta make sure partitions are correct, pixel sizes are changed, kernels are replaced, things like that
 
it stops right at the beginning with:

build/core/product_config.mk:209: *** No matches for product "cm_arthur". Stop.

need to go pick up my girl. Be back in about 20.
 
the man himself, thanks btw for your work on your original device tree, without that we could have never gotten cwm working. but yea basically we are trying to find a working cm9 or 10 device tree for the warp 1, then i can adapt it to the warp 2. because otherwise im pretty well lost
 
we have a broken copy of the arthur cm9 tree with our files and settings injected into it, but it wont even build as is. we know what we need to change basically we just dont have anything we can change it on and come up with a successful build
 
You must log in or register to reply here.
Back
Top Bottom