[PATCH] Override modules list and don't always load desktop-shell.so

Pier Luigi pierluigi.fiorini at gmail.com
Tue Aug 13 13:17:36 PDT 2013

2013/5/1 Kristian Høgsberg <hoegsberg at gmail.com>:
> On Fri, Apr 19, 2013 at 04:11:01PM -0700, Bill Spitzak wrote:
>> >2013/4/16 Kristian Høgsberg <hoegsberg at gmail.com>:
>> >>I know the current behavior is a bit problematic for some use cases.
>> >>However it works well for the case where you load a plugin in addition
>> >>to the shell, like xwayland.  I'm not sure what the best way to make
>> >>both cases work is, except to make the shell plugin special.  We could
>> >>go back to use a shell config key and command line option and make
>> >>modules only about additional modules.
>> Would it be possible to load all the named modules, then find out if
>> any of them are shells, and load the default shell if none are? Ie
>> if the command line does not name a shell module you will get the
>> default one.
> Yeah, I think we could do something like that.  Instead of looking up
> the module_init function we can dlsym for an instance of a
> weston_module struct, which can let us do ABI version checks and make
> sure we only load one of each type of module (shell, cms, etc).
> Kristian

We might have two or more shell plugins and this way only the first
will be loaded.
I would like to have a way to specify a restricted list of modules
from command line to control exactly what gets loaded.

PS: Sorry for the huge delay.

Out of the box experience

More information about the wayland-devel mailing list