linux - What is the use of various Qt platform plugins? -


i doing cross compiling of qt5.2 application arm based target (ti am335x evm) , failing display on platform. after doing google’ing found if launched with:

 ./helloworld -platform eglfs 

it show (full screen, worked)!

i started looking @ platform options, found:

android, eglfs, linuxfb, minimalegl, windows, xcb, cocoa, ios, offscreen, qnx, directfp, kms, minimal, openwfd

i’m wondering for. assume, example, if wanted run application on android device i’d have pass -platform android, they’re not obvious me.

is there listing anywhere of when each of these parameters should used?

for example, eglfs stand for? , why did need use linuxfb didn’t work?
(i have thought linux frame buffer how wanted launch application since running on embedded linux)

if linuxfb plugin doesn't work, possibly didn't correctly configure framebuffer device on system. maybe directf layer running, may want try directfb plugin instead.

if wish avoid having specify platform option when run executable, can pass default 1 configure when build qt.

the plugins can described follows:

  • linux plugins - use linux-specific input devices , various output devices

    • eglfs - uses opengl es in fullscreen mode. there's no other way since opengl has no concept of window manager.

    • directfb (not directfp) - uses linux frame buffer opengl es via directfb layer. integrates directfb windowing.

    • linuxfb - uses linux frame buffer in fullscreen mode. there's no other way since linuxfb has no concept of window manager.

    • kms - uses linux kernel modesetting api in fullscreen mode. there's no other way since drm has no concept of window manager.

    • openwfd - uses openwfd wifi display in fullscreen mode. there's no other way since openwfd has no concept of window manager.

  • platform-independent plugins - made run on os

    • xcb - runs on x11 server , integrated x11 windowing environment. won't behave correctly without window manager running well. can made work on windows, given windows implementation of xlib, if want to, say, serve applications windows server x11 thin terminals (typically unix boxes).

    • offscreen - renders offscreen buffer. useful rendering custom displays.

    • minimal - minimalistic backing store optionally dumps virtual screen file. implements bare minimum of functionality demonstrate how start writing platform plugin.

  • other platform-specific plugins

    • android - uses android apis , integrated android environment.

    • windows - uses winapi , integrated windows windowing environment.

    • cocoa - uses cocoa apis , integrated os x windowing environment.

    • ios - uses ios toolkits , integrated ios environment.

    • qnx - uses qnx apis , integrated qnx photon windowing environment.


Comments

Popular posts from this blog

html - Sizing a high-res image (~8MB) to display entirely in a small div (circular, diameter 100px) -

java - IntelliJ - No such instance method -

identifier - Is it possible for an html5 document to have two ids? -