Qt
  1. Qt
  2. QTBUG-58150

The load(qt_plugin) directive results in a "could not find feature reduce_exports" error

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: P1: Critical P1: Critical
    • Resolution: Out of scope
    • Affects Version/s: 5.8.0 RC
    • Fix Version/s: None
    • Component/s: Build tools: qmake
    • Labels:
      None
    • Environment:

      QtBase: 4a73842 (head of 5.8 from meta-qt5 layer)

      Description

      There is a problem with qtbase 4a73842 (head of 5.8 from meta-qt5 layer). It seems like every time I try to run qmake on a .pro file containing load(qt_plugin) I get the error Project ERROR: Could not find feature reduce_exports. While the QT_CONFIG in mkspecs/qconfig.pri shows that the parameter is there.

      1. qmake.log
        12 kB
        Gordan Markuš

        Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          Oswald Buddenhagen added a comment -

          where does that qt_plugins.prf come from?

          Show
          Oswald Buddenhagen added a comment - where does that qt_plugins.prf come from?
          Hide
          Gordan Markuš added a comment -

          Oswald Buddenhagen I've attached the relevant part of the qmake debug output, it seems like the function fails in mkspecs/features/qt_functions.prf . Is that enough information or would you require the whole qmake.log?

          Show
          Gordan Markuš added a comment - Oswald Buddenhagen I've attached the relevant part of the qmake debug output, it seems like the function fails in mkspecs/features/qt_functions.prf . Is that enough information or would you require the whole qmake.log?
          Hide
          Oswald Buddenhagen added a comment -

          that doesn't answer my question. i have no clue what that qt_plugins thing may be and therefore how the problem may be related to it. maybe you mean qt_plugin? this file is very clearly marked as private and you have no business using it unless you're creating a qt module.

          Show
          Oswald Buddenhagen added a comment - that doesn't answer my question. i have no clue what that qt_plugins thing may be and therefore how the problem may be related to it. maybe you mean qt_plugin? this file is very clearly marked as private and you have no business using it unless you're creating a qt module.
          Hide
          Gordan Markuš added a comment - - edited

          Oswald Buddenhagen, sorry for the tardy reply. I've edited the issue topic and description.

          This is the case with load(qt_plugin) , my mistake.

          Show
          Gordan Markuš added a comment - - edited Oswald Buddenhagen , sorry for the tardy reply. I've edited the issue topic and description. This is the case with load(qt_plugin) , my mistake.
          Hide
          Oswald Buddenhagen added a comment -

          ok, but you still need to convince me that your use case is valid.

          Show
          Oswald Buddenhagen added a comment - ok, but you still need to convince me that your use case is valid.
          Hide
          Gordan Markuš added a comment - - edited

          Acting as an integrator I came across this issue. By using QT+=multimedia-private the team saw a need to use the load(qt_plugin) directive, which is not valid for their use case.
          From my perspective the bug can be closed as the load(qt_plugin) was used in a case that is not valid.

          Show
          Gordan Markuš added a comment - - edited Acting as an integrator I came across this issue. By using QT+=multimedia-private the team saw a need to use the load(qt_plugin) directive, which is not valid for their use case. From my perspective the bug can be closed as the load(qt_plugin) was used in a case that is not valid.

            People

            • Assignee:
              Oswald Buddenhagen
              Reporter:
              Gordan Markuš
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes