Closed
Bug 673084
Opened 13 years ago
Closed 13 years ago
postflight_all errors when building official mac builds manually
Categories
(Calendar :: Build Config, defect)
Calendar
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
1.0
People
(Reporter: Fallen, Assigned: standard8)
Details
Attachments
(1 file)
2.18 KB,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
I don't have the error at hand right now (mschroeder maybe?), but when building universal builds under mac, we seem to be getting some errors in calendar/lightning/build/universal.mk because some of the variables are not set.
Comment 1•13 years ago
|
||
(In reply to comment #0) > I don't have the error at hand right now (mschroeder maybe?) /bin/sh: ../obj-thunderbird-lightning-tests-trunk/i386/mozilla/dist/thunderbird/Shredder.app/Contents/MacOS/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/install.rdf_: No such file or directory
Assignee | ||
Comment 2•13 years ago
|
||
The root cause of this seems to be that DISABLE_LIGHTNING_INSTALL=1 is set in the mozconfigs but not in the global environment. The issue here is that we get lightning build with DISABLE_LIGHTNING_INSTALL set, but then when postflight_all comes along, that doesn't get pass the env var and so the flight.mk fails. The buildbot builds currently get around this by specifying DISABLE_LIGHTNING_INSTALL in the environment. The code in flight.mk appears to be trying to unify the lightning install.rdf into $(DIST)/universal/<appname>.app/Contents/MacOS/extensions/... however, the problem there is that the rest of the unify code isn't unifying the rest of the lightning extension into that directory. Rather than trying to fix the flight.mk issue, it appears to be simpler and potentially better to concentrate on getting lightning release builds into the xpi-stage directory, generating build symbols from there (bug 673083). The only downside to this is that developers building universal binaries of Thunderbird with Lightning, won't get lightning installed into the application directory. I don't think that is a significant issue as it is likely to be rare. If we find we need it, we can try fixing it properly later.
Assignee | ||
Updated•13 years ago
|
Attachment #548568 -
Attachment description: WIP → The fix
Reporter | ||
Comment 3•13 years ago
|
||
Comment on attachment 548568 [details] [diff] [review] The fix r=philipp
Attachment #548568 -
Flags: review?(philipp) → review+
Assignee | ||
Comment 4•13 years ago
|
||
Checked in: http://hg.mozilla.org/comm-central/rev/4cb88997f292
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
Reporter | ||
Updated•13 years ago
|
Target Milestone: 1.0 → 1.0b8
You need to log in
before you can comment on or make changes to this bug.
Description
•