Le 11/01/2016 19:28, [email protected] a écrit : > Hi, > > When building FxOS, how/where's the logic that dispatches the resulting files > into the various boot.img, recovery.img, system.img, ... files. Can it be > overridden?
That's not B2G specific, this is Android build system magic. You need to play with the modules stuff in makefiles. Have a look at gonk-misc/Android.mk for example, that will give you a good short example of code being put to boot and system partitions. [...] > > Out of curiosity, this reminds me bug 1085230 - [Flame] OTA needs enough > /system space to update [2]. Since Flame also has custpack partition, I was > wondering if using it (and making symlinks from system to custpack like in > Fire E) would have been a viable alternative to increasing the size of system > partition? I don't know what you mean related to custpack. The trick on this topic was that there was some empty space in the GPT partition layout (defined by gpt_main0.bin) so we could move the starting (or the ending, I don't recall precisely) of the system partition. Now, you need to be 10000% sure that you have exactly the same layout. How did you checked the partition layout of Fire E ? Does that does to being close even in term of partitions sizes, starting/ending blocks? > > Thanks, > > Émeric > > > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1085230 > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
