Make sure your using the 1.1 branch of Wayland and Weston, and the
stable branch of QtWayland.
By default when you compile QtWayland it will just provide you with a
QPA plugin which will allow you to run Qt applications inside a
Wayland compositor. QtWayland also contains apis to simplify
You can rasterize a glyph with freetype, then you can depending on the
surface you want to draw into either upload your glyph into some
texture glyph cache and then blit the texture into some gl surface,
or if your working on a main memory surface, you can use some raster
painter abstraction and
Hi
JørgenOn Wed, Aug 22, 2012 at 07:17:13PM +, ext jegde jedge wrote:
Thanks everybody.
I ran into a few blocks trying to build qtwayland/src/plugins/platform/wayland
Thats not good :(
I have to keep two separate libxkbcommon's around one for weston and
one for qt5.
weston will not
Hi,
On Tue, Aug 21, 2012 at 09:15:54AM -0400, ext jegde jedge wrote:
Please forgive the 'user' post in a devel list.
I am porting a fundamentally Qt system but still need some X backward
compatability?
I am unclear of the Qt/X/Weston/Wayland interoperability.
Does the weston compositor
Hi Mikalai
On 12 July 2012 08:03, Mikalai Kisialiou kisial...@gmail.com wrote:
Juan, Jonas and Christopher,
I appreciate your feedback! Small additions to shells are indeed not a
problem. It was not a right example to make my point. As it is now, Weston
can be considered barebone since the
Hi guys.
I have implemented a proposal for thread affinity for libwayland-client.
By this I mean that proxies belong to threads. So events will be
dispatched in the thread that created the proxy. Obviously proxies can
be moved between threads if that is desired.
As a side-effect I also
Hi guys,
We have had a patch in Qt-Wayland since November that has given us some
thread affinity to Wayland clients so we can assure that we don't run
wl_display_iterate from other threads then the thread that actually created the
display. I have just cleaned it up a bit and was hoping to get it
