Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. How to disable compilation of the QMultimedia DirectShow plugin, if at all possible
Forum Updated to NodeBB v4.3 + New Features

How to disable compilation of the QMultimedia DirectShow plugin, if at all possible

Scheduled Pinned Locked Moved Installation and Deployment
2 Posts 1 Posters 1.3k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Thoran
    wrote on last edited by
    #1

    Hello everyone.

    Iam trying to compile the Qt5.4.0 source with VS2008 and have an compile error in

    \qt-everywhere-opensource-src-5.4.0\qtmultimedia\src\plugins\directshow\camera\dscamerasession.cpp(104) : error C2664:

    As I don't need the DirectShow features I wonder how I can disable the compilation of the DS plugin.
    Of course I can go one folder up and remove the DS plugin dir in the *.pro-file, but I found out that there is the following line in the *.pro-file:

    config_directshow: SUBDIRS += directshow

    which lets me assume I can disable compilation of the DS plugin by configuration and without intrusion in the source code. I already had a look at the features in "\qt-everywhere-opensource-src-5.4.0\qtbase\src\corelib\global\qfeatures.txt" but I couldn't find a matching feature there.

    Is there another way of excluding it from compilation?

    Thanks in advance.
    Thoran

    1 Reply Last reply
    0
    • T Offline
      T Offline
      Thoran
      wrote on last edited by
      #2

      Ok, for now I commented the above mentioned entry in plugins.pro to get rid of the error. Not nice, but it works. However I am now facing compile errors with the precompiled headers. I am not quite sure if this is a direct consequence of my change in *.pro file or whether this is just simply a VS2008 problem that just can't be solved. In case I stumble across a solution I post it here, otherwise I guess I have to change to the VS2013 CE.

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved