B2G/Updating: Difference between revisions

B2G/Updating (view source)

837 bytes added , 7 December 2012

23

edits

@@ Line 25: / Line 25: @@
 == Building updates for multiple software versions ==
-* build full update.zip and update.mar for every version
+* Initially, use the <tt>gecko-update-full</tt> target to generate a complete update MAR for the last successful b2g build. This will place the MAR in <tt>$GECKO_OBJDIR/dist/b2g-update/b2g-gecko-update.mar</tt>:
-* generating diffs
-* signing packages
+<pre>
+$ ./build.sh gecko-update-full
+$ cp $GECKO_OBJDIR/dist/b2g-update/b2g-gecko-update.mar <dest>
+</pre>
+* For a complete FOTA update.zip, use the standard AOSP build hooks:
+** Make sure the kernel binary is in the appropriate place under <tt>vendor</tt> to enable boot image, recovery image, and update.zip generation
+** Copy the update.zip that lives under <tt>out/target/product/$DEVICE/*.zip</tt>
+* To generate an incremental MAR update, you simply need two complete update MARs to generate it from. Pass their paths to the gecko MAR generation tool:
+<pre>
+$ ./tools/update-tools/build-gecko-mar.py --from $FROM_MAR --to $TO_MAR $DEST_MAR
+</pre>
+* TODO: generate FOTA incremental zip
+* TODO: signing packages
 * this doc covers "linear updates"; can generate more if desired