On 2 May 2013 13:49, Kai-Uwe Behrmann <[email protected]> wrote: > Why will come a need for a CMS to read hardcoded names from the config file?
Well, colord won't, but not everybody wants/needs colord, e.g. on an embedded display where a color profile is never likely to change. For this case I've added a cms-static plugin[1] that reads the weston.conf config file like this: [output] name=LVDS1 icc_profile=/usr/share/color/icc/colord/Bluish.icc So the "static" CMS plugin needs the LVDS1 name so it can check the weston_output when the created callback gets called. Note, in the colord plugin we also set the LVDS1-type name as metadata on the device, although it's not required. Richard. [1] krh didn't want this directly in the compositor-drm file, which makes sense. _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
