RE: waltham ivi-application build failed

Hello Pekka, Thank you for your kindly reply. It is very helpful for me. >We haven't got far enough with Waltham to be able to build multiple XML files >together. src/waltham/Makefile.am generates several source files from >command.xml. One would need to replicate those rules for

[PATCH libinput] configure.ac: set AC_CONFIG_AUX_DIR

If not set, libtool will search directories up to ../.. for an install-sh and then dump the aux files there. This caused a couple of problems with the xorg release.sh script that now uses worktrees but is generally bad behaviour because we can't guarantee that we're not inside some other

[PATCH weston] weston-terminal: Add a --maximized command line parameter

This is useful for testing compositor response to a client that requests a maximized initial surface. Signed-off-by: Derek Foreman --- clients/terminal.c | 5 + 1 file changed, 5 insertions(+) diff --git a/clients/terminal.c b/clients/terminal.c index

[PATCH v2] configure: add option to disable tests

When building for a product, tests are not needed. Besides, one test requires a C++ compiler, which is not always available. So, add an option to configure to disable building tests altogether. Signed-off-by: "Yann E. MORIN" Reviewed-by: Eric Engestrom

[PATCH v2] configure: better check for the C++ compiler

When a C++ compiler is not found, then AC_PROG_CXX will set CXX to 'false'. However, we test that we can find $CXX, and indeed false exists in the PATH, for virtually all systems we have a chance to be compiled on. So we conclude that we do have a C++ compiler, when this is clearly wrong.

Re: weston-simple-egl fullscreen broken?

Hi, I have investigate deeper the issue and it comes from the Mali400 wayland library (at least in the r6p1-01rel0 version). Actually, the Mali400 wayland library is creating very early the output surface taking into account the 250x250 default size because fullscreen information is not yet

Re: [PATCH] [wayland] configure: add option to disable tests

Eric, All, On 2017-03-08 14:50 +, Eric Engestrom spake thusly: > On Sunday, 2017-03-05 11:53:18 +0100, Yann E. MORIN wrote: > > When building for a product, tests are not needed. > > > > Besides, one test requires a C++ compiler, which is not always > > available. > > > > So, add an option

Re: [PATCH] [wayland] configure: better check for the C++ compiler

Peter, All, On 2017-03-08 16:52 +1000, Peter Hutterer spake thusly: > On Sun, Mar 05, 2017 at 03:17:36PM +0100, Yann E. MORIN wrote: > > When a C++ compiler is not found, then AC_PROG_CXX will set CXX to > > 'false'. > > urgh... that is a rather unexpected behaviour. > > > However, we test that

[PATCH weston 0/2] Introduce substitute of connector option

Remove the option, because it is hard to use. Drm connector ids are hard to reach for users, and they can change when kernel or device tree is modified. If someone wants to enable just one output and disable all others, he can set "require-output-config". Then, all unconfigured outputs will be

[PATCH weston 1/2] Add option to disable unconfigured outputs

In current implementation, there is no configuration to disable unconfigured outputs. One can create an output section for a known output in weston.ini file and set its mode to "off" to disable a known output. But there is no configuration to disable unknown outputs. This might be usefull for

[PATCH weston 2/2] compositor-drm: remove connector option

Remove the option, because it is hard to use. Drm connector ids are hard to reach for users, and they can change when kernel or device tree is modified. If someone wants to enable just one output and disable all others, he can set "require-output-config". Then, all unconfigured outputs will be

Re: [PATCH] [wayland] configure: add option to disable tests

On Sunday, 2017-03-05 11:53:18 +0100, Yann E. MORIN wrote: > When building for a product, tests are not needed. > > Besides, one test requires a C++ compiler, which is not always > available. > > So, add an option to configure to disable building tests altogether. > > Signed-off-by: "Yann E.

Re: [PATCH weston v2 09/11] Switch to global output repaint timer

On Wed, 1 Mar 2017 11:34:08 + Daniel Stone wrote: > In preparation for grouping output repaint together where possible, > switch the per-output repaint timer, to a global timer which iterates > across all outputs. > > This is implemented by storing the absolute time

Re: [PATCH weston v3 08/11] Change boolean repaint_scheduled to quad-state enum

On Fri, 3 Mar 2017 16:59:42 + Daniel Stone wrote: > repaint_scheduled is actually cleverly a quad-state, disguised as a > boolean. There are four possible conditions for the repaint loop to be > in at any time: > - loop idle; no repaint will occur until specifically

Re: [PATCH weston v2 03/11] timespec: Add timespec_to_msec helper

On Wed, 8 Mar 2017 13:34:18 +0200 Pekka Paalanen wrote: > On Wed, 1 Mar 2017 11:34:02 + > Daniel Stone wrote: > > > Paralleling timespec_to_nsec, converts to milliseconds. > > > > Signed-off-by: Daniel Stone > >

Re: [PATCH weston v2 03/11] timespec: Add timespec_to_msec helper

On Wed, 1 Mar 2017 11:34:02 + Daniel Stone wrote: > Paralleling timespec_to_nsec, converts to milliseconds. > > Signed-off-by: Daniel Stone > Reviewed-by: Pekka Paalanen > --- > libweston/compositor.c | 2 +-

Re: waltham ivi-application build failed

On Tue, 7 Mar 2017 23:51:03 + "Mizuno, Wataru (ADITJ/SWG)" wrote: > Hello, > > I found ivi-applicaion.xml under data directory and tried to build it. > I had edited data/command.xml and build it then it succeeded so I did > same way to do ivi-application but it

[ANNOUNCE] libinput 1.6.3

libinput 1.6.3 is now available. A few small fixes that likely affect few users only: the minimum size for horizontal edge scrolling has been reduced to 40mm and hovering touches inside a software button area are handled better now. Since we don't use pressure-based touches in 1.6.x, this is