792050 - Allow to precompile startup cache without omnijar'ing first

Status: RESOLVED FIXED

(Firefox Build System :: General, defect)

Comment 1

[Mike Hommey [:glandium]]

Attachment: Allow to precompile startup cache without omnijar'ing first

This refactors precompile_cache.js to use the resource protocol handler to get the gre and app resource locations, and import all modules and components that can be found in either the corresponding omnijar or directory.

This will allow, in bug 780561, to avoid a two-step packaging, and in bug 755724, to properly precompile cache for both browser and metro without too much hassle.

Comment 2

[Mike Hommey [:glandium]]

As a bonus, it also removes the import exceptions logs, which are confusing to many people looking at tinderbox logs.

Comment 3

[Mike Hommey [:glandium]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/572b3980300c

Comment 4

[Mike Hommey [:glandium]]

Backed out for pymake bustage.
https://hg.mozilla.org/integration/mozilla-inbound/rev/bf9c0d80b36e

Comment 5

[Mike Hommey [:glandium]]

Attachment: Fixup

Interdiff for a fixup to avoid the windows breakage. The problem was that MOZ_STARTUP_CACHE ended up with a path in the form e:/build/something, and NS_NewLocalFile barfs on these (because it expects absolute file names with backslashes).

Comment 6

[Mike Hommey [:glandium]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/305cace7ba51

Comment 7

[Ed Morley [:emorley]]

https://hg.mozilla.org/mozilla-central/rev/305cace7ba51