I do not think we should be overriding upstream defaults like this. If your
use case is different, you can always provide a custom weston.ini through a
bbappend.

Alex

On Wed, 11 Mar 2020 at 17:52, Domarys Correa <
domarys.correa@ossystems.com.br> wrote:

> Don't force users to have input device in your targets. As the default
> option require-input is set to true, Weston only starts if we have a
> device in /dev/input/event* and this not a requirement for all
> applications,
> e.g. kiosk browser.
>
> Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
> ---
>  meta/recipes-graphics/wayland/weston-init/weston.ini | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/wayland/weston-init/weston.ini
> b/meta/recipes-graphics/wayland/weston-init/weston.ini
> index 1eecf48bc1..1e6dff68fd 100644
> --- a/meta/recipes-graphics/wayland/weston-init/weston.ini
> +++ b/meta/recipes-graphics/wayland/weston-init/weston.ini
> @@ -1,9 +1,10 @@
>  # configuration file for Weston
>
> -#[core]
> +[core]
>  #modules=xwayland.so,cms-colord.so
>  #shell=desktop-shell.so
>  #gbm-format=xrgb2101010
> +require-input=false
>
>  #[shell]
>  #background-image=/usr/share/backgrounds/gnome/Aqua.jpg
> --
> 2.17.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>