First of all, there needs to be someone who’s able to produce a bootable image. If this is achieved, there will still be a lot of work to make this image usable. As I said before, I’m not a CM-dev, but I guess, depending on how many people are working together, this can take up to a few months. Until this point it doesn’t make sense for a “normal user” to install these images anyway.
If the port gets into a usable state it is possible to submit it as an official CM port. Once it gets accepted, the images will get hosted by CM and get published on the download page.
I don’t know if they are acting in a legal gray area, but apparently they are hosting the images…
But unfortunately the hard work needs to be done first, before discussing the possibility where to download the result.
Edit:
Out of curiosity I wanted to check whether the images from the CM download page contain blobs or not. They do! You can download a python script from github to access the file system of the images. The latest M8 image for example contains the files listed in common-proprietary-files.txt, linked in my previous post.
Just trying to revive the thread, Juan Gomez (atilag) from Mozilla did a blobfree Firefox OS (B2G) compilation for the FP2 which extracts blobs from the device before packing the fastboot images.
Due to the similarities between the build processes of CyanogenMod and B2G, because they share the same low level base of Android, I think a port of CM to the FP2 is viable, with the B2G port as an example.
Now we have some right things to continue the @keesj’s initial work on the CM12 port. My machine is pretty slow, but, damned, I prefer having it burned down than not trying anything!
Edit: CM Recovery successfully compiled, Edit2: flashed. It works, yay! Edit3: I’ve done a new extract-files.sh that seems to extract blobs, at least. I’m kind of improvising… never cooked roms before. See it here. Edit4: I tried a full CM12 build today. Failed, of course, a lot of things have to be adjusted. I talked with Juan (I know him from some Mozilla meetups, and he has experience with CM ports) for generating an up-to-date blob-list. This is going to be funny, but slow. Should someone wants to help, message me,
My post? I don’t think it should. I could have explained myself bad, but I’m trying to build CyanogenMod, not B2G. The FxOS/B2G mention is because it is based on (the low level layer of) Android and both build processes have similarities (one being the blob dependencies to fully work).
I hope more peple who are able to work on a CM port will help you and push it further. I don’t want to lose CM when switching to a FP2, so I rely on guys like you and I want to thank you for your initial work here.
Linkage errors are really hard to debug…
Best scenario, you just missed a compilation flag on the command line, or you don’t use the correct compiler.
If not, then… go on the code and try to understand why it is not working… But with this kind of code, it’s seems pretty hard.
BTW I am really interested to help building a CM image, but I don’t really have lots of time and I never cooked roms. I will try to dive into this topic and free 50Go on my Debian
[quote=“NicoM, post:70, topic:10399”]
Linkage errors are really hard to debug…Best scenario, you just missed a compilation flag on the command line, or you don’t use the correct compiler.If not, then… go on the code and try to understand why it is not working… But with this kind of code, it’s seems pretty hard.[/quote]
I’ve not much experience with big builds nor C/C++ matters. I’m on Debian Testing, but seems like I’ll need to move to Ubuntu for this… which means I’ll have to set up a VM and compile time will increase,
Me neither! Hahaha. Come and help, I’ll appreciate it,
Maybe someone can wiki-fy the first article and add an up to date howto (what to checkout, how much space will be needed … ) and current problems, so that more people will try it? Most stuff can be copied from the old howto, I assume.
Cyanogen Inc. is chopping its staff after its for-profit alternative Android (Cyanogen OS, based on non-profit, community made CyanogenMod) has failed to catch on with phone makers.
CyanogenMod is a community effort and it doesn’t depend on Cyanogen Inc. nor Cyanogen OS.