@TonyRietwyk said in Qt 5.15.5 cannot load custom designer plugin:
Does the installed Designer need 64-bit dll's?
Designer or Creator? (Qt Creator has an embedded version of Qt Designer)
Recent releases of Qt Creator are 64-bit. You can check by clicking Help > About Qt Creator...
I'm not sure about the bitness of the stand-alone Qt Designer .
API-MS-WIN-CORE-SYNCH-L1-2-0.DLL seems to be causing a cyclic dependency with KERNEL32.dll.
The API-MS-*.dll are usually false positives. Ignore them.
I have Qt5.15.5/5.15.5/msvc2019/bin in my system path.
This often causes problems... I highly recommend you don't put Qt in your PATH. You can break other apps on your PC that depend on a different version of Qt.
@TonyRietwyk said in Qt 5.15.5 cannot load custom designer plugin:
Turns out the problem was fixed by copying zlib1.dll into the 5.15.5\msvc2019\bin folder
That should go into the folder which contains your plugin, not into your Qt folder.
Again, I recommend you remove Qt from your PATH.
Related to my post...
Yesterday Cristian Adam has published another interesting article on Qt's blog about Building Qt Creator plugins with GitHub Actions.
Make sure that all needed dlls are found when trying to load the ibase plugin -> check with Dependency Walker if the ibase plugin has all it's dependencies available.
@fcarney I can't beleive I missed your question. Comparing with Heob, Deleaker provides more features like taking snapshot at any moment, and comparing them later. Besides heap allocations, Deleaker also tracks COM/ActiveX/GDI/USER32 leaks etc.
@SGaist Thanks for the suggestion.
Sorry for the very delayed reply.
I tried few options as in the mentioned link.
Adding the qrc path in the application's pro file worked.
Thank you!!
@BobZ
Hi
You need to compile the plugin with same compiler as Creator itself
That means visual studio compiler ( mingw wont work) and also same version of
Qt ca. So a Qt 4.8 plugin wont load in a much newer creator.
[image: Qrnzow.png]
so here i should use around Qt 5.11 and vs2015, 32 bit.
This is due to the plugins being DLLs and it simply cant load
Dlls produced by much older compiler and the Qt used must also be
at lease same major version.
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/
Hi
the include in the ui_ comes from
QString WorldTimeClockPlugin::includeFile() const
{
return QStringLiteral("worldtimeclock.h");
}
but it seems the error contains no filename ??
