Closed
Bug 77049
Opened 23 years ago
Closed 23 years ago
Use Xlib-toolkit if no GTK+ is available...
Categories
(SeaMonkey :: Build Config, enhancement)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: roland.mainz, Assigned: cls)
Details
RFE: Build config should switch to Xlib-toolkit (e.g. "--enable-toolkit=xlib") as "fallback" if GTK+-toolkit is not available or does not work (e.g. configure test fails (like on 64bit SPARC where it tries to link against 32bit libraries)). This should help on platforms like 64bit SPARC where GTK+ toolkit is not available (see bug 20860) and removes one item from the incredibly large "you must install xyz first before you can compile mozilla"-list...
This is not going to happen. The existance of a "fallback" mechanism would imply extended support for building with xlib which is not in any current roadmap. We do not have the developer resources to split development between both gtk & xlib as such as fallback would require dual-toolkit development. If a machine cannot meet the default prerequistes, then the user can specify the configure options themseles to get around the problem.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 2•23 years ago
|
||
> If a machine cannot meet the default prerequistes, then the user can specify
> the configure options themseles to get around the problem.
Agreed... valid arguments.
What about adding a "echo" line which tells the user about the option to use
"--enable-toolkit=xlib" when the GTK+/GDK test fails and/or update the Unix
build instructions ?
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•