In the old build system extensions would be expanded under dist/bin/distribution/extensions but they currently being put under dist/bin/extensions This means that when a new user starts the application they do not have the extensions and they do not show up under Extensions in the Add-ons Manager. The code that does the expansion starts at: http://mxr.mozilla.org/comm-central/source/mozilla/config/rules.mk#1361

I did look at potentially using DIST_SUBDIR but that also changes FINAL_TARGET in config.mk and I think it is not the intended use of DIST_SUBDIR.

Comment on attachment 8466763 [details] [diff] [review] Proposed fix [Checked into m-i: Comment 3] Review of attachment 8466763 [details] [diff] [review]: ----------------------------------------------------------------- meh

Comment on attachment 8466763 [details] [diff] [review] Proposed fix [Checked into m-i: Comment 3] https://hg.mozilla.org/integration/mozilla-inbound/rev/ae747b1cc524

What used to happen was that extensions were built into dist/bin/extensions and then in omnijar builds suite/app/Makefile.in would zip them up into XPIs into dist/bin/extensions or dist/bin/distribution/extensions as appropriate, but if you used --enable-chrome-format=flat then the extensions would remain flat in dist/bin/extensions so that you could easily develop them. Is there any way we can maintain this developer option?

This is probably not worth spending the time to verify since it does not affect standard builds.