Just a quick note: Open C and Flame are still new devices and that's
probably why the documentation is lacking a bit.
Adrian is right about the fact that there is technical debt in the build
system: it mostly works for our needs and so not much love is devoted to
it right now.
Thanks for the good feedback anyway !
Le 07/06/2014 01:06, LazerUnicorns Developers a écrit :
Hey all,
I have to say it's really hard to get started with building FirefoxOS
by yourself. It's pretty impossible for a newbie in B2G development.
Here's my feedback after around 10 hours of trying to get started -
with no success at all.
I mean, modifying and fixing the build setup is pain. You founded a
repo for the config and setup stuff (B2G), why splitting up everything
in b2g-manifests then? After 10 hours of googling all the information
together ... other developers won't invest that much time to get
started on development. Just sayin'.
1. I had to find a gist file that was building FirefoxOS 1.2 to find
out the dependencies. I modified it in order to properly build v1.4
(which I still haven't getting managed to do). The gist is available
at the following link. I build everything on Ubuntu Trusty Thar (14.04
stable) inside a VirtualBox VM in order to not fuck up my usual
Android build system.
Note: I'm still using the original B2G repo, but I need to fix that
stuff - so I forked it together with the b2g-manifest repo.
https://gist.github.com/martensms/a057224797238239ea99
2. Why are the Android building dependencies included for Darwin if
you can build it only on Ubuntu anyways?
3. The manifest files are out of date. I can't get anything built due
to the missing tinyxml / tinyxml2 repositories that are not existing
(base-caf-jb.xml manifest file). So in order to fix that, I had to
fork your repositories to get it run properly. That sucks hard if you
haven't built anything at that time and you have no idea what to do as
a newbie.
4. The wiki entries suck. No offense, but it's pretty impossible to
gather all Compiler Setup instructions there. I own a ZTE Open C
device, I had to google 15min just to find out that its codename can
be "treated as flame" after using the Unlock tool that only runs on
Windows that wasn't working anyways. I then had to use fastboot to
unlock, because I realized the bootloader was capable of installing
files via adb pushes ... no docs at all on the wiki / MDN pages /
google results?
Problems and Questions:
========================
- Why are all the necessary configurations not hosted in a single
(namely the B2G) repository?
- How can you build a "flame" variant properly?
- How to overwrite the repository with the correct one in the manifest
file? (I have no clue of the repo manifest files)
===========
= TL;DR LOL =
===========
config.sh call fails due to repo sync errors; here's the output
(warning, huge txt file!):
https://gist.github.com/martensms/011a7e4bd3646528ab69
Need to fix the tinyxml2 repository, how can I do that in the manifest
files?
Cheers and many thanks so far,
CM
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
