@anp405, my first guess would be that by setting PYTHONPATH you are losing the location of PyQt5 package. This depends on your Python and environment setup, but if there is some PYTHONPATH existing, you are overriding it completely instead of complementing. You can verify this by opening a new command line session, setting PYTHONPATH to wherever your code sets it, then running Python interpreter and trying to import PyQt5. Another guess would be that your child process uses different Python environment (e.g. built-in system Python 2), which does not have PyQt5 installed in its site-packages.

One thing you can try is to use the "-I" and "-L" options of the configure script passing there the paths to your MySQL include and library folder.

@DSpider great! please don't forget to mark your post as solved. Thanks.

@JonB @MrShawn Thanks you two for clarifying. After downloading/installing a MySQL server in a school computer, I could build/run my app on my computer and insert/update data successfully to the server. That part's all good. Thanks from y'all. Marking as solved.

You should only use -developer-build is you plant to contribute to Qt. If you're building for yourself, there is no need to add that flag.

Why do you have your plugins and application all in the same project ?

Thanks for your input, the problem was that the DLL was actually not in the place where it should have been, my mistake.

SOLUTION with the help of @mrjj i found solution. It's just that instructions were not clear on tutorial Steps get the Qt creator source : git clone --recursive https://code.qt.io/qt-creator/qt-creator.git set qmake version . your qmake version should be close to the qt version you are using . for e.g. if you are building for 5.10 your qmake should also use 5.10. you can set qmake version by sudo mv /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf_orig sudo vim /usr/share/qtchooser/my_Qt_5.10.0_Desktop_gcc_x64.conf <Qt_dir>/5.10.0/gcc_64/bin <Qt_dir>/5.10.0/gcc_64/lib ln -s /usr/share/qtchooser/my_Qt_5.10.0_Destop_gcc_x64.conf /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf check qmake by qmake --version mkdir qt-creator-build cd qt-creator-build qmake ../qt-creator/qtcreator.pro 4. ``` cd qt-creator-build make qmake_all make -j <number-of-cpu-cores+1> wait for some time . it will take long time to build. now you have both source and build of Qt creator . Now just follow the wizard and point the qt soruce and build locations build and run voila !! \0/

@kshegunov yes that is exactly what I was wondering. I was not sure if plugins can be loaded into other C++ plugins or not. I will give this a shot. @SGaist good point about creating a library. I think isolating the communication API into a dynamic library would be an even better solution as you suggested. I will have to do some refactoring. Thank you both for sharing the quick and helpful response!

Hi Also for my first attempt i used http://doc.qt.io/qt-5/qtwidgets-tools-echoplugin-example.html which is pretty small and easy to understand.

@VRHans seems i was wrong afterall: QResource::registerResource() But you have to provide the resource binary (.rcc file). Created with the following command: rcc -binary myresource.qrc -o myresource.rcc

Because it's a dependency of the plugin not of the application.

It was indeed compiling with mingw which was the issue. Thanks mrjj and jsulm for the fast answers.

@ghielmetti Hi Normally I do have the .h file in the project folder and point to that in the Promote dialog. Im not sure it will take a full path in the dialog but I never tried :)

Okay... finally i solved it. Nothing to do with .pro file or PLUGIN macro. It was a basic PATH issue. qmake was searching for 'plugin' directory in /PREFIX path not in /SYSROOT/PREFIX path. I just copied all plugin directory from /SYSROOT/PREFIX to /PREFIX directory. I know this may not be the right way, but it temporarily solved my issue. If someone could suggest the correct solution please let me know.

@zappy Hello. Have you looked at the bug report in the other thread you were following? Apparently there were some bug in the static building for Qt 5.5 and it's fixed in Qt 5.6.1 (https://bugreports.qt.io/browse/QTBUG-51071). So aside from upgrading, am at a loss ...

...crickets?

@Jakob You're welcome. I was a bit concerned that I'm not making my explanation clear enough, but happily that doesn't seem to be the case. Good luck! Kind regards.

Thank you for the reply. After the user went to Windows Update and installed "additional packages" his problem went away. VS 2013 compiler. We distribute: msvcp100.dll msvcp120.dll msvcr100.dll msvcr120.dll I will have the next person with the issue try to run the Dependency Walker. Thank you! Ben

Does anyone have instructions for Qt static build that is version 5.4 or greater?

@JKSH, @hskoglund, thank you very much! Using both qt.conf file and "QMAKE_LFLAGS += -Wl,--rpath=\$$ORIGIN/lib" line in my app's .pro file helped me.

@Chris-Kawa Wow, never seen before. Can I reopen the powerfull wizzard for a just created project again to add new classes incl. plugins ? It seem not to be possible. To the QDesignerCustomWidgetCollectionInterface: I change the project to importing only the interface "with the long name" and must remove the Q_PLUGIN_METADATA macro of all single widgets!

ACGuiApplication is a symbol that comes from that other library so it's not provided by libCommon. Have a look at the link_prl and create_prl qmake options. They should provide you with all the dependencies needed automatically.

Yes, same SP also, that's a Microsoft thing, nothing Qt specific. Currently, you have to edit the title prepending [solved]. Don't forget to also vote the answer(s) in a topic that you find interesting, useful that will help other users find the most appropriate answer to a question