Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Abstract plugin inheritance error
Forum Updated to NodeBB v4.3 + New Features

Abstract plugin inheritance error

Scheduled Pinned Locked Moved Solved General and Desktop
23 Posts 4 Posters 6.9k Views 3 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.
  • K kshegunov
    12 Jan 2017, 00:16

    @Defohin said in Abstract plugin inheritance error:

    It's not an export problem

    I would argue that it is. You're trying to use a class that's defined in the application project in the library. The Q_OBJECT macro generates members(!) that have to be accessible to the linker, and in your case they aren't. This is moot when dealing with interfaces, but it's significant when dealing with classes like AbstractPlugin.

    The virtual inheritance is to avoid the diamond problem.

    If you have a diamond somewhere, then you've done something very, very, very wrong. I have had a need to deal with it only a couple of times in my 10 years of experience with C++. Virtual inheritance is evil, avoid it at (almost) any cost!

    D Offline
    D Offline
    Defohin
    wrote on 12 Jan 2017, 00:19 last edited by
    #5

    @kshegunov Thank you, for real, but what you think I should do? The entire code is here, but still I have no idea what is happening.

    K 1 Reply Last reply 12 Jan 2017, 00:20
    0
    • D Defohin
      12 Jan 2017, 00:19

      @kshegunov Thank you, for real, but what you think I should do? The entire code is here, but still I have no idea what is happening.

      K Offline
      K Offline
      kshegunov
      Moderators
      wrote on 12 Jan 2017, 00:20 last edited by kshegunov 1 Dec 2017, 00:21
      #6

      Simply remove the AbstractPlugin class, it's not necessary anyway, it does nothing. Instead for each plugin derive from QObject and the interface as you've done. That should fix it for the most part. Namely:

      class PluginFoo : public QObject, public PluginInterface
      {
          Q_OBJECT
          Q_PLUGIN_METADATA(IID PluginInterface_iid FILE "pluginfoo.json")
          Q_INTERFACES(PluginInterface)
      };
      

      Then (as you're working on windows) you'll probably get a linker error for the plugin class itself, exporting it from the dll should fix that as well.

      Read and abide by the Qt Code of Conduct

      D 1 Reply Last reply 12 Jan 2017, 00:24
      0
      • K kshegunov
        12 Jan 2017, 00:20

        Simply remove the AbstractPlugin class, it's not necessary anyway, it does nothing. Instead for each plugin derive from QObject and the interface as you've done. That should fix it for the most part. Namely:

        class PluginFoo : public QObject, public PluginInterface
        {
            Q_OBJECT
            Q_PLUGIN_METADATA(IID PluginInterface_iid FILE "pluginfoo.json")
            Q_INTERFACES(PluginInterface)
        };
        

        Then (as you're working on windows) you'll probably get a linker error for the plugin class itself, exporting it from the dll should fix that as well.

        D Offline
        D Offline
        Defohin
        wrote on 12 Jan 2017, 00:24 last edited by
        #7

        @kshegunov I will need the abstract class to add a few common methods. It's just an example code.

        K 1 Reply Last reply 12 Jan 2017, 00:28
        0
        • D Defohin
          12 Jan 2017, 00:24

          @kshegunov I will need the abstract class to add a few common methods. It's just an example code.

          K Offline
          K Offline
          kshegunov
          Moderators
          wrote on 12 Jan 2017, 00:28 last edited by kshegunov 1 Dec 2017, 00:29
          #8

          @Defohin said in Abstract plugin inheritance error:

          I will need the abstract class to add a few common methods. It's just an example code.

          Then you must provide the linker with the appropriate binary. Meaning you must, in this case, move the abstract plugin class in a separate library to which your plugins will link (look up the docs, there's examples how to make an ordinary dynamic library look here). In this library you need to export the AbstractPlugin class (through Q_DECL_EXPORT and Q_DECL_IMPORT again you can look how exactly in the docs). The interface can stay either in the application project or in the new library, that's up to you and is a matter of convenience.

          Read and abide by the Qt Code of Conduct

          1 Reply Last reply
          2
          • D Offline
            D Offline
            Defohin
            wrote on 12 Jan 2017, 13:33 last edited by Defohin 1 Dec 2017, 13:37
            #9

            @kshegunov I tried to add this:

            myprojectglobal.h

            #ifndef MYPROJECTGLOBAL_HPP
            #define MYPROJECTGLOBAL_HPP
            
            #include <QtCore/qglobal.h>
            
            #if defined(MYPROJECT_LIBRARY)
            #  define MYPROJECT_EXPORT Q_DECL_EXPORT
            #else
            #  define MYPROJECT_EXPORT Q_DECL_IMPORT
            #endif
            
            #endif // MYPROJECTGLOBAL_HPP
            

            myproject.pro

            DEFINES += MYPROJECT_LIBRARY
            

            plugininterface.hpp

            #ifndef PLUGININTERFACE_HPP
            #define PLUGININTERFACE_HPP
            
            #include "myprojectglobal.hpp"
            #include <QtPlugin>
            
            class MYPROJECT_EXPORT PluginInterface
            {
            public:
                virtual ~PluginInterface() {}
            };
            
            #define PluginInterface_iid "PluginInterface/1.0"
            
            Q_DECLARE_INTERFACE(PluginInterface, PluginInterface_iid)
            
            #endif // PLUGININTERFACE_HPP
            

            abstractplugin.hpp

            #ifndef ABSTRACTPLUGIN_HPP
            #define ABSTRACTPLUGIN_HPP
            
            #include "plugininterface.hpp"
            
            class MYPROJECT_EXPORT AbstractPlugin : public QObject, public PluginInterface
            {
                Q_OBJECT
                Q_INTERFACES(PluginInterface)
            };
            
            #endif // ABSTRACTPLUGIN_HPP
            

            And now I'm getting these errors:

            moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual __cdecl PluginInterface::~PluginInterface(void)" (_imp??1PluginInterface@@UEAA@XZ) referenced in function "int public: __cdecl PluginFoo::PluginFoo(void)'::1'::dtor$0" (?dtor$0@?0???0PluginFoo@@QEAA@XZ@4HA)

            moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: __cdecl PluginInterface::PluginInterface(void)" (_imp??0PluginInterface@@QEAA@XZ) referenced in function "public: __cdecl PluginFoo::PluginFoo(void)" (??0PluginFoo@@QEAA@XZ)

            moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual void * __cdecl AbstractPlugin::qt_metacast(char const *)" (_imp?qt_metacast@AbstractPlugin@@UEAAPEAXPEBD@Z) referenced in function "public: virtual void * __cdecl PluginFoo::qt_metacast(char const *)" (?qt_metacast@PluginFoo@@UEAAPEAXPEBD@Z)

            moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual int __cdecl AbstractPlugin::qt_metacall(enum QMetaObject::Call,int,void * *)" (_imp?qt_metacall@AbstractPlugin@@UEAAHW4Call@QMetaObject@@HPEAPEAX@Z) referenced in function "public: virtual int __cdecl PluginFoo::qt_metacall(enum QMetaObject::Call,int,void * *)" (?qt_metacall@PluginFoo@@UEAAHW4Call@QMetaObject@@HPEAPEAX@Z)

            moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: __cdecl AbstractPlugin::AbstractPlugin(void)" (_imp??0AbstractPlugin@@QEAA@XZ) referenced in function "public: __cdecl PluginFoo::PluginFoo(void)" (??0PluginFoo@@QEAA@XZ)

            moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual __cdecl AbstractPlugin::~AbstractPlugin(void)" (_imp??1AbstractPlugin@@UEAA@XZ) referenced in function "public: virtual __cdecl PluginFoo::~PluginFoo(void)" (??1PluginFoo@@UEAA@XZ)

            moc_pluginfoo.obj:-1: error: LNK2001: unresolved external symbol "__declspec(dllimport) public: static struct QMetaObject const AbstractPlugin::staticMetaObject" (_imp?staticMetaObject@AbstractPlugin@@2UQMetaObject@@B)

            ....\bin\plugins\pluginfoo.dll:-1: error: LNK1120: 7 unresolved externals

            J 1 Reply Last reply 12 Jan 2017, 13:37
            0
            • D Defohin
              12 Jan 2017, 13:33

              @kshegunov I tried to add this:

              myprojectglobal.h

              #ifndef MYPROJECTGLOBAL_HPP
              #define MYPROJECTGLOBAL_HPP
              
              #include <QtCore/qglobal.h>
              
              #if defined(MYPROJECT_LIBRARY)
              #  define MYPROJECT_EXPORT Q_DECL_EXPORT
              #else
              #  define MYPROJECT_EXPORT Q_DECL_IMPORT
              #endif
              
              #endif // MYPROJECTGLOBAL_HPP
              

              myproject.pro

              DEFINES += MYPROJECT_LIBRARY
              

              plugininterface.hpp

              #ifndef PLUGININTERFACE_HPP
              #define PLUGININTERFACE_HPP
              
              #include "myprojectglobal.hpp"
              #include <QtPlugin>
              
              class MYPROJECT_EXPORT PluginInterface
              {
              public:
                  virtual ~PluginInterface() {}
              };
              
              #define PluginInterface_iid "PluginInterface/1.0"
              
              Q_DECLARE_INTERFACE(PluginInterface, PluginInterface_iid)
              
              #endif // PLUGININTERFACE_HPP
              

              abstractplugin.hpp

              #ifndef ABSTRACTPLUGIN_HPP
              #define ABSTRACTPLUGIN_HPP
              
              #include "plugininterface.hpp"
              
              class MYPROJECT_EXPORT AbstractPlugin : public QObject, public PluginInterface
              {
                  Q_OBJECT
                  Q_INTERFACES(PluginInterface)
              };
              
              #endif // ABSTRACTPLUGIN_HPP
              

              And now I'm getting these errors:

              moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual __cdecl PluginInterface::~PluginInterface(void)" (_imp??1PluginInterface@@UEAA@XZ) referenced in function "int public: __cdecl PluginFoo::PluginFoo(void)'::1'::dtor$0" (?dtor$0@?0???0PluginFoo@@QEAA@XZ@4HA)

              moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: __cdecl PluginInterface::PluginInterface(void)" (_imp??0PluginInterface@@QEAA@XZ) referenced in function "public: __cdecl PluginFoo::PluginFoo(void)" (??0PluginFoo@@QEAA@XZ)

              moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual void * __cdecl AbstractPlugin::qt_metacast(char const *)" (_imp?qt_metacast@AbstractPlugin@@UEAAPEAXPEBD@Z) referenced in function "public: virtual void * __cdecl PluginFoo::qt_metacast(char const *)" (?qt_metacast@PluginFoo@@UEAAPEAXPEBD@Z)

              moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual int __cdecl AbstractPlugin::qt_metacall(enum QMetaObject::Call,int,void * *)" (_imp?qt_metacall@AbstractPlugin@@UEAAHW4Call@QMetaObject@@HPEAPEAX@Z) referenced in function "public: virtual int __cdecl PluginFoo::qt_metacall(enum QMetaObject::Call,int,void * *)" (?qt_metacall@PluginFoo@@UEAAHW4Call@QMetaObject@@HPEAPEAX@Z)

              moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: __cdecl AbstractPlugin::AbstractPlugin(void)" (_imp??0AbstractPlugin@@QEAA@XZ) referenced in function "public: __cdecl PluginFoo::PluginFoo(void)" (??0PluginFoo@@QEAA@XZ)

              moc_pluginfoo.obj:-1: error: LNK2019: unresolved external symbol "__declspec(dllimport) public: virtual __cdecl AbstractPlugin::~AbstractPlugin(void)" (_imp??1AbstractPlugin@@UEAA@XZ) referenced in function "public: virtual __cdecl PluginFoo::~PluginFoo(void)" (??1PluginFoo@@UEAA@XZ)

              moc_pluginfoo.obj:-1: error: LNK2001: unresolved external symbol "__declspec(dllimport) public: static struct QMetaObject const AbstractPlugin::staticMetaObject" (_imp?staticMetaObject@AbstractPlugin@@2UQMetaObject@@B)

              ....\bin\plugins\pluginfoo.dll:-1: error: LNK1120: 7 unresolved externals

              J Offline
              J Offline
              jsulm
              Lifetime Qt Champion
              wrote on 12 Jan 2017, 13:37 last edited by
              #10

              @Defohin Do you link your pluginfoo plugin against the lib containing AbstractPlugin and PluginInterface?

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              D 1 Reply Last reply 12 Jan 2017, 20:14
              1
              • J jsulm
                12 Jan 2017, 13:37

                @Defohin Do you link your pluginfoo plugin against the lib containing AbstractPlugin and PluginInterface?

                D Offline
                D Offline
                Defohin
                wrote on 12 Jan 2017, 20:14 last edited by
                #11

                @jsulm What you mean? The whole code I have is here.

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  SGaist
                  Lifetime Qt Champion
                  wrote on 12 Jan 2017, 20:23 last edited by
                  #12

                  Hi,

                  The usual setup when building a plugin based application is to have the plugin interfaces definitions and related code in a library that you will link to both the plugin and the application.

                  That's what is suggested here.

                  Interested in AI ? www.idiap.ch
                  Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                  D 1 Reply Last reply 12 Jan 2017, 20:26
                  1
                  • S SGaist
                    12 Jan 2017, 20:23

                    Hi,

                    The usual setup when building a plugin based application is to have the plugin interfaces definitions and related code in a library that you will link to both the plugin and the application.

                    That's what is suggested here.

                    D Offline
                    D Offline
                    Defohin
                    wrote on 12 Jan 2017, 20:26 last edited by
                    #13

                    @SGaist I'm really struggling to understand, can you provide an example, please?

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on 12 Jan 2017, 20:40 last edited by SGaist 1 Dec 2017, 20:40
                      #14

                      Roughly :
                      pluginfoo.pro

                      QT          += core gui
                      TARGET       = pluginfoo
                      TEMPLATE     = lib
                      CONFIG      += plugin
                      DESTDIR      = $$OUTPWD/bin/plugins
                      LIBS += -L$$OUTPWD/lib -lmycoollib
                      DEFINES     += QT_DEPRECATED_WARNINGS
                      INCLUDEPATH += ../mycoollib
                      SOURCES     += pluginfoo.cpp
                      HEADERS     += pluginfoo.hpp
                      DISTFILES   += pluginfoo.json
                      

                      mycoollib.pro

                      QT          += core gui
                      TARGET       = mycoollib
                      TEMPLATE  = lib
                      DESTDIR      = $$OUTPWD/lib
                      INCLUDEPATH += .
                      SOURCES     += \
                          abstractplugin.cpp
                      HEADERS     += \
                          plugininterface.hpp
                          abstractplugin.hpp
                      
                      

                      myproject.pro

                      QT      += core gui widgets xml network
                      TARGET   = myproject
                      TEMPLATE = app
                      DESTDIR  = $$OUTPWD/bin
                      LIBS += -L$$OUTPWD/lib -lmycoollib
                      INCLUDEPATH += ../mycoollib
                      DEFINES += QT_DEPRECATED_WARNINGS
                      SOURCES += src/main.cpp \
                                 gui/myprojectwindow.cpp
                      
                      HEADERS += gui/myprojectwindow.hpp
                      

                      Project structure

                      mycoolproject \
                      ---- mycoollib
                      ---- pluginfoo
                      ---- myproject
                      

                      mycoolproject being a SUBDIR project building first mycoollib and then pluginfoo and myproject.

                      Interested in AI ? www.idiap.ch
                      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                      D 1 Reply Last reply 12 Jan 2017, 20:44
                      1
                      • S SGaist
                        12 Jan 2017, 20:40

                        Roughly :
                        pluginfoo.pro

                        QT          += core gui
                        TARGET       = pluginfoo
                        TEMPLATE     = lib
                        CONFIG      += plugin
                        DESTDIR      = $$OUTPWD/bin/plugins
                        LIBS += -L$$OUTPWD/lib -lmycoollib
                        DEFINES     += QT_DEPRECATED_WARNINGS
                        INCLUDEPATH += ../mycoollib
                        SOURCES     += pluginfoo.cpp
                        HEADERS     += pluginfoo.hpp
                        DISTFILES   += pluginfoo.json
                        

                        mycoollib.pro

                        QT          += core gui
                        TARGET       = mycoollib
                        TEMPLATE  = lib
                        DESTDIR      = $$OUTPWD/lib
                        INCLUDEPATH += .
                        SOURCES     += \
                            abstractplugin.cpp
                        HEADERS     += \
                            plugininterface.hpp
                            abstractplugin.hpp
                        
                        

                        myproject.pro

                        QT      += core gui widgets xml network
                        TARGET   = myproject
                        TEMPLATE = app
                        DESTDIR  = $$OUTPWD/bin
                        LIBS += -L$$OUTPWD/lib -lmycoollib
                        INCLUDEPATH += ../mycoollib
                        DEFINES += QT_DEPRECATED_WARNINGS
                        SOURCES += src/main.cpp \
                                   gui/myprojectwindow.cpp
                        
                        HEADERS += gui/myprojectwindow.hpp
                        

                        Project structure

                        mycoolproject \
                        ---- mycoollib
                        ---- pluginfoo
                        ---- myproject
                        

                        mycoolproject being a SUBDIR project building first mycoollib and then pluginfoo and myproject.

                        D Offline
                        D Offline
                        Defohin
                        wrote on 12 Jan 2017, 20:44 last edited by
                        #15

                        @SGaist Do I have to link with -l every single plugin I have? Or I can just provide a path like -L and it's going to work?

                        I will try to modify here based on your example.

                        1 Reply Last reply
                        0
                        • S Offline
                          S Offline
                          SGaist
                          Lifetime Qt Champion
                          wrote on 12 Jan 2017, 20:49 last edited by SGaist 1 Dec 2017, 20:50
                          #16

                          You don't link the plugins. You link your plugins against that common library.

                          Yes, you have to use both -land -L.

                          -L just tells the linker where to look at.

                          Interested in AI ? www.idiap.ch
                          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                          D 1 Reply Last reply 13 Jan 2017, 03:36
                          1
                          • S SGaist
                            12 Jan 2017, 20:49

                            You don't link the plugins. You link your plugins against that common library.

                            Yes, you have to use both -land -L.

                            -L just tells the linker where to look at.

                            D Offline
                            D Offline
                            Defohin
                            wrote on 13 Jan 2017, 03:36 last edited by
                            #17

                            @SGaist It works, but I have another question now.

                            I named the "commonlib" to "pluginmanager" this class will hold information about plugins, load, unload and so on using QPluginLoader, but... when I try to use it on the main application including the header pluginmanager.hpp it says that it cannot open the file, even if I have the INCLUDEPATH += ../pluginmanager. On Qt Creator it does work, I'm able to ctrl+click, etc, but when I try to compile I get this error.

                            J 1 Reply Last reply 13 Jan 2017, 05:13
                            0
                            • D Defohin
                              13 Jan 2017, 03:36

                              @SGaist It works, but I have another question now.

                              I named the "commonlib" to "pluginmanager" this class will hold information about plugins, load, unload and so on using QPluginLoader, but... when I try to use it on the main application including the header pluginmanager.hpp it says that it cannot open the file, even if I have the INCLUDEPATH += ../pluginmanager. On Qt Creator it does work, I'm able to ctrl+click, etc, but when I try to compile I get this error.

                              J Offline
                              J Offline
                              jsulm
                              Lifetime Qt Champion
                              wrote on 13 Jan 2017, 05:13 last edited by jsulm
                              #18

                              @Defohin Did you run qmake again after changing the pro file? After qmake you should do a complete rebuild.

                              https://forum.qt.io/topic/113070/qt-code-of-conduct

                              D 1 Reply Last reply 13 Jan 2017, 05:21
                              0
                              • J jsulm
                                13 Jan 2017, 05:13

                                @Defohin Did you run qmake again after changing the pro file? After qmake you should do a complete rebuild.

                                D Offline
                                D Offline
                                Defohin
                                wrote on 13 Jan 2017, 05:21 last edited by
                                #19

                                @jsulm It works, but now I'm getting unresolved external symbol on the main project when trying to use PluginManager manager on the MyProjectWindow, and I have LIBS += -L../libs -lpluginmanager on the pro file.

                                myprojectwindow.obj:-1: error: LNK2019: unresolved external symbol "public: __cdecl PluginManager::PluginManager(class QObject *)" (??0PluginManager@@QEAA@PEAVQObject@@@Z) referenced in function "public: __cdecl MyProjectWindow::MyProjectWindow(class QWidget *)" (??0MyProjectWindow@@QEAA@PEAVQWidget@@@Z)

                                J 1 Reply Last reply 13 Jan 2017, 05:27
                                0
                                • D Defohin
                                  13 Jan 2017, 05:21

                                  @jsulm It works, but now I'm getting unresolved external symbol on the main project when trying to use PluginManager manager on the MyProjectWindow, and I have LIBS += -L../libs -lpluginmanager on the pro file.

                                  myprojectwindow.obj:-1: error: LNK2019: unresolved external symbol "public: __cdecl PluginManager::PluginManager(class QObject *)" (??0PluginManager@@QEAA@PEAVQObject@@@Z) referenced in function "public: __cdecl MyProjectWindow::MyProjectWindow(class QWidget *)" (??0MyProjectWindow@@QEAA@PEAVQWidget@@@Z)

                                  J Offline
                                  J Offline
                                  jsulm
                                  Lifetime Qt Champion
                                  wrote on 13 Jan 2017, 05:27 last edited by
                                  #20

                                  @Defohin ../libs is a relative path, are you sure it is correct?
                                  Can you post the compiler/linker call just before the error message?
                                  As suggested by @SGaist : LIBS += -L$$OUTPWD/lib -lmycoollib (pluginmanager instead of mycoollib)

                                  https://forum.qt.io/topic/113070/qt-code-of-conduct

                                  D 1 Reply Last reply 13 Jan 2017, 12:10
                                  0
                                  • J jsulm
                                    13 Jan 2017, 05:27

                                    @Defohin ../libs is a relative path, are you sure it is correct?
                                    Can you post the compiler/linker call just before the error message?
                                    As suggested by @SGaist : LIBS += -L$$OUTPWD/lib -lmycoollib (pluginmanager instead of mycoollib)

                                    D Offline
                                    D Offline
                                    Defohin
                                    wrote on 13 Jan 2017, 12:10 last edited by
                                    #21

                                    @jsulm I'm using $$OUTPWD now but it still doesn't work.

                                    J 1 Reply Last reply 13 Jan 2017, 12:11
                                    0
                                    • D Defohin
                                      13 Jan 2017, 12:10

                                      @jsulm I'm using $$OUTPWD now but it still doesn't work.

                                      J Offline
                                      J Offline
                                      jsulm
                                      Lifetime Qt Champion
                                      wrote on 13 Jan 2017, 12:11 last edited by
                                      #22

                                      @Defohin Is the resulting path correct and is the lib there?

                                      https://forum.qt.io/topic/113070/qt-code-of-conduct

                                      1 Reply Last reply
                                      0
                                      • D Offline
                                        D Offline
                                        Defohin
                                        wrote on 13 Jan 2017, 12:13 last edited by Defohin
                                        #23

                                        It's working now, I forgot to put MYPROJECT_EXPORT on PluginManager class.

                                        I love you guys ♥

                                        1 Reply Last reply
                                        0

                                        14/23

                                        12 Jan 2017, 20:40

                                        • Login

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