On Monday, 2 December 2013 06:45:20 UTC+1, Andreas Gal wrote: > For security updates its critical to not develop a diverging zoo of Gecko > binaries. Originally we had one binary that was bit-for-bit identical on all > devices. We at some point reduced that constraint to binary-identical for all > devices with the same gonk version (ICS vs JB etc). Anything beyond that > should be detected by reading props the OEM can set. Please don't further > fork Gecko on a per-device basis. It would dramatically worsen our security > story.
So how does that work for different CPU types? I'm currently trying to port B2G to the HTC Wildfire which has an armv6 CPU. As far as I can see, the Gecko config happily ignores that and tries to compile for armv7. Even if that build would finish (it fails at some linking right now), the resulting binary would just not run on the device. What's the recommended approach in this case? Regards, Felix _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
