1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking Benchmarking Platform
Phoromatic Test Orchestration

Qt5's Linux Requirements Cause Problems

Qt

Published on 15 September 2012 03:37 AM EDT
Written by Steven Starr in Qt
110 Comments

With XCB being a requirement for the Linux version of Qt 5.0, and Xlib not being supported, it's causing problems for some wishing to adopt this forthcoming tool-kit.

Qt 5.0 on Linux is using the X C-language Bindings rather than Xlib since that's what is generally favored these days for communicating with the X.Org Server. On Qt4, Xlib was supported. Just one day after there was the controversial freelance article about Mono being desirable for Linux, another developer is sharing his freelance views on a separate project. Steven Starr as a Linux desktop developer wrote into Phoronix with his views (well, it's more along the lines of a brief rant but does spark a valid point) on Qt5 about the change.

I wonder about Qt developers some times.

Qt5 is OpenGL based right, well XCB is a requirement on Linux now, it wasn't on Qt4. And XLIB isn't supported.

Let me throw out a quote from the XCB devs.
XCB-GLX only communicates with the X server, it does not perform any hardware initialization or touch the OpenGL client-side state. Because of this XCB-GLX cannot be used as a replacement for the GLX API. To use OpenGL in the X Windowing system, one must use the GLX API, and the GLX API is closely coupled with Xlib. As a result, an OpenGL application on the X Windows must use Xlib and thus can't be done using only XCB. [Citation]
So what does this mean?

It means that they're forcing us to install and use XCB that doesn't support Hardware Accelerated Graphics using your ATI/NVIDIA binary drivers. And it ends up reverting back and using XLIB/GLX anyways.

Qt5 + XCB = Low Level Crippled API Wrapper for a Higher Level Fully Functional API.

If you ever wonderd why KDE4 and Nvidia cards are constantly breaking theres your answer. Because some stupid fuck thought XCB was cool because someone else told him it was.

The reason I am soooo pissed is because I have been writing a new Qt Desktop Environment for the last 1-1/2 years and Qt devs broke it by removing the QX11 API's. And my new desktop is blazzzzzzing rubber melting FAST!!!!

Qt5's Linux Requirements Cause Problems


Has Qt5 with XCB caused problems for you? This isn't a Linux-specific problem but any Qt platform using X. Share your thoughts in the Phoronix Forums. Should you have any other freelance article to share with the Phoronix reader base, feel free to contact Phoronix.

Latest Linux News
  1. Linux 4.1-rc5 Kernel Released
  2. Mesa 10.5.6 Brings Fixes All Over The Place
  3. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  4. The Latest Linux Kernel Git Code Fixes The EXT4 RAID0 Corruption Problem
  5. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  6. Ubuntu's LXD vs. KVM For The Linux Cloud
  7. Fedora Server 22 Benchmarks With XFS & The Linux 4.0 Kernel
  8. GCC 6 Gets Support For The IBM z13 Mainframe Server
  9. Fedora 22 Is Being Released Next Tuesday
  10. OpenWRT 15.05 Preparing Improved Security & Better Networking
Latest Articles & Reviews
  1. The Latest Features For Linux Performance Management + Benchmark Monitoring
  2. Noctua NH-U12DX i4 + NF-F12
  3. Btrfs RAID 0/1 Benchmarks On The Linux 4.1 Kernel
  4. The State Of Various Firefox Features
Most Viewed News This Week
  1. The Linux 4.0 Kernel Currently Has An EXT4 Corruption Issue
  2. The Linux 4.0 EXT4 RAID Corruption Bug Has Been Uncovered
  3. Microsoft Open-Sources The Windows Communication Foundation
  4. Systemd 220 Has Finally Been Released
  5. Another HTTPS Vulnerability Rattles The Internet
  6. LibreOffice 5.0 Open-Source Office Suite Has Been Branched
  7. LibreOffice 5.0 Beta 1 Released
  8. Will Ubuntu Linux Hit 200 Million Users This Year?