Confirm
4,378
edits
Changes
→Misc
* Other Useful tips for third party webapp dev:
** https://developer.mozilla.org/en-US/Apps/Build/App_development_FAQ#What_are_useful_commands_during_development.3F
== verifying patches before they land for gaia ==
From bug 1134649:
just to note, this is an example of one way to verify patches before they land on a branch: <br>
<br>
In order to verify that the patch works: <br>
# flash a flame with the latest 2.2 eng build
#*reason: to get the latest gonk/gecko ; engineering build as it has root access and simplifies things.
# git clone -b v2.2 https://github.com/mozilla-b2g/gaia.git v2.2_gaia_git
#*reason: need to get the latest gaia for v2.2, -b v2.2 signifies the branch; if you already have a gaia 2.2, then just do a "git pull" on it. v2.2_gaia_git is somewhat arbitrary. you can have a different name, just keep it consistent with the next line ( cd )
# cd v2.2_gaia_git
# git checkout -b fix-clock-load
#* reason: branch out to a different branch to pull the patch in in case we need to reuse this local repo; this also autoswitches you to that branch after creating the branch. you can verify with: git branch ; fix-clock-load is arbitrary. You can have it different like bug_1134649
# git pull https://github.com/mcav/gaia.git fix-clock-load
#* reason: need to pull mcav's fix; should be fine so long as he didn't make any changes on top of this fix in the branch. Otherwise you would have to cherry pick the fix. That might be a separate wiki entry...
# save the commit, if you're in vi then 'esc' :wq
#* reason : 'esc' key then :wq will save the commit, we just need to save a comment and the patch locally.
# MOZILLA_OFFICIAL=1 make install-gaia
#* reason: to build and install gaia on the device. This assumes that your flame device is connected, awake, no screenlocked and has adb access. MOZILLA_OFFICIAL=1 is only to brand it mozilla. There's no real need to do the MOZILLA_OFFICIAL=1.
== General Testing on Mobile devices ==
https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks_Part2
