Remove MOZ_ENABLE_CAIRO_GFX from the build system

RESOLVED FIXED

Status

()

Core
Build Config
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Peter Weilbacher, Assigned: Peter Weilbacher)

Tracking

Trunk
x86
Linux
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
While looking at bug 376790 and bug 376791 again I noticed that there are still quite a few checks of MOZ_ENABLE_CAIRO_GFX in our build system. I guess they can be removed by now.
I noticed some cruft in the libxul makefiles the other day:
http://lxr.mozilla.org/mozilla/source/toolkit/library/libxul-config.mk#286
(Assignee)

Comment 2

10 years ago
Created attachment 297352 [details] [diff] [review]
patch

Ted, yes, that stuff is what prompted me to file this bug. :-)

Well, this patch does what I had in mind. It kind of robs the "cairo-" (in front of the platform toolkit names in configure.in) of its purpose, but it seems to work, at least I can still compile SeaMonkey on Linux and it runs afterwards. Maybe a case for the try server?
Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Attachment #297352 - Flags: review?(ted.mielczarek)
Comment on attachment 297352 [details] [diff] [review]
patch

r=me as long as you ran a tryserver build with this.

Do you have a followup on removing MOZ_CAIRO_GFX?  (Or did you already do that?)
Attachment #297352 - Flags: review?(ted.mielczarek) → review+
(Assignee)

Comment 4

10 years ago
Comment on attachment 297352 [details] [diff] [review]
patch

Yes, I did a try server run (with a patch that included this one).

The one on MOZ_CAIRO_GFX is bug 413632.
Attachment #297352 - Flags: approval1.9?
Comment on attachment 297352 [details] [diff] [review]
patch

a=beltzner for 1.9
Attachment #297352 - Flags: approval1.9? → approval1.9+
(Assignee)

Comment 6

10 years ago
Patch checked into trunk.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Flags: in-testsuite-
(Assignee)

Comment 7

10 years ago
Just committed the change to config/static-config.mk that I had apparently forgotten last night.
You need to log in before you can comment on or make changes to this bug.