XULRunner build (--enable-libxul actually) does not play well with other --enable flags

RESOLVED INCOMPLETE

Status

Toolkit Graveyard
XULRunner
--
minor
RESOLVED INCOMPLETE
13 years ago
2 years ago

People

(Reporter: Darin Fisher, Unassigned)

Tracking

Details

(Reporter)

Description

13 years ago
XULRunner build (--enable-libxul actually) does not play well with other
--enable flags.

For example, it's not possible to build libxul without necko2, which can be
disabled using --enable-necko-protocols (or something like that).
(In reply to comment #0)
> XULRunner build (--enable-libxul actually) does not play well with other
> --enable flags.
> 
> For example, it's not possible to build libxul without necko2, which can be
> disabled using --enable-necko-protocols (or something like that).

Such incompatibilities should be detected at configure time; the same applies to --enable-optimize vs. --enable-debug, or (on some non-Mozilla software which I download in source form) --without-x vs. --enable-gui=gtk2.

Or do you mean that the incompatibility is bogus, and that it should be removed (possibly by moving about the functions or modules which create the incompatibility)?

Comment 2

2 years ago
XULRunner has been removed from the Mozilla tree: see https://groups.google.com/forum/#!topic/mozilla.dev.platform/_rFMunG2Bgw for context.

I am closing all the bugs currently in the XULRunner bugzilla component, in preparation for moving this component to the graveyard. If this bug is still valid in a XULRunner-less world, it will need to be moved to a different bugzilla component to be reopened.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

2 years ago
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.