Revision history [back]

We are compiling Qt 4 from source and linking to it statically. And looking at the configuration banners, OpenCV seems to only be using a tiny fraction of Qt's functionality. E.g. stuff like network support, scripting support, video, Qt3 compatibility, various image formats support all seems unneeded because OpenCV uses its own facilities for that. So we'd like to disable them to reduce compilation time and the resulting file size.

Is there any official guidance and/or discernable indicators of which Qt features are actualy used by OpenCV?

We are compiling Qt 4 from source and linking to it statically. And looking link to it. Looking at the configuration banners, OpenCV seems to only be using a tiny fraction of Qt's functionality. E.g. stuff like network support, scripting support, video, Qt3 compatibility, various image formats support all seems unneeded because OpenCV uses its own facilities for that. So we'd like to disable them to reduce compilation time and the resulting file size.

Is there any official guidance and/or discernable indicators of which Qt features are actualy used by OpenCV?

We are compiling Qt 4 from source to link to it. and using it as a private copy. Looking at the configuration banners, OpenCV seems to only be using a tiny fraction of Qt's functionality. E.g. stuff like network support, scripting support, video, Qt3 compatibility, various image formats support all seems unneeded because OpenCV uses its own facilities for that. So we'd like to disable them to reduce compilation time and the resulting file size.

Is there any official guidance and/or discernable indicators of which Qt features are actualy used by OpenCV?