Closed Bug 450964 Opened 15 years ago Closed 15 years ago
Get rid of remaining SVG build options in comm-central
The comm-central doesn't need to care about SVG. Investigating what we need to port from bug 450495 I realized that we have removed most of the SVG stuff already at checkin, but a few things remain that should still be cleaned up. I could do this as part of bug 445141 but it might be better to do the whole task in smaller chunks. The most problematic case is http://mxr.mozilla.org/comm-central/source/mail/installer/windows/packages-static#393 but with the removal of vast parts of this that we already did I'm not sure if it works correctly at the moment, and removing the ifdef doesn't change more than adding two bogus warnings at packaging time for current default Thunderbird builds.
This patch removes the rest of SVG definitions in comm-central. I was informed that bug 366126 enabled SVG in Thunderbird, so that ifdef is actually even more unneeded as default builds have it anyway.
Assignee: nobody → kairo
Status: NEW → ASSIGNED
Attachment #334179 - Flags: review?(bugzilla)
Attachment #334179 - Flags: review?(bugzilla) → review+
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Does this mean |ac_add_options --disable-svg| support is somehow "reduced" ?
Target Milestone: --- → seamonkey2.0alpha
(In reply to comment #3) > Does this mean |ac_add_options --disable-svg| support is somehow "reduced" ? No. Options will still get passed to the core mozilla configure. All it reduces is the extra time to configure comm-central (which isn't much in this case).
Product: SeaMonkey → MailNews Core
QA Contact: build-config → build-config
Target Milestone: seamonkey2.0alpha → ---
(In reply to comment #4) Actually, it looks like it does ... because SeaMonkey was missing some related #ifdef: I filed bug 541267.
You need to log in before you can comment on or make changes to this bug.