Плагин платформы qt windows для виндовс 7 - Доктор Windows

Qt6 Source Packages

Qt 6.4.2 Source Packages:

The source code is available:

For Windows users as a single zip file (1.1 G) (Info)
For Linux/macOS users as a tar.xz file (703 MB) (Info)

You can get split source packages from here. Or visit the repository at code.qt.io.

Qt 6.2.4 Source Packages:

The source code is available:

For Windows users as a single zip file (1.0 G) (Info)
For Linux/macOS users as a tar.xz file (631 MB) (Info)

You can get split source packages from here. Or visit the repository at code.qt.io.

Older Qt Versions

All older versions of Qt are available in the archive.

Qt 5.15.x Source Packages

The source code is available:

For Windows users as a single zip file (962 MB) (Info)
For Linux/macOS users as a tar.xz file (560 MB) (Info)

You can get split source packages from here. Or visit the repository at code.qt.io.

Pre-releases

Looking for Qt 6.5 Beta? Packages are available in Qt Online Installer. Additionally source packages are available here.

Источник

Edit:
Some people started to mark my question as a duplicate. Do not forget that many similar questions existed when I asked this one (see e.g. the list below). However, none of these answers solved my problem. After a long search I found a comment which had been ignored by all users pointing to the missing lib. Now, many months later, the comment has been changed to an answer. However, when I answered this question by msyself I intended to help other people by directly providing the solution. This should not be forgotten and so far my answer helped a lot of people. Therefore my question is definitely not a duplicate. By the way: The accepted answer within the provided link on top does not solve the problem!

Yes, i used the search:

Failed to load platform plugin «windows». Available platforms are : Error

Deploying Qt C++ Application from Visual Studio qwindows.dll error

failed to load platform plugin «windows» Available platforms are: windows, minimal

However, in my case the problem still persists. I am using Qt 5.1.1 with Visual Studio 2012 and developed my Application on Windows 7 with Qt Creator 2.8.1. Application is compiled in «Release»-mode and can be executed if directly started with Qt Creator.

However, when starting from the «release»-Folder, i get the following message:

This application failed to start because it could not find or load the
Qt platform plugin «windows». Available platform plugins are:
minimal, offscreen, windows.

Folder structure looks like this:

release
+ gui.exe
+ icudt51.dll
+ icuin51.dll
+ icuuc51.dll
+ libGLESv2.dll
+ Qt5Core.dll
+ Qt5Gui.dll
+ Qt5Widgets.dll
+ platforms

Platforms is the folder directly copied from QtQt5.1.15.1.1msvc2012pluginsplatforms including e.g. qwindows.dll. Does not matter if I rename it to «platform» as some other users did. Qt is still not finding the «platform plugin windows», where is my mistake?

asked Dec 10, 2013 at 13:16

Okay, as posted here https://stackoverflow.com/a/17271172/1458552 without much attention by other users:

The libEGL.dll was missing! Even though this has not been reported when trying to start the application (all other *.dlls such as Qt5Gui.dll had been reported).

answered Dec 10, 2013 at 13:43

AnonymousAnonymous

4,5778 gold badges47 silver badges61 bronze badges

I created a platforms directory next to my exe location and put qwindows.dll inside, but I still received the «Failed to load platform plugin «windows». Available platforms are: windows» error.

I had copied qwindows.dll from C:QtQt5.1.1ToolsQtCreatorbinpluginsplatforms, which is not the right location. I looked at the debug log from running in Qt Creator and found that my app was looking in C:QtQt5.1.15.1.1mingw48_32pluginsplatforms when it ran in the debugger.

When I copied from C:QtQt5.1.15.1.1mingw48_32pluginsplatforms, everything worked fine.

answered Jun 12, 2014 at 19:30

BrandonBrandon

5514 silver badges2 bronze badges

The release is likely missing a library/plugin or the library is in the wrong directory and or from the wrong directory.

Qt intended answer: Use windeployqt. see last paragraph for explanation

Manual answer:

Create a folder named «platforms» in the same directory as your application.exe file. Copy and paste the qwindows.dll, found in the /bin of whichever compiler you used to release your application, into the «platforms» folder. Like magic it works. If the .dll is not there check plugins/platforms/ ( with plugins/ being in the same directory as bin/ ) <— PfunnyGuy’s comment.

It seems like a common issue is that the .dll was taken from the wrong compiler bin. Be sure to copy your the qwindows.dll from the same compiler as the one used to release your app.

Qt comes with platform console applications that will add all dependencies (including ones like qwindows.dll and libEGL.dll) into the folder of your deployed executable. This is the intended way to deploy your application, so you do not miss any libraries (which is the main issue with all of these answers). The application for windows is called windeployqt. There is likely a deployment console app for each OS.

answered Aug 10, 2017 at 2:10

Setting the QT_QPA_PLATFORM_PLUGIN_PATH environment variable to %QTDIR%pluginsplatforms worked for me.

It was also mentioned here and here.

answered Oct 30, 2016 at 12:38

Jim G.Jim G.

15k22 gold badges104 silver badges164 bronze badges

I ran into this and none of the answers I could find fixed it for me.

My colleauge has Qt (5.6.0) installed on his machine at:
C:QtQt5.6.05.6msvc2015plugins
I have Qt (5.6.2) installed in the same location.

I learned from this post: http://www.tripleboot.org/?p=536, that the Qt5Core.dll has a location to the plugins written to it when Qt is first installed.
Since my colleague’s and my Qt directories were the same, but different version of Qt were installed, a different qwindows.dll file is needed. When I ran an exe deployed by him, it would use my C:QtQt5.6.05.6msvc2015pluginsplatformsqwindows.dll file instead of the one located next to the executable in the .platforms subfolder.

To get around this, I added the following line of code to the application which seems to force it to look next to the exe for the ‘platforms’ subfolder before it looks at the path in the Qt5Core.dll.

QCoreApplication::addLibraryPath(".");

I added the above line to the main method before the QApplication call like this:

int main( int argc, char *argv[] )
{
    QCoreApplication::addLibraryPath(".");
    QApplication app( argc, argv );
    ...
    return app.exec();
}

answered Mar 13, 2017 at 15:38

JoelJoel

1372 silver badges7 bronze badges

create dir platforms and copy qwindows.dll to it, platforms and app.exe are in the same dir

cd app_dir mkdir platforms xcopy qwindows.dll platformsqwindows.dll

Folder structure
+ app.exe + platformsqwindows.dll

answered Mar 8, 2018 at 9:24

KunMing XieKunMing Xie

1,57316 silver badges15 bronze badges

I found another solution. Create qt.conf in the app folder as such:

[Paths]
Prefix = .

And then copy the plugins folder into the app folder and it works for me.

answered Aug 6, 2017 at 18:56

Peter QuiringPeter Quiring

1,5881 gold badge15 silver badges21 bronze badges

For anyone coming from QT version 5.14.0, it took me 2 days to find this piece statment of bug:

windeployqt does not work for MinGW QTBUG-80763 Will be fixed in
5.14.1

https://wiki.qt.io/Qt_5.14.0_Known_Issues

So be aware. Using windeployqt withMinGW will give the same error stated here.

answered Jan 17, 2020 at 3:41

Yahya TawilYahya Tawil

3873 silver badges10 bronze badges

I had this problem while using QT 5.6, Anaconda 4.3.23, python 3.5.2 and pyinstaller 3.3.
I had created a python program with an interface developed using QTcreator, but had to deploy it to other computers, therefore I needed to make an executable, using pyinstaller.

I’ve found that the problem was solved on my computer if I set the following environment variables:

QT_QPA_PLATFORM_PLUGIN_PATH: %QTDIR%pluginsplatforms

QTDIR: C:Miniconda3pkgsqt-5.6.2-vc14_3Library

But this solution only worked on my PC that had conda and qt installed in those folders.

To solve this and make the executable work on any computer, I’ve had to edit the «.spec» (file first generated by pyinstaller) to include the following line:

datas=[(
‘C:Miniconda3pkgsqt-5.6.2-vc14_3Librarypluginsplatforms*.dll’,
‘platforms’ ),]

This solution is based on the answers of Jim G. and CrippledTable

answered Oct 3, 2017 at 12:34

For me the solution was to correct the PATH variable. It had Anaconda3Librarybin as one of the first paths. This directory contains some Qt libraries, but not all. Apparently, that is a problem. Moving C:ProgramsQt5.12.3msvc2017_64bin to the front of PATH solved the problem for me.

answered Apr 29, 2019 at 13:23

Most of these answers contain good (correct) info, but in my case, there was still something missing.

My app is built as a library (dll) and called by a non-Qt application. I used windeployqt.exe to set up the Qt dlls, platforms, plugins, etc. in the install directory, but it still couldn’t find the platform. After some experimentation, I realized the application’s working directory was set to a different folder. So, I grabbed the directory in which the dll «lived» using GetModuleHandleExA and added that directory to the Qt library path at runtime using

QCoreApplication::addLibraryPath(<result of GetModuleHandleExA>);

This worked for me.

answered May 9, 2018 at 13:14

I had the same problem and solved it by applying several things.
The first, if it is a program that you did with Qt.

In the folder (in my case) of «C: Qt Qt5.10.0 5.10.0 msvc2017_64 plugins» you find other folders, one of them is «platforms». That «platforms» folder is going to be copied next to your .exe executable. Now, if you get the error 0xc000007d is that you did not copy the version that was, since it can be 32bits or 64.

If you continue with the errors is that you lack more libraries. With the «Dependency Walker» program you can detect some of the missing folders. Surely it will indicate to you that you need an NVIDIA .dll, and it tells you the location.

Another way, instead of using «Dependency Walker» is to copy all the .dll from your «C: Windows System32» folder next to your executable file. Execute your .exe and if everything loads well, so you do not have space occupied in dll libraries that you do not need or use, use the .exe program with all your options and without closing the .exe you do is erase all the .dll that you just copied next to the .exe, so if those .dll are being used by your program, the system will not let you erase, only removing those that are not necessary.

I hope this solution serves you.

Remember that if your operating system is 64 bits, the libraries will be in the System32 folder, and if your operating system is 32 bits, they will also be in the System32 folder. This happens so that there are no compatibility problems with programs that are 32 bits in a 64-bit computer.
The SysWOW64 folder contains the 32-bit files as a backup.

answered Mar 23, 2018 at 17:41

For a MinGW platform and if you are compiling a Debug target by a hand made CMakeLists.txt written ad hoc you need to add the qwindows.dll to the platform dir as well.
The windeployqt executable does its work well but it seems that for some strange reason the CMake build needs the release variant as well.
In summary it will be better to have both the qwindows.dll and qwindowsd.dll in your platform directory.
I did not notice the same strange result when importing the CMake project in QtCreator and then running the build procedure.
Compiling on the command line the CMake project seems to trigger the qwindows.dll dependency either if the correct one for the Debug target is set in place (qwindowsd.dll)

answered Oct 11, 2017 at 9:40

Use this batch file: RunWithQt.bat

@echo off
set QTDIR=C:QtQt5.1.15.1.1msvc2012bin
set QT_QPA_PLATFORM_PLUGIN_PATH=%QTDIR%pluginsplatforms
start %1

to use it, drag your gui.exe file and drop it on the RunWithQt.bat in explorer,
or call RunWithQt gui.exe from the command line

answered Feb 8, 2018 at 15:54

If you have Anaconda installed I recomend you to uninstall it and try installing python package from source, i fixed this problem in this way

answered Mar 27, 2018 at 19:39

The application qtbase/bin/windeployqt.exe deploys automatically your application. If you start a prompt with envirenmentvariables set correctly, it deploys to the current directory.
You find an example of script:

@echo off
set QTDIR=E:QT5110vc2017

set INCLUDE=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFCinclude;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726include;C:Program Files (x86)Windows KitsNETFXSDK4.6.1includeum;C:Program Files (x86)Windows Kits10include10.0.14393.0ucrt;C:Program Files (x86)Windows Kits10include10.0.14393.0shared;C:Program Files (x86)Windows Kits10include10.0.14393.0um;C:Program Files (x86)Windows Kits10include10.0.14393.0winrt;C:Program Files (x86)Windows Kits10include10.0.14393.0cppwinrt

set LIB=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;C:Program Files (x86)Windows KitsNETFXSDK4.6.1libumx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0ucrtx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0umx86;

set LIBPATH=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86storereferences;C:Program Files (x86)Windows Kits10UnionMetadata10.0.17134.0;C:ProgramFiles (x86)Windows Kits10References10.0.17134.0;C:WindowsMicrosoft.NETFrameworkv4.0.30319;

Path=%QTDIR%qtbasebin;%PATH%
set VCIDEInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEVC
set VCINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVC
set VCToolsInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.11.25503
set VisualStudioVersion=15.0
set VS100COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 10.0Common7Tools
set VS110COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 11.0Common7Tools
set VS120COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools
set VS150COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7Tools
set VS80COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 8Common7Tools
set VS90COMNTOOLS=c:Program Files (x86)Microsoft Visual Studio 9.0Common7Tools
set VSINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017Enterprise
set VSSDK110Install=C:Program Files (x86)Microsoft Visual Studio 11.0VSSDK
set VSSDK150INSTALL=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVSSDK
set WindowsLibPath=C:Program Files (x86)Windows Kits10UnionMetadata;C:Program Files (x86)Windows Kits10References
set WindowsSdkBinPath=C:Program Files (x86)Windows Kits10bin
set WindowsSdkDir=C:Program Files (x86)Windows Kits10
set WindowsSDKLibVersion=10.0.14393.0
set WindowsSdkVerBinPath=C:Program Files (x86)Windows Kits10bin10.0.14393.0
set WindowsSDKVersion=10.0.14393.0
set WindowsSDK_ExecutablePath_x64=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Toolsx64
set WindowsSDK_ExecutablePath_x86=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Tools

mkdir C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
cd C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
copy /Y ..Releaseapplication.exe .
windeployqt application.exe
pause

answered Nov 23, 2018 at 9:03

MyGeertRoMyGeertRo

1311 silver badge3 bronze badges

Lets say, you wanted to have some CGAL-Demos portable. So you’d have a folder «CGAL», and in it, 1 subfolder called «lib»: all (common) support-dlls for any programs in the CGAL-folder go here. In our example, this would be the Dll-Download: simply unzip into the «lib» directory. The further you scroll down on the demos-page, the more impressive the content. In my case, the polyhedron-demo seemed about right. If this runs on my 10+ yo notebook, I’m impressed. So I created a folder «demo» in the «CGAL»-directory, alongside «lib».
Now create a .cmd-file in that folder. I named mine «Polyhedron.cmd». So we have a directory structure like this:

 CGAL - the bag for all the goodies
  lib - all libraries for all CGAL-packages
 demo - all the demos I'm interested in
[...] - certainly some other collections, several apps per folder...
Polyhedron.cmd - and a little script for every Qt-exe to make it truly portable.

In this little example, «Polyhedron.cmd» contains the following text:

@echo off
set "me=%~dp0"
set PATH=%me%lib
set "QT_PLUGIN_PATH=%me%libplugins"
start /b "CGAL Polyhedron Demo" "%me%demopolyhedronpolyhedron_3.exe"

All scripts can be the same apart from the last line, obviously. The only caveat is: the «DOS-Window» stays open for as long as you use the actual program. Close the shell-window, and you kill the *.exe as well. Whereever you copy the «CGAL»-folder, as the weird «%~dp0»-wriggle represents the full path to the *.cmd-file that we started, with trailing «». So «%me%lib» is always the full path to the actual library («CGALlib» in my case). The next 2 lines tell Qt where its «runtime» files are. This will be at least the file «qwindows.dll» for Windows-Qt programs plus any number of *.dlls. If I remember rightly, the Dll-library (at least when I downloaded it) had a little «bug» since it contains the «platforms»-directory with qwindows.dll in it. So when you open the lib directory, you need to create a folder «plugins» next to «platforms», and then move into «plugins». If a Qt-app, any Qt-app, doesn’t find «qwindows.dll», it cannot find «windows». And it expects it in a directory named «platforms» in the «plugins» directory, which it has to get told by the OS its running on…and if the «QT_PLUGIN_PATH» is not exactly pointing to all the helper-dlls you need, some Qt-programs will still run with no probs. And some complain about missing *.dlls you’ve never heard off…

answered Jan 20, 2019 at 4:09

I ran into the same error and solved it with a different method than those mentioned in other posts. Hopefully this will help future readers.

BUILD:

Windows 10 (64bit)
Minicoda (using python 3.9.4) (pkgs are from conda-forge channel)
pyqt 5.12.3

My scenario:

I was building a GUI application for some embedded work. I had two machines that were used for development (same OS and architecture), one had zero internet connection. After packaging up my environment and installing on the offline machine, I ran into the error that you got.

Solution:

locate the qt.conf file in your conda environment.
for me: C:Users»name»miniconda3envs»env_name»qt.conf

Make sure the paths are correct. I needed to update the «name» as this was left over from the old machine.

Hopefully this helps someone.

answered Jun 3, 2021 at 20:34

Jesse T-PJesse T-P

1071 silver badge7 bronze badges

I had the same problem of running a QT5 application in windows 10 ( VS2019).
My error was

..DebugQt5Cored.dll
Module: 5.14.1
File: kernelqguiapplication.cpp
Line: 1249

This application failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.

Solution

Since I was using QT msvc2017, I copied plugins folders from «C:QtQt5.14.15.14.1msvc2017plugins» location to the binary location

it worked.

Then check visual studio output window and identify the dlls loaded from plugin folder and removed unwanted dlls

answered Dec 17, 2020 at 22:54

SamanSaman

711 silver badge3 bronze badges

Setting QT_PLUGIN_PATH env variable to <...>/plugins directory also worked for me.

answered Jan 7, 2021 at 5:57

AndreiAndrei

7408 silver badges9 bronze badges

I got the error when Pycharm was trying to run Matplot. The solution that worked for me was setting the Anaconda3Libraryplugins directory (for example: c:Program filesAnaconda3Libraryplugins) as environment variable «QT_PLUGIN_PATH».
To set that you should go to Control Panel / System / Advanced System Settings / Environment Variables.

answered Sep 9, 2021 at 2:50

StarStar

837 bronze badges

Talking mainly about the Windows platform

Faced the same issue when trying to debug the app build using the vcpkg installed Qt library, while having my app build using cmake. Had trouble for some hours until found the solution. The simplest way is to do the following:

in your build folder, find the folder where the final executable is located.
in that folder, you’ll find some Qt libraries, like Qt6Core.dll.
pay attention to whether or not the library file has the d suffix in its name, i.e. Qt6Cored.dll instead of Qt6Core.dll
in the vcpkg folder, you have 2 options
1. ./installed/x64-windows/Qt6/plugins/platforms
2. ./installed/x64-windows/debug/Qt6/plugins/platforms
if the d suffix was present, copy the content of the ../debug/.. folder (otherwise the other one) into the platforms folder in the same folder, where your executable and the Qt libraries are located (if there’s no such folder, create on your own).

You can somehow automate this process. Leaving that task to you. If I do that on my own, will update the answer.

Edit

If you are using CMakeLists you may want to give this a try. Add the following to your app’s CMakeLists.txt

# assuming your target's name is app

if(WIN32)
    add_custom_command(
        TARGET app POST_BUILD
        COMMAND ${CMAKE_COMMAND} -E copy_directory
            ${Qt6_DIR}/../../$<$<CONFIG:Debug>:debug/>Qt6/plugins/platforms/
            $<TARGET_FILE_DIR:app>/platforms/
    )
endif()

answered Mar 18, 2022 at 11:52

arsdeverarsdever

1,07010 silver badges30 bronze badges

Источник

Yes, i used the search:

Failed to load platform plugin «windows». Available platforms are : Error

Deploying Qt C++ Application from Visual Studio qwindows.dll error

failed to load platform plugin «windows» Available platforms are: windows, minimal

However, when starting from the «release»-Folder, i get the following message:

This application failed to start because it could not find or load the
Qt platform plugin «windows». Available platform plugins are:
minimal, offscreen, windows.

Folder structure looks like this:

release
+ gui.exe
+ icudt51.dll
+ icuin51.dll
+ icuuc51.dll
+ libGLESv2.dll
+ Qt5Core.dll
+ Qt5Gui.dll
+ Qt5Widgets.dll
+ platforms

asked Dec 10, 2013 at 13:16

Okay, as posted here https://stackoverflow.com/a/17271172/1458552 without much attention by other users:

The libEGL.dll was missing! Even though this has not been reported when trying to start the application (all other *.dlls such as Qt5Gui.dll had been reported).

answered Dec 10, 2013 at 13:43

AnonymousAnonymous

4,5778 gold badges47 silver badges61 bronze badges

I created a platforms directory next to my exe location and put qwindows.dll inside, but I still received the «Failed to load platform plugin «windows». Available platforms are: windows» error.

When I copied from C:QtQt5.1.15.1.1mingw48_32pluginsplatforms, everything worked fine.

answered Jun 12, 2014 at 19:30

BrandonBrandon

5514 silver badges2 bronze badges

The release is likely missing a library/plugin or the library is in the wrong directory and or from the wrong directory.

Qt intended answer: Use windeployqt. see last paragraph for explanation

Manual answer:

It seems like a common issue is that the .dll was taken from the wrong compiler bin. Be sure to copy your the qwindows.dll from the same compiler as the one used to release your app.

answered Aug 10, 2017 at 2:10

Setting the QT_QPA_PLATFORM_PLUGIN_PATH environment variable to %QTDIR%pluginsplatforms worked for me.

It was also mentioned here and here.

answered Oct 30, 2016 at 12:38

Jim G.Jim G.

15k22 gold badges104 silver badges164 bronze badges

I ran into this and none of the answers I could find fixed it for me.

My colleauge has Qt (5.6.0) installed on his machine at:
C:QtQt5.6.05.6msvc2015plugins
I have Qt (5.6.2) installed in the same location.

QCoreApplication::addLibraryPath(".");

I added the above line to the main method before the QApplication call like this:

int main( int argc, char *argv[] )
{
    QCoreApplication::addLibraryPath(".");
    QApplication app( argc, argv );
    ...
    return app.exec();
}

answered Mar 13, 2017 at 15:38

JoelJoel

1372 silver badges7 bronze badges

create dir platforms and copy qwindows.dll to it, platforms and app.exe are in the same dir

cd app_dir mkdir platforms xcopy qwindows.dll platformsqwindows.dll

Folder structure
+ app.exe + platformsqwindows.dll

answered Mar 8, 2018 at 9:24

KunMing XieKunMing Xie

1,57316 silver badges15 bronze badges

I found another solution. Create qt.conf in the app folder as such:

[Paths]
Prefix = .

And then copy the plugins folder into the app folder and it works for me.

answered Aug 6, 2017 at 18:56

Peter QuiringPeter Quiring

1,5881 gold badge15 silver badges21 bronze badges

For anyone coming from QT version 5.14.0, it took me 2 days to find this piece statment of bug:

windeployqt does not work for MinGW QTBUG-80763 Will be fixed in
5.14.1

https://wiki.qt.io/Qt_5.14.0_Known_Issues

So be aware. Using windeployqt withMinGW will give the same error stated here.

answered Jan 17, 2020 at 3:41

Yahya TawilYahya Tawil

3873 silver badges10 bronze badges

I’ve found that the problem was solved on my computer if I set the following environment variables:

QT_QPA_PLATFORM_PLUGIN_PATH: %QTDIR%pluginsplatforms

QTDIR: C:Miniconda3pkgsqt-5.6.2-vc14_3Library

But this solution only worked on my PC that had conda and qt installed in those folders.

To solve this and make the executable work on any computer, I’ve had to edit the «.spec» (file first generated by pyinstaller) to include the following line:

datas=[(
‘C:Miniconda3pkgsqt-5.6.2-vc14_3Librarypluginsplatforms*.dll’,
‘platforms’ ),]

This solution is based on the answers of Jim G. and CrippledTable

answered Oct 3, 2017 at 12:34

answered Apr 29, 2019 at 13:23

Most of these answers contain good (correct) info, but in my case, there was still something missing.

QCoreApplication::addLibraryPath(<result of GetModuleHandleExA>);

This worked for me.

answered May 9, 2018 at 13:14

I had the same problem and solved it by applying several things.
The first, if it is a program that you did with Qt.

I hope this solution serves you.

answered Mar 23, 2018 at 17:41

answered Oct 11, 2017 at 9:40

Use this batch file: RunWithQt.bat

@echo off
set QTDIR=C:QtQt5.1.15.1.1msvc2012bin
set QT_QPA_PLATFORM_PLUGIN_PATH=%QTDIR%pluginsplatforms
start %1

to use it, drag your gui.exe file and drop it on the RunWithQt.bat in explorer,
or call RunWithQt gui.exe from the command line

answered Feb 8, 2018 at 15:54

If you have Anaconda installed I recomend you to uninstall it and try installing python package from source, i fixed this problem in this way

answered Mar 27, 2018 at 19:39

@echo off
set QTDIR=E:QT5110vc2017

set INCLUDE=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFCinclude;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726include;C:Program Files (x86)Windows KitsNETFXSDK4.6.1includeum;C:Program Files (x86)Windows Kits10include10.0.14393.0ucrt;C:Program Files (x86)Windows Kits10include10.0.14393.0shared;C:Program Files (x86)Windows Kits10include10.0.14393.0um;C:Program Files (x86)Windows Kits10include10.0.14393.0winrt;C:Program Files (x86)Windows Kits10include10.0.14393.0cppwinrt

set LIB=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;C:Program Files (x86)Windows KitsNETFXSDK4.6.1libumx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0ucrtx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0umx86;

set LIBPATH=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86storereferences;C:Program Files (x86)Windows Kits10UnionMetadata10.0.17134.0;C:ProgramFiles (x86)Windows Kits10References10.0.17134.0;C:WindowsMicrosoft.NETFrameworkv4.0.30319;

Path=%QTDIR%qtbasebin;%PATH%
set VCIDEInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEVC
set VCINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVC
set VCToolsInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.11.25503
set VisualStudioVersion=15.0
set VS100COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 10.0Common7Tools
set VS110COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 11.0Common7Tools
set VS120COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools
set VS150COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7Tools
set VS80COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 8Common7Tools
set VS90COMNTOOLS=c:Program Files (x86)Microsoft Visual Studio 9.0Common7Tools
set VSINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017Enterprise
set VSSDK110Install=C:Program Files (x86)Microsoft Visual Studio 11.0VSSDK
set VSSDK150INSTALL=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVSSDK
set WindowsLibPath=C:Program Files (x86)Windows Kits10UnionMetadata;C:Program Files (x86)Windows Kits10References
set WindowsSdkBinPath=C:Program Files (x86)Windows Kits10bin
set WindowsSdkDir=C:Program Files (x86)Windows Kits10
set WindowsSDKLibVersion=10.0.14393.0
set WindowsSdkVerBinPath=C:Program Files (x86)Windows Kits10bin10.0.14393.0
set WindowsSDKVersion=10.0.14393.0
set WindowsSDK_ExecutablePath_x64=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Toolsx64
set WindowsSDK_ExecutablePath_x86=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Tools

mkdir C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
cd C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
copy /Y ..Releaseapplication.exe .
windeployqt application.exe
pause

answered Nov 23, 2018 at 9:03

MyGeertRoMyGeertRo

1311 silver badge3 bronze badges

 CGAL - the bag for all the goodies
  lib - all libraries for all CGAL-packages
 demo - all the demos I'm interested in
[...] - certainly some other collections, several apps per folder...
Polyhedron.cmd - and a little script for every Qt-exe to make it truly portable.

In this little example, «Polyhedron.cmd» contains the following text:

@echo off
set "me=%~dp0"
set PATH=%me%lib
set "QT_PLUGIN_PATH=%me%libplugins"
start /b "CGAL Polyhedron Demo" "%me%demopolyhedronpolyhedron_3.exe"

answered Jan 20, 2019 at 4:09

I ran into the same error and solved it with a different method than those mentioned in other posts. Hopefully this will help future readers.

BUILD:

Windows 10 (64bit)
Minicoda (using python 3.9.4) (pkgs are from conda-forge channel)
pyqt 5.12.3

My scenario:

Solution:

locate the qt.conf file in your conda environment.
for me: C:Users»name»miniconda3envs»env_name»qt.conf

Make sure the paths are correct. I needed to update the «name» as this was left over from the old machine.

Hopefully this helps someone.

answered Jun 3, 2021 at 20:34

Jesse T-PJesse T-P

1071 silver badge7 bronze badges

I had the same problem of running a QT5 application in windows 10 ( VS2019).
My error was

..DebugQt5Cored.dll
Module: 5.14.1
File: kernelqguiapplication.cpp
Line: 1249

This application failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.

Solution

Since I was using QT msvc2017, I copied plugins folders from «C:QtQt5.14.15.14.1msvc2017plugins» location to the binary location

it worked.

Then check visual studio output window and identify the dlls loaded from plugin folder and removed unwanted dlls

answered Dec 17, 2020 at 22:54

SamanSaman

711 silver badge3 bronze badges

Setting QT_PLUGIN_PATH env variable to <...>/plugins directory also worked for me.

answered Jan 7, 2021 at 5:57

AndreiAndrei

7408 silver badges9 bronze badges

answered Sep 9, 2021 at 2:50

StarStar

837 bronze badges

Talking mainly about the Windows platform

in your build folder, find the folder where the final executable is located.
in that folder, you’ll find some Qt libraries, like Qt6Core.dll.
pay attention to whether or not the library file has the d suffix in its name, i.e. Qt6Cored.dll instead of Qt6Core.dll
in the vcpkg folder, you have 2 options
1. ./installed/x64-windows/Qt6/plugins/platforms
2. ./installed/x64-windows/debug/Qt6/plugins/platforms
if the d suffix was present, copy the content of the ../debug/.. folder (otherwise the other one) into the platforms folder in the same folder, where your executable and the Qt libraries are located (if there’s no such folder, create on your own).

You can somehow automate this process. Leaving that task to you. If I do that on my own, will update the answer.

Edit

If you are using CMakeLists you may want to give this a try. Add the following to your app’s CMakeLists.txt

# assuming your target's name is app

if(WIN32)
    add_custom_command(
        TARGET app POST_BUILD
        COMMAND ${CMAKE_COMMAND} -E copy_directory
            ${Qt6_DIR}/../../$<$<CONFIG:Debug>:debug/>Qt6/plugins/platforms/
            $<TARGET_FILE_DIR:app>/platforms/
    )
endif()

answered Mar 18, 2022 at 11:52

arsdeverarsdever

1,07010 silver badges30 bronze badges

Источник

I have looked through all of the questions that appear to be related on stack overflow, and none of the solutions seem to help me.

I am building a Qt application with this setup:

Windows 7 Professional x64
Visual Studio 2012
Qt 5.2.0 built with configure -developer-build -debug-and-release -opensource -nomake examples -nomake tests -platform win32-msvc2012 -no-opengl
Project uses QtSingleApplication (qt-solutions)
Application is a 32 bit application
qmake run with the following: -makefile -spec win32-msvc2012
.pri uses QMAKE_CXX += /D_USING_V110_SDK71_

I can build and run my program fine on my development machine (noted above); I can also install and run the package from Program Files directory on dev machine.

When I install and run on a Windows Vista machine (multiple machines)

VC++ redist 2012 11.0.61030.0 installed
VC++ redist 2010 10.0.40219 installed
plus 2005, 2008 versions of redist

(also fails on a clean install of Windows 7)

I get:

Application failed to start because it could not find or load the QT platform plugin "windows"

So I followed the instructions and added a .platforms/ directory, and added qwindows.dll (also added qminimal.dll and qoffscreen.dll); I also added libEGL.dll, libGLESv2.dll (even though I shouldn’t need them I don’t think)

Once I added qoffscreen.dll I now get the additional message: Available platform plugins are: offscreen

If I run through Dependency Walker I get this error listed:

GetProcAddress(0x76CA0000 [KERNEL32.DLL], "GetCurrentPackageId") called from "MSVCR110.DLL" at address 0x6AC6FDFA and returned NULL. Error: The specified procedure could not be found (127).

and then further down get the:

GetProcAddress(0x745A0000 [UXTHEME.DLL], "BufferedPaintUnInit") called from "COMCTL32.DLL" at address 0x745FFBF8 and returned 0x745AE18C.
This application failed to start because it could not find or load the Qt platform plugin "windows".

Available platform plugins are: offscreen.

Reinstalling the application may fix this problem.

Any ideas how to fix this dll issue?

Источник

В этой статье мы разберём как установить Qt на Windows 7 и выше, плоть до Windows 10, думаю вам будет полезно и интересно.

Также если вы планируете в будущем перейти на Linux, то для установки Qt на него, прочитайте статью «Как установить Qt 5 на Linux Ubuntu».

Как установить Qt на Windows:

Чтобы вам установить Qt, вам сначала нужно скачать установщик, сделать это можно с официального сайта, переходим на него.

Там сверху вы увидите кнопку с надписью «Download. Try.» нажмите на неё. Вы перейдёте на страницу с разными версиями для скачивания Qt, я выберу Open Source, там надо будет нажать на кнопку «Go open source».

Теперь вы переходите на другую страницу, где вам нужно скролить до самого низа, вы увидите кнопку «Download the Qt Online Installer», нажимаете на неё. Теперь когда вы проскролите немного в низ, увидите кнопку «Download», и у вас наконец начнёт скачиваться установщик.

Когда у вас скачался установщик, можете перейти к установке.

Установка Qt:

Для установки Qt правой кнопкой мыши два раза кликаем по установщику, который скачали выше.

Вам надо будет ввести Email и пароль от учётной записи Qt, поэтому если у вас её нет, надо будет зарегистрироваться, сделать это сможете по ссылке.

Далее нажимаете кнопку «Next», потом со всем соглашаетесь и опять нажимаете «Next», дальше выбираем, отправлять ли данные или нет, тут уже на свой выбор.

Я выбрал не отправлять данные, вам тоже рекомендую так сделать, нажимаем «Next», потом вам предложат выбрать путь до программы и способ установки.

Дальше вам нужно выбрать компоненты для установки, я выбрал для базовой работы, вы можете назначить другие.

Также нажимаете «Next», потом ещё раз со всем соглашаетесь и идёт установка. После того как установка прошла, можете начать работать.

Как возможно вы заметили, я устанавливал на Windows 10, но инструкция подойдёт и начиная с Windows 7.

Вывод:

В этой статье вы узнали как установить Qt на Windows 10, но и также для Windows 7 и 8, думаю вам было интересно и полезно.

Подписываетесь на соц-сети:

Оценка:

Загрузка…

Также рекомендую:

Источник

Вопрос

Проблема: как исправить ошибку «Не удалось запустить приложение из-за того, что не удалось инициализировать подключаемый модуль платформы Qt» в Windows?

Привет. Недавно после обновления Windows мне не удалось заставить OneDrive работать. Каждый раз, когда мой компьютер загружается, я получаю сообщение об ошибке «Не удалось запустить приложение, потому что не удалось инициализировать подключаемый модуль платформы Qt». Есть какие-нибудь советы, как решить эту проблему? Заранее спасибо.

Решенный ответ

Операционная система Windows состоит из множества компонентов — некоторые из них уже предустановлены, а другие необходимо реализовать вручную. Например, Node.js является одним из сторонних компонентов, которые вы можете увидеть практически на любом компьютере с Windows.

Qt основан на C ++^[1] фреймворк, предназначенный для создания приложений на Windows, Android, Linux,^[2] и другие платформы. Хотя это не язык программирования сам по себе, приложения, основанные на нем, должны иметь установленную платформу на своих машинах, чтобы иметь возможность работать. К сожалению, эти зависимости могут создавать определенные проблемы по той или иной причине.

Когда что-то пойдет не так с платформой Qt, пользователи могут получить сообщение об ошибке «Не удалось запустить приложение, потому что не удалось инициализировать подключаемый модуль платформы Qt».

Эта ошибка может затронуть несколько приложений, включая такие игры, как Apex Legends,^[3] автономные компоненты (Dllhost) или часто используемые приложения, такие как OneDrive. Последний находится на каждом компьютере с Windows и является чрезвычайно полезным приложением, обычно используемым для резервного копирования системы / файлов или дополнительного хранилища для пользовательских файлов.

Вот полное сообщение, которое пользователи получают при обнаружении ошибки (текст сообщения об ошибке может отличаться в некоторых случаях):

Это приложение не удалось запустить, потому что не удалось инициализировать подключаемый модуль платформы Qt. Переустановка приложения может решить проблему.

Доступные плагины платформы: минимальные, закадровые, окна.

Хотя может показаться, что включение или установка платформы Qt исправит ошибку «Не удалось запустить приложение, потому что не удалось инициализировать подключаемый модуль платформы Qt», это не так. Однако переустановка приложения, у которого возникают проблемы с обнаружением плагина, может помочь.

Как исправить ошибку «Не удалось запустить приложение, потому что не удалось инициализировать плагин платформы Qt» в Windows?

К сожалению, это не всегда возможно, поскольку пользователи сообщали, что при попытке сделать это они получили ошибку «Не удается найти». Причина этого в том, что более новая версия приложения может уже присутствовать на устройстве, поэтому удаление невозможно. Есть способ обойти это.

В некоторых случаях причины ошибки могут быть не связаны с упомянутыми выше. Например, повреждение системного файла также может вызвать эту ошибку, поэтому мы рекомендуем попробовать запустить сканирование с помощью ReimageСтиральная машина Mac X9 программное обеспечение для ремонта, которое может автоматически устранять основные проблемы Windows. В противном случае используйте следующие методы, которые должны помочь вам навсегда решить эту ошибку.

Способ 1. Скопируйте соответствующую папку в другое место

Исправить это сейчас!Исправить это сейчас!

Для восстановления поврежденной системы необходимо приобрести лицензионную версию Reimage Reimage.

Способ 2. Проверить системные файлы на наличие повреждений

Исправить это сейчас!Исправить это сейчас!

Для восстановления поврежденной системы необходимо приобрести лицензионную версию Reimage Reimage.

Введите cmd в поиске Windows
Щелкните правой кнопкой мыши на Командная строка и выберите Запустить от имени администратора
Здесь введите sfc / scannow и нажмите Входить
Дождитесь завершения сканирования и начать сначала ваша машина
Если SFC вернула ошибка заявив, что не удалось восстановить поврежденные файлы, выполните следующие команды, нажав Входить каждый раз:
DISM / Онлайн / Очистка-Образ / CheckHealth
DISM / Онлайн / Очистка-Изображение / ScanHealth
DISM / Онлайн / Очистка-Образ / RestoreHealth

Способ 3. Попробуйте чистую загрузку

Исправить это сейчас!Исправить это сейчас!

Для восстановления поврежденной системы необходимо приобрести лицензионную версию Reimage Reimage.

Тип msconfig в поиске Windows нажмите Входить
Перейти к Услуги вкладка
Проверить Скрыть все службы Microsoft флажок и выберите Отключить все
Перейти к Запускать вкладка и выберите Открыть диспетчер задач
Здесь щелкните правой кнопкой мыши каждую запись и выберите Запрещать и закройте диспетчер задач
Перейти к Ботинок вкладка, отметьте Безопасная загрузка и выберите Применить + ОК.

После загрузки обратно в Windows попробуйте запустить приложение, с которым у вас возникли проблемы. Если это решит вашу проблему, значит, виновато стороннее приложение. Чтобы исправить ошибку «Не удалось запустить приложение, потому что не удалось инициализировать подключаемый модуль платформы Qt», вам следует удалить все недавно установленные приложения и посмотреть, решит ли это вашу проблему в обычном режиме.

Способ 4. Переустановите указанное приложение

Исправить это сейчас!Исправить это сейчас!

Для восстановления поврежденной системы необходимо приобрести лицензионную версию Reimage Reimage.

Вам следует попробовать удалить приложение, с которым у вас возникли проблемы, а затем установить его заново. Если вы имеете дело с OneDrive, вам следует сделать следующее:

Нажмите Win + R на твоей клавиатуре
в Бегать диалоговое окно, скопируйте и вставьте следующее:
% userprofile% AppData Local Microsoft OneDrive Update OneDriveSetup.exe
Пройдите этапы установки и начать сначала ваш компьютер
Если Windows не может найти указанный файл, вам следует загрузить установочный файл с официального сайта [Прямая ссылка].

Если этот метод не работает и вы получаете сообщение об ошибке, перейдите к приведенному ниже методу, а затем повторите этот шаг.

Метод 5. Удалите проблемное приложение через командную строку

Исправить это сейчас!Исправить это сейчас!

Для восстановления поврежденной системы необходимо приобрести лицензионную версию Reimage Reimage.

Удаление программы, которая не хочет удаляться, может быть трудным, хотя это возможно через PowerShell, так как вы можете запустить ее от имени администратора. Имейте в виду, что приведенный ниже пример относится к приложению OneDrive, и команда будет отличаться в зависимости от имени приложения и его местоположения.

Открытым Командная строка от имени администратора как объяснено выше
Скопируйте и вставьте следующие команды, нажав Входить после каждого:
taskkill / f / im OneDrive.exe
% SystemRoot% SysWOW64 OneDriveSetup.exe / удалить
Примечание: если вы используете 32-битная система Windows вместо этого используйте следующую команду для удаления OneDrive:
% SystemRoot% System32 OneDriveSetup.exe / удалить
Это должно принудительно удалить приложение.

Исправляйте ошибки автоматически

Команда ugetfix.com делает все возможное, чтобы помочь пользователям найти лучшие решения для устранения их ошибок. Если вы не хотите бороться с методами ручного ремонта, используйте автоматическое программное обеспечение. Все рекомендованные продукты были протестированы и одобрены нашими профессионалами. Инструменты, которые можно использовать для исправления ошибки, перечислены ниже:

Предложение

сделай это сейчас!

Скачать Fix
Счастье
Гарантия

сделай это сейчас!

Скачать Fix
Счастье
Гарантия

Совместим с Майкрософт ВиндоусСовместим с OS X По-прежнему возникают проблемы?
Если вам не удалось исправить ошибку с помощью Reimage, обратитесь за помощью в нашу службу поддержки. Сообщите нам все подробности, которые, по вашему мнению, нам следует знать о вашей проблеме.

Reimage — запатентованная специализированная программа восстановления Windows. Он диагностирует ваш поврежденный компьютер. Он просканирует все системные файлы, библиотеки DLL и ключи реестра, которые были повреждены угрозами безопасности.Reimage — запатентованная специализированная программа восстановления Mac OS X. Он диагностирует ваш поврежденный компьютер. Он просканирует все системные файлы и ключи реестра, которые были повреждены угрозами безопасности.
Этот запатентованный процесс восстановления использует базу данных из 25 миллионов компонентов, которые могут заменить любой поврежденный или отсутствующий файл на компьютере пользователя.
Для восстановления поврежденной системы необходимо приобрести лицензионную версию Reimage инструмент для удаления вредоносных программ.

Нажмите

Условия использования Reimage | Политика конфиденциальности Reimage | Политика возврата денег за товар | Нажмите

VPN имеет решающее значение, когда дело доходит до конфиденциальность пользователя. Онлайн-трекеры, такие как файлы cookie, могут использоваться не только платформами социальных сетей и другими веб-сайтами, но также вашим интернет-провайдером и правительством. Даже если вы примените самые безопасные настройки через веб-браузер, вас все равно можно будет отслеживать через приложения, подключенные к Интернету. Кроме того, браузеры, ориентированные на конфиденциальность, такие как Tor, не являются оптимальным выбором из-за пониженной скорости соединения. Лучшее решение для вашей максимальной конфиденциальности — это Частный доступ в Интернет — быть анонимным и безопасным в сети.

Программное обеспечение для восстановления данных — один из вариантов, который может вам помочь восстановить ваши файлы. После удаления файла он не исчезает в воздухе — он остается в вашей системе до тех пор, пока поверх него не записываются новые данные. Восстановление данных Pro это программа для восстановления, которая ищет рабочие копии удаленных файлов на вашем жестком диске. Используя этот инструмент, вы можете предотвратить потерю ценных документов, школьных заданий, личных фотографий и других важных файлов.

Источник

Qt Creator

Qt Creator is a cross-platform, integrated development environment (IDE) for
application developers to create applications for multiple desktop, embedded,
and mobile device platforms.

The Qt Creator Manual is available at:

https://doc.qt.io/qtcreator/index.html

For an overview of the Qt Creator IDE, see:

https://doc.qt.io/qtcreator/creator-overview.html

Supported Platforms

The standalone binary packages support the following platforms:

Windows 10 (64-bit) or later
(K)Ubuntu Linux 20.04 (64-bit) or later
macOS 10.14 or later

Contributing

For instructions on how to set up the Qt Creator repository to contribute
patches back to Qt Creator, please check:

https://wiki.qt.io/Setting_up_Gerrit

See the following page for information about our coding standard:

https://doc.qt.io/qtcreator-extending/coding-style.html

Compiling Qt Creator

Prerequisites:

Qt 6.2 or later. The Qt version that you use to build Qt Creator defines the
minimum platform versions that the result supports
(Windows 10, RHEL/CentOS 8.4, Ubuntu 20.04, macOS 10.14 for Qt 6.2).
Qt WebEngine module for QtWebEngine based help viewer
On Windows:
- MinGW with GCC 9 or Visual Studio 2019 or later
- Python 3.5 or later (optional, needed for the python enabled debug helper)
- Debugging Tools for Windows (optional, for MSVC debugging support with CDB)
On Mac OS X: latest Xcode
On Linux: GCC 9 or later
LLVM/Clang 10 or later (optional, LLVM/Clang 14 is recommended.
See instructions on how to
get LLVM.
The ClangFormat plugin uses the LLVM C++ API.
Since the LLVM C++ API provides no compatibility guarantee,
if later versions don’t compile we don’t support that version.)
CMake
Ninja (recommended)

The used toolchain has to be compatible with the one Qt was compiled with.

Linux and macOS

These instructions assume that Ninja is installed and in the PATH, Qt Creator
sources are located at /path/to/qtcreator_sources, Qt is installed in
/path/to/Qt, and LLVM is installed in /path/to/llvm.

Note that if you install Qt via the online installer, the path to Qt must
include the version number and compiler ABI. The path to the online installer
content is not enough.

Note that /path/to/Qt doesn’t imply the full path depth like:
$USER/Qt/6.2.4/gcc_64/lib/cmake/Qt6, but only $USER/Qt/6.2.4/gcc_64.

See instructions on how to
get LLVM.

mkdir qtcreator_build
cd qtcreator_build

cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja "-DCMAKE_PREFIX_PATH=/path/to/Qt;/path/to/llvm" /path/to/qtcreator_sources
cmake --build .

Windows

These instructions assume that Ninja is installed and in the PATH, Qt Creator
sources are located at pathtoqtcreator_sources, Qt is installed in
pathtoQt, and LLVM is installed in pathtollvm.

Note that if you install Qt via the online installer, the path to Qt must
include the version number and compiler ABI. The path to the online installer
content is not enough.

Note that pathtoQt doesn’t imply the full path depth like:
c:Qt6.2.4msvc2019_64libcmakeQt6, but only c:/Qt/6.2.4/msvc2019_64.
The usage of slashes / is intentional, since CMake has issues with backslashes
in CMAKE_PREFX_PATH, they are interpreted as escape codes.

See instructions on how to
get LLVM.

Decide which compiler to use: MinGW or Microsoft Visual Studio.

MinGW is available via the Qt online installer, for other options see
https://wiki.qt.io/MinGW. Run the commands below in a shell prompt that has
<path_to_mingw>bin in the PATH.

For Microsoft Visual C++ you can use the «Build Tools for Visual Studio». Also
install the «Debugging Tools for Windows» from the Windows SDK installer. We
strongly recommend using the 64-bit version and 64-bit compilers on 64-bit
systems. Open the x64 Native Tools Command Prompt for VS <version> from the
start menu items that were created for Visual Studio, and run the commands
below in it.

md qtcreator_build
cd qtcreator_build

cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja "-DCMAKE_PREFIX_PATH=/path/to/Qt;/path/to/llvm" pathtoqtcreator_sources
cmake --build .

Qt Creator can be registered as a post-mortem debugger. This can be done in the
options page or by running the tool qtcdebugger with administrative privileges
passing the command line options -register/unregister, respectively.
Alternatively, the required registry entries

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebug
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionAeDebug

can be modified using the registry editor regedt32 to contain

qtcreator_buildbinqtcdebugger %ld %ld

When using a self-built version of Qt Creator as post-mortem debugger, it needs
to be able to find all dependent Qt-libraries and plugins when being launched
by the system. The easiest way to do this is to create a self-contained Qt
Creator by installing it and installing its dependencies. See «Options» below
for details.

Note that unlike on Unix, you cannot overwrite executables that are running.
Thus, if you want to work on Qt Creator using Qt Creator, you need a separate
installation of it. We recommend using a separate, release-built version of Qt
Creator to work on a debug-built version of Qt Creator.

Options

If you do not have Ninja installed and in the PATH, remove -G Ninja from
the first cmake call. If you want to build in release mode, change the build
type to -DCMAKE_BUILD_TYPE=Release. You can also build with release
optimizations but debug information with -DCMAKE_BUILD_TYPE=RelWithDebInfo.

You can find more options in the generated CMakeCache.txt file. For instance,
building of Qbs together with Qt Creator can be enabled with -DBUILD_QBS=ON.

Installation is not needed. It is however possible, using

cmake --install . --prefix /path/to/qtcreator_install

To create a self-contained Qt Creator installation, including all dependencies
like Qt and LLVM, additionally run

cmake --install . --prefix /path/to/qtcreator_install --component Dependencies

Perf Profiler Support

Support for the perf profiler
requires the perfparser tool that is part of the Qt Creator source package, and also
part of the Qt Creator Git repository in form of a submodule in src/tools/perfparser.

Compilation of perfparser requires ELF and DWARF development packages.
You can either download and extract a prebuilt package from
https://download.qt.io/development_releases/prebuilt/elfutils/ and add the
directory to the CMAKE_PREFIX_PATH when configuring Qt Creator,
or install the libdw-dev package on Debian-style Linux systems.

You can also point Qt Creator to a separate installation of perfparser by
setting the PERFPROFILER_PARSER_FILEPATH environment variable to the full
path to the executable.

Getting LLVM/Clang for the Clang Code Model

The Clang code model uses Clangd and the ClangFormat plugin depends on the
LLVM/Clang libraries. The currently recommended LLVM/Clang version is 14.0.

Prebuilt LLVM/Clang packages

Prebuilt packages of LLVM/Clang can be downloaded from
https://download.qt.io/development_releases/prebuilt/libclang/

This should be your preferred option because you will use the version that is
shipped together with Qt Creator (with backported/additional patches). In
addition, MinGW packages for Windows are faster due to profile-guided
optimization. If the prebuilt packages do not match your configuration, you
need to build LLVM/Clang manually.

If you use the MSVC compiler to build Qt Creator the suggested way is:
1. Download both MSVC and MinGW packages of libclang.
2. Use the MSVC version of libclang during the Qt Creator build.
3. Prepend PATH variable used for the run time with the location of MinGW version of libclang.dll.
4. Launch Qt Creator.

Building LLVM/Clang manually

You need to install CMake in order to build LLVM/Clang.

Build LLVM/Clang by roughly following the instructions at
http://llvm.org/docs/GettingStarted.html#git-mirror:

Clone LLVM/Clang and checkout a suitable branch

git clone -b release_130-based --recursive https://code.qt.io/clang/llvm-project.git

Build and install LLVM/Clang

For Linux/macOS:

cmake 
  -D CMAKE_BUILD_TYPE=Release 
  -D LLVM_ENABLE_RTTI=ON 
  -D LLVM_ENABLE_PROJECTS="clang;clang-tools-extra" 
  -D CMAKE_INSTALL_PREFIX=<installation location> 
  ../llvm-project/llvm
cmake --build . --target install

For Windows:

cmake ^
  -G Ninja ^
  -D CMAKE_BUILD_TYPE=Release ^
  -D LLVM_ENABLE_RTTI=ON ^
  -D LLVM_ENABLE_PROJECTS="clang;clang-tools-extra" ^
  -D CMAKE_INSTALL_PREFIX=<installation location> ^
  ..llvm-projectllvm
cmake --build . --target install

Clang-Format

The ClangFormat plugin depends on the additional patch

https://code.qt.io/cgit/clang/llvm-project.git/commit/?h=release_130-based&id=42879d1f355fde391ef46b96a659afeb4ad7814a

While the plugin builds without it, it might not be fully functional.

Note that the plugin is disabled by default.

Licenses and Attributions

Qt Creator is available under commercial licenses from The Qt Company,
and under the GNU General Public License version 3,
annotated with The Qt Company GPL Exception 1.0.
See LICENSE.GPL-EXCEPT for the details.

Qt Creator furthermore includes the following third-party components,
we thank the authors who made this possible:

YAML Parser yaml-cpp (MIT License)

https://github.com/jbeder/yaml-cpp

QtCreator/src/libs/3rdparty/yaml-cpp

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

KSyntaxHighlighting

Syntax highlighting engine for Kate syntax definitions

This is a stand-alone implementation of the Kate syntax highlighting
engine. It’s meant as a building block for text editors as well as
for simple highlighted text rendering (e.g. as HTML), supporting both
integration with a custom editor as well as a ready-to-use
QSyntaxHighlighter sub-class.

Distributed under the:

MIT License

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
«Software»), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

The source code of KSyntaxHighlighting can be found here:
https://cgit.kde.org/syntax-highlighting.git
QtCreator/src/libs/3rdparty/syntax-highlighting
https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/libs/3rdparty/syntax-highlighting

Clazy

https://github.com/KDE/clazy

Distributed under GNU LIBRARY GENERAL PUBLIC LICENSE Version 2 (LGPL2).

Integrated with patches from
https://code.qt.io/cgit/clang/clazy.git/.

LLVM/Clang

https://github.com/llvm/llvm-project.git

Distributed under the Apache 2.0 License with LLVM exceptions,
see https://github.com/llvm/llvm-project/blob/main/clang/LICENSE.TXT

With backported/additional patches from https://code.qt.io/cgit/clang/llvm-project.git

std::span implementation for C++11 and later

A single-header implementation of C++20’s std::span, conforming to the C++20
committee draft. It is compatible with C++11, but will use newer language
features if they are available.

https://github.com/tcbrindle/span

QtCreator/src/libs/3rdparty/span

Distributed under the Boost Software License, Version 1.0.
(See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt)

Open Source front-end for C++ (license MIT), enhanced for use in Qt Creator

Roberto Raggi roberto.raggi@gmail.com

QtCreator/src/libs/3rdparty/cplusplus

Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation.

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
KDEVELOP TEAM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Open Source tool for generating C++ code that classifies keywords (license MIT)

Roberto Raggi roberto.raggi@gmail.com

QtCreator/src/tools/3rdparty/cplusplus-keywordgen

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the «Software»), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

SQLite (version 3.8.10.2)

SQLite is a C-language library that implements a small, fast, self-contained,
high-reliability, full-featured, SQL database engine.

SQLite (https://www.sqlite.org) is in the Public Domain.

ClassView and ImageViewer plugins

Contact: http://www.qt.io

This file is part of Qt Creator.

You may use this file under the terms of the BSD license as follows:

«Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
* Neither the name of The Qt Company Ltd and its Subsidiary(-ies) nor
the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
«AS IS» AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.»

Source Code Pro font

Copyright 2010, 2012 Adobe Systems Incorporated (http://www.adobe.com/),
with Reserved Font Name ‘Source’. All Rights Reserved. Source is a
trademark of Adobe Systems Incorporated in the United States
and/or other countries.

This Font Software is licensed under the SIL Open Font License, Version 1.1.

The font and license files can be found in QtCreator/src/libs/3rdparty/fonts.

JSON Library by Niels Lohmann

Used by the Chrome Trace Format Visualizer plugin instead of QJson
because of QJson’s current hard limit of 128 Mb object size and
trace files often being much larger.

The sources can be found in QtCreator/src/libs/3rdparty/json.

The class is licensed under the MIT License:

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the “Software”), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished
to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

litehtml

The litehtml HTML/CSS rendering engine is used as a help viewer backend
to display help files.

The sources can be found in:
* QtCreator/src/plugins/help/qlitehtml
* https://github.com/litehtml

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Neither the name of the nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS «AS IS» AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

gumbo

The litehtml HTML/CSS rendering engine uses the gumbo parser.

Licensed under the Apache License, Version 2.0 (the «License»);
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an «AS IS» BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

gumbo/utf8.c

The litehtml HTML/CSS rendering engine uses gumbo/utf8.c parser.

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

SourceCodePro fonts

Qt Creator ships with the following fonts licensed under OFL-1.1:

SourceCodePro-Regular.ttf
SourceCodePro-It.ttf
SourceCodePro-Bold.ttf

SIL OPEN FONT LICENSE

Version 1.1 — 26 February 2007

PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.

The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.

DEFINITIONS
«Font Software» refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.

«Reserved Font Name» refers to any names specified as such after the
copyright statement(s).

«Original Version» refers to the collection of Font Software components as
distributed by the Copyright Holder(s).

«Modified Version» refers to any derivative made by adding to, deleting,
or substituting — in part or in whole — any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.

«Author» refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:

Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.
Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.
The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.
The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.

TERMINATION
This license becomes null and void if any of the above conditions are
not met.

DISCLAIMER
THE FONT SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.

Qbs

Qt Creator installations deliver Qbs. Its licensing and third party
attributions are listed in Qbs Manual at
https://doc.qt.io/qbs/attributions.html

conan.cmake

CMake script used by Qt Creator’s auto setup of package manager dependencies.

The sources can be found in:
* QtCreator/src/share/3rdparty/package-manager/conan.cmake
* https://github.com/conan-io/cmake-conan

The MIT License (MIT)

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

TartanLlama/expected

Implementation of std::expected compatible with C++11/C++14/C++17.

https://github.com/TartanLlama/expected

To the extent possible under law, the author(s) have dedicated all
copyright and related and neighboring rights to this software to the
public domain worldwide. This software is distributed without any warranty.

http://creativecommons.org/publicdomain/zero/1.0/

Источник

Qt — это кросс-платформенный фреймворк, с помощью которого можно создавать программное обеспечение, которое будет компилироваться в исполняемые файлы для различных операционных систем без изменения или с минимальным изменением кода. Первоначально платформа Qt создавалась для работы с кодом на языке программирования C++, однако вскоре появились наборы расширений для программирования на PHP, Python, Ruby и Java.

Являясь объектно-ориентированной средой программирования рассчитанной на мультиплатформенную разработку, Qt распространяется вместе с классами и библиотеками необходимыми для разработки элементов интерфейса в различных платформах, поддержки работы с сетью и подключения к базам данных, что делает его пригодным «из коробки» для создания большинства прикладных программ. Как и у большинства современных сред разработки и фреймворков, при необходимости функциональность Qt можно значительно расширить с помощью подключаемых плагинов и виджетов.

Фактически после выхода версии 4.5.0, которая получила интегрированный модуль Qt Creator, фреймворк стал представлять собой полноценную мультиплатформенную среду разработки в которой можно полноценно писать код, разрабатывать графические интерфейсы режиме визуального редактора с помощью модуля Qt Designer, разрабатывать кросс-платформенную справку воспользовавшись Qt Assistant и локализировать своё приложение на множество языков с благодаря модулю Qt Linguist.

Как и в случае с большинством свободно распространяемых программ, вы можете скачать исходный код Qt с официального сайта и собственноручно собрать нужные модули с персональными пожеланиями, однако в большинстве случае достаточно скачать Qt в виде автоматизированного установщика и просто выбрать, какие именно компоненты вам необходимы

Большинство модулей фреймворка Qt распространяются по лицензии LGPL v3 и GPL v3 с открытым исходным кодомLGPL v3 и GPL v3 с открытым исходным кодом и его можно скачивать и использовать бесплатно. При этом нужно иметь в виду, что лицензия некоторых модулей требует, чтобы создаваемый вами продукт так же распространялся под лицензией совместимой с GPL. Подробности лицензирования можно уточнить на официальном сайте фреймворка.

Источник