We can build Mozilla with more than one toolkit enabled, but that makes no real sense if we can't tell Mozilla which to use when starting up. Because of this, we'll need a startup switch to tell it what we want to use (we have xlib, gtk, gtk2, and qt now IIRC). This would be especially good if you want to test not-so-mature toolkits as gtk2 or the re-enabled qt port, but still be able to use gtk for "normal" working.
What about implementing this feature in run-mozilla.sh using $LD_LIBRARY_PATH ? Toolkit-specific compoents are then stored in seperate dirs - and LD_LIBRARY_PATH includes only the selected toolkit dir into it's path.
Summary: Add command-line switch to start up using specific toolkit (e.g. qt or gtk) → Add command-line switch to start up using specific toolkit (e.g. gtk, qt, photon, xlib, etc.)
The LD_LIBRARY_PATH switching doesn't help when it comes to the components. Component dirs are not in the LD_LIBRARY_PATH and currently, everything in (and maybe under) bin/components gets automagically registered.
support for multiple toolkits has been dropped (bug 191528)
Should this bug be marked as INVALID ?
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
Component: Cmd-line Features → Cmd-line Features
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.