If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Migrate mail/components to frozen linkage for non-static linux builds

RESOLVED FIXED

Status

Thunderbird
Build Config
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: standard8, Assigned: standard8)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
Created attachment 311659 [details] [diff] [review]
The fix

As part of the ongoing effort to move Thunderbird onto libxul, I've migrated mail/components to frozen linkage.

This patch will only migrate non-static builds (i.e. developer builds), static builds will remain unaffected. If we were to affect static builds, then we'd be forced to move the mail/components items into a separate shared library, hence potentially affecting performance.

As we don't have any performance testing at the moment, but would like to preserve the code so that it does still work with frozen linkage, this is the best compromise that Dan and I came up with.

I've only done Linux as that's all I've got at the moment.
Attachment #311659 - Flags: superreview?(bienvenu)
Attachment #311659 - Flags: review?(bienvenu)

Comment 1

10 years ago
Comment on attachment 311659 [details] [diff] [review]
The fix

looks like a tab here:

-	}
+	if (!starting || name.IsEmpty())
+    return PR_FALSE;
+
Attachment #311659 - Flags: superreview?(bienvenu)
Attachment #311659 - Flags: superreview+
Attachment #311659 - Flags: review?(bienvenu)
Attachment #311659 - Flags: review+
(Assignee)

Comment 2

10 years ago
Patch checked in with tab -> space. Fixed.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.