[PATCH weston 04/11] make the backends compositor-neutral

Giulio Camuffo giuliocamuffo at gmail.com
Mon Jun 22 22:51:15 PDT 2015

2015-06-23 3:52 GMT+03:00 Bill Spitzak <spitzak at gmail.com>:
> It seems like prev
> On Mon, Jun 22, 2015 at 1:02 PM, Giulio Camuffo <giuliocamuffo at gmail.com>
> wrote:
>> The backends used to have lots of code dealing with weston specific
>> configs.
>> To allow them to be used by other compositors with their own
>> configurations
>> remove all the usage of weston_config from the backends code and move it
>> in weston.c.
> It seems like the previous version allowed the backend to decide on the
> name, type, and number of config options that it understood, while this
> requires the main program to have all that knowledge. Thus it does not seem
> as good.

Not really. The previous versions had quite frankestein plugins, in
that they also had an entry point specific for the compositor weston.
Other compositors still needed to handle config in the compositor
By making all even for all compositors i think the new version is better.

> Just because it is a weston_config structure does not mean it has to contain
> the contents of a weston configuration. A different compositor could just
> extract any backend-specific details from it's own configuration database
> and write a dummy weston_config containing them.

I'm not sre what you mean. Other compositors will not use
weston_config, many needed functions for it are not even exported.
And there is not just weston_config, there also is the command line
options handling which can vary between compositors.

More information about the wayland-devel mailing list