+1 much needed! I'd also like to plug an alternative approach to the discovery problem. Awhile back I wrote a module that extends the mach module in the B2G repo: https://github.com/ahal/b2g-commands
It adds mach commands that basically just wrap the existing shell scripts. So e.g instead of `MOZ_DEBUG=1 ./build.sh` you could run: ../mach build --debug The nice benefit about this is you can run `./mach build --help` to see all of those hidden environment variables in a help message. It does the same thing for `config.sh`, `./repo sync` and even introduces some new goodies like `bootstrap`. Currently only a very small handful of those hidden environment variables are actually exposed via cli argument. But I can add more if people find it useful. Also if anyone wants to work on improving this, patches are welcome, or I'd even transfer ownership as I don't have a lot of time for it lately. Cheers, Andrew On 26/05/15 11:42 PM, Naoki Hirata wrote:
Hey all, A few of us were talking and thought having a sheet that says what the build variables are and what they do, and how they change things ( like VARIANT ) would help out a lot. Having a cheat sheet might be handy. We started : https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS/B2G_Build_Variables_Reference_Sheet If you wouldn't mind, could you add to the sheet if you happen to know some of the variables and can explain what it does? It could help open eyes to some build variables that other devs might find handy. After all, sharing is caring. :) Regards, Naoki
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
