QT Platform Plugin Set Path
-
Hello there, I want DLL files from platforms, styles and imageformats folders to run in home directory. Can you help me?
Default:
-- platforms
---- qwindows.dll-- imageformats
---- qgif.dll
---- qicns.dll
---- qico.dll
---- qjpeg.dll-- Test.exe
Must be:
-- qwindows.dll
-- qgif.dll
-- qicns.dll
-- qico.dll
-- qjpeg.dll
-- Test.exe -
Hi and welcome to devnet,
Please show some patience and allows at least 24 hours before bumping your own thread. This is a voluntary driven forum and people may not even live in the same timezone as you.
As for issue, you cannot completely flatten the plugin structure. Qt has some expectations with regards to where it will look for specific plugins.
What is your current issue with it ?
-
Hi and welcome to devnet,
Please show some patience and allows at least 24 hours before bumping your own thread. This is a voluntary driven forum and people may not even live in the same timezone as you.
As for issue, you cannot completely flatten the plugin structure. Qt has some expectations with regards to where it will look for specific plugins.
What is your current issue with it ?
-
@Mo1ra-ALP said in QT Platform Plugin Set Path:
wmprotect
Then you should talk with these folks so see how to properly handle your use case.
The other solution is to do a static build but it has constraints depending on which license you use.
-
@Mo1ra-ALP said in QT Platform Plugin Set Path:
wmprotect
Then you should talk with these folks so see how to properly handle your use case.
The other solution is to do a static build but it has constraints depending on which license you use.
-
@Mo1ra-ALP said in QT Platform Plugin Set Path:
Isn't it possible to create a single exe in QT?
It is. You need static Qt build as @SGaist already mentioned.
-
@Mo1ra-ALP said in QT Platform Plugin Set Path:
Isn't it possible to create a single exe in QT?
It is. You need static Qt build as @SGaist already mentioned.
-
-
-
-
@jsulm I'm getting an error (QT 6.0.1)
'cmake' is not recognized as an internal or external command, operable program or batch file. 'cmake' is not recognized as an internal or external command, operable program or batch file.@Mo1ra-ALP What Qt version do you want to build? CMake is only needed if you build Qt6.
-
@Mo1ra-ALP What Qt version do you want to build? CMake is only needed if you build Qt6.
-
@Mo1ra-ALP If you want to build Qt6 install cmake first...
-
Exit:
C:\QT\6.1.0\Src>configure -static -release -no-exceptions + cd qtbase + C:\QT\6.1.0\Src\qtbase\configure.bat -top-level -static -release -no-exceptions CMake Error at qtbase/cmake/QtProcessConfigureArgs.cmake:227 (message): Unknown command line option '-no-exceptions'. Call Stack (most recent call first): qtbase/cmake/QtProcessConfigureArgs.cmake:531 (qtConfAddError) -
Exit:
C:\QT\6.1.0\Src>configure -static -release -no-exceptions + cd qtbase + C:\QT\6.1.0\Src\qtbase\configure.bat -top-level -static -release -no-exceptions CMake Error at qtbase/cmake/QtProcessConfigureArgs.cmake:227 (message): Unknown command line option '-no-exceptions'. Call Stack (most recent call first): qtbase/cmake/QtProcessConfigureArgs.cmake:531 (qtConfAddError)@Mo1ra-ALP said in QT Platform Plugin Set Path:
-no-exceptions
remove this parameter from your configure call...
You also should NEVER build inside source directory! Your source tree is now polluted with build artefacts... -
@Mo1ra-ALP said in QT Platform Plugin Set Path:
-no-exceptions
remove this parameter from your configure call...
You also should NEVER build inside source directory! Your source tree is now polluted with build artefacts... -
No it's not,
Nuke your sources and get new one, 6.1 having been released it's likely a better idea to use that one.Then make a folder somewhere, go inside it and then call configure from there.
