Hi guys,
How will the offscreen render buffer behave? (for example pixmap?)
Maybe in wayland, there will be no offscreen? Or all the clients will be
offscreen?
Is the pixmap of the window shared for all the clients? Or only shared
to the compositor?
--
*^_^*
Many thanks & Best Reg
Cyril Brulebois (16/06/2011):
> ---
> COPYING | 97
> +++
> 1 files changed, 97 insertions(+), 0 deletions(-)
> create mode 100644 COPYING
>
> Introducing packages in Debian usually means checking licenses, and
> since there was jus
POSIX says equality is tested through the = operator; == is a bashism.
---
configure.ac | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
In case a pointer is needed:
http://pubs.opengroup.org/onlinepubs/95399/utilities/test.html
diff --git a/configure.ac b/
If wayland-scanner.m4 is missing, the WAYLAND_SCANNER_RULES macro is
undefined, and this token ends up in the generated configure script.
This makes autogen.sh (or autoreconf) succeed, but configure fail.
Catch that at configure time, making sure the macro was expanded:
| configure.ac:111: error:
Hi,
while trying to build the Wayland support for Qt, I noted that the
generated (and exported) client protocol header is not self contained.
Attached is a simple fix, though I haven't checked whether the server
protocol header would need similar treatment.
regards,
Michael
>From df9af09af8104b71
