summaryrefslogtreecommitdiffstats
path: root/src/plugins/gfxdrivers/directfb/directfb.pro
diff options
context:
space:
mode:
authorAnders Bakken <anders.bakken@nokia.com>2009-08-24 15:34:08 (GMT)
committerAnders Bakken <anders.bakken@nokia.com>2009-08-25 19:15:08 (GMT)
commit6a546cadf18b2c73d32868d84a8e3edc4455d508 (patch)
tree5494bf4c3c1018954e0b7218a6934ac4d97fc53f /src/plugins/gfxdrivers/directfb/directfb.pro
parentdc4e9f4bb91237b26b82e27310eda6808786ce36 (diff)
downloadQt-6a546cadf18b2c73d32868d84a8e3edc4455d508.zip
Qt-6a546cadf18b2c73d32868d84a8e3edc4455d508.tar.gz
Qt-6a546cadf18b2c73d32868d84a8e3edc4455d508.tar.bz2
Implement support for keeping image provider alive
If you define QT_DIRECTFB_IMAGEPROVIDER_KEEPALIVE we make sure atleast one IDirectFBImageProvider is alive at all times. Apparently this is refcounted by DirectFB on atleast one implementation and there's considerable overhead involved when releasing the last/creating the first image provider. Reviewed-by: TrustMe
Diffstat (limited to 'src/plugins/gfxdrivers/directfb/directfb.pro')
-rw-r--r--src/plugins/gfxdrivers/directfb/directfb.pro1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/plugins/gfxdrivers/directfb/directfb.pro b/src/plugins/gfxdrivers/directfb/directfb.pro
index f01d8b1..055e7cd 100644
--- a/src/plugins/gfxdrivers/directfb/directfb.pro
+++ b/src/plugins/gfxdrivers/directfb/directfb.pro
@@ -7,6 +7,7 @@ QTDIR_build:DESTDIR = $$QT_BUILD_TREE/plugins/gfxdrivers
# support all of the DirectFB API.
#
#DEFINES += QT_DIRECTFB_IMAGEPROVIDER
+#DEFINES += QT_DIRECTFB_IMAGEPROVIDER_KEEPALIVE
#DEFINES += QT_DIRECTFB_IMAGECACHE
#DEFINES += QT_NO_DIRECTFB_WM
#DEFINES += QT_NO_DIRECTFB_LAYER