Hi,
I landed bug 780561, which replaced a bunch of awful Makefile goo around
a perl script (and a few other things) with a quite well unittested python
codebase.
While it doesn't affect everyday development, and doesn't change the
Firefox, Firefox for Android and B2G tinderbox builds much, there are
three noticeable changes that do affect third parties (Seamonkey,
Thunderbird, Bluegriffon, Sunbird and others):
- MOZ_CHROME_FILE_FORMAT/--enable-chrome-format is still used to
select the chrome format for the packaged application, but what is
installed under dist/bin is now always as if MOZ_CHROME_FILE_FORMAT
was flat or symlink (depending on the platform). It was already the
case for MOZ_CHROME_FILE_FORMAT=omni, it now is also the case for
MOZ_CHROME_FILE_FORMAT=jar. MOZ_CHROME_FILE_FORMAT=omni is
recommended, though. If your application is hooked under the mozilla
tree and you're using --enable-application=path flag to enable your
application code (like Sunbird or Bluegriffon), you should't need
changes. If your applications lives outside the mozilla tree (like
Seamonkey or Thunderbird), you may need changes to your build
system. See bug 825872 for the comm-central version of this.
- The way universal builds are done for Mac changed in a way that
requires changes for applications living outside the mozilla tree
(like Seamonkey or Thunderbird). Refer bug 825872 for that as well.
- The way manifest files are created for chrome and component registration
is different, and some manifest file names changed. This means some
adjustments to removed-files.in can be necessary. These adjustments
have landed for Firefox, Firefox for Android and B2G, but third
party applications may need to do these changes on their end.
Other than the above, any breakage to "make package"/"make install" are
unexpected and you are welcome to file bugs under Core::Build Config about
any problem you can have with the new codebase.
Something else worth noting: the new packaging code does preprocessing
on its ends, so you may want to remove the rules preprocessing
MOZ_PKG_MANIFEST_P into MOZ_PKG_MANIFEST, and define MOZ_PKG_MANIFEST to
point to the file to preprocess.
Cheers,
Mike
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
