Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » Wayland & U++
Wayland & U++ [message #33509] Tue, 16 August 2011 22:32 Go to previous message
dolik.rce is currently offline  dolik.rce
Messages: 1789
Registered: August 2008
Location: Czech Republic
Ultimate Contributor

Hi everyone!

dolik.rce wrote on Sun, 24 July 2011 22:11

mirek wrote on Sun, 24 July 2011 20:56

Next steps now should be

- macosx
- android
- maybe "gtk backend" - one which is more tightly bound to gtk
- ditto for QT

Volunteers needed Smile
You forgot to add the Wayland display server to your list Wink The drawing part will be probably quite similar to framebuffer, so it shouldn't be very difficult.

I already tried to compile wayland and get it running on my Arch Linux with mixed results - the server runs, the clients don't Confused But as soon as I get it to work, I promise to volunteer Wink

As I promised, I'm here to volunteer Very Happy . I've finally compiled everything necessary to run wayland as well as the example compositor and client applications. I also tried to incorporate U++ into the examples - and here comes the first problem Smile

I started with the simplest available example (just about 200 lines of code Smile ) and tried to put in some U++ drawing code. But as soon as I add the Draw package into the project, I started getting these runtime errors:
Quote:

unknown object (138760168), message create_buffer(nhiiuo)
unknown object (2049), message attach(oii)
wl_display@1: error 1: invalid arguments for wl_shm@6.create_buffer
disconnect from client 0x9637030
Aborted
This happens as soon as I link Draw to the executable, even when using no code from the package (not even include Draw/Draw.h). Based on this behavior I figured it is related to INITBLOCKs and tracked the problem down to call of sInitFonts() in Draw/Font.cpp:49. I have no idea how can it influence the wayland code (any hints?), but as soon as I commented it out, the problem disappeared. It also works fine when explicitly called from CONSOLE_APP_MAIN after the wayland display is initialized.

So far I have just very basic stuff, drawing an Image on the screen. In the next days, I'll begin to incorporate this into the rainbow framework. As I already said, it should be pretty straight forward. I will use this thread to keep you informed about the progress. Also I can post the package if anyone is interested (and has libwayland-* libraries ready)...

Best regards,
Honza
 
Read Message
Read Message
Previous Topic: MVC example
Next Topic: Assist Open File in Solution?
Goto Forum:
  


Current Time: Sun Apr 28 15:29:24 CEST 2024

Total time taken to generate the page: 0.03014 seconds