QT install, fourth attempt
-
Use the
amd64, what you selected now is a cross-compiler to do 32 to 64bit compilation.amd64is the original name for the 64bit architecture known now as x86_64 because AMD were the first to produce a 64bit version of the x86 architecture. Soamd64andx86_64are synonyms. -
From SGaist I changed the selection to: Microsoft Visual C++ Compiler 15.0 (amd64) for both C and C++ compiler. Now the hover message looks better as it states:
Warning: The ABI of the selected debugger does not match the tool chain ABI.
It no longer has the warning about the compiler not working. As I started to chase down the VS debugger it occurred to me to ask:
The only option I am really aware of is Visual Studio. But I see things about the GNU tool chain. Which tool chain do I really want? Here are some drivers.
I am using G++ at work on a Centos Linux machine. There I am working Qt for interactive display and OpenGL to build a strip chart. Maybe that matters.
At home I have just started an Arduino project. The processor will sense temperatures, pressures, and currents in the compressor and air handler and provide data to an app on my PC. That app will show the status of our HVAC system. And that app is this Qt environment.
Have you a suggestion as to which tool set to select?
-
The debugger follows the same rule as the compiler: it must match the architecture.
As for the arduino, don't you have a specific tool chain for it ?
-
The Arduino does have its own IDE. I have installed that and it seems to be working.
Because of work I am leaning towards the GNU tool chain. I really don't know if there are any downsides to that so ask for opinions. I do have a Linux machine that I might fire up. However, I want to make my HVAC app available to most people and that audience is predominantly Windows.
What ever you, every read, suggests, it will be my decision, meaning only that I won't blame anyone. Still, I suspect there will not be a bad choice, just maybe one better than the other. -
The Arduino does have its own IDE. I have installed that and it seems to be working.
Because of work I am leaning towards the GNU tool chain. I really don't know if there are any downsides to that so ask for opinions. I do have a Linux machine that I might fire up. However, I want to make my HVAC app available to most people and that audience is predominantly Windows.
What ever you, every read, suggests, it will be my decision, meaning only that I won't blame anyone. Still, I suspect there will not be a bad choice, just maybe one better than the other.Hi @BKBK,
On Linux you can use GCC and Clang, and if I remember correctly, both produce binary compatible code, so you can use both with one Qt version.
On Mac, IMHO, only Clang is used for a long time, probably because Apple said so.
For Windows, you can use the MSVC and the MinGW compiler with Qt.
For MSVC, you have to install the MS C++ compiler, the MS CDB console debugger and a suitable Qt MSVC version.
For MinGW, you can all install with the Qt online installer: the GCC compiler, the GDB debugger and the Qt MinGW version.
Both toolchains can create fully working Windows programs, however some external libraries are only supported on one of the two.
In Principle you can develop on one platform and you or someone else can compile on another platform, as long as you don't use System-specific APIs.
I hope that clearifies things a bit.
-
If you want a quick and easy setup to start using Qt then the MinGW version is the way to go. You can install everything in one go: Qt, the compiler and debugger.
-
@SGaist said in QT install, fourth attempt:
MinGW
I am going with MinGW.
I found the MinGW web site and I think I installed it. Not positive, but lets see what happens.
Open QT Creator and get to here
Click Manage Kits to get:
How important is this Auto-detected versus Manual. I cannot tell. But I have MinGW installed and do not want MSVC so try to remove all the MSVC and install the MinGW.
Start with the Auto-detected by clicking on the item to get
Go to Compiler -> C++ and direct it to the MiGW directory.
No, that does not work.
Click on button Manage to the right. To get:
Don’t want all the Microsoft entries, there is a Remove button that is activated when a line is selected, so do a bunch of removes.
As this is being done manually, click on Manual -> C++, that does nothing.
Click on the Add button, not shown in the previous image.
Add -> MinGW -> C++ to get a selection dialog.
Browse to the path to get here
Question: What belongs in the fields: Platform codegen flags, Platform linker flags, and ABI?
To continue, click Apply. It does not acknowledge the button click.
Click OK. The form closes. But debugger was not set.
Click Manage Kits again and select debuggers to get
Note that it reports 32 bit. I have always selected 64. I don’t know how important this is so continue
Back to here: image Sunday 08
After all that work, Qt Creator is still set up for MSVC 2017.
I don’t know what to do different. Please advise. -
@SGaist said in QT install, fourth attempt:
MinGW
I am going with MinGW.
I found the MinGW web site and I think I installed it. Not positive, but lets see what happens.
Open QT Creator and get to here
Click Manage Kits to get:How important is this Auto-detected versus Manual. I cannot tell. But I have MinGW installed and do not want MSVC so try to remove all the MSVC and install the MinGW.
Start with the Auto-detected by clicking on the item to get
Go to Compiler -> C++ and direct it to the MiGW directory.
No, that does not work.
Click on button Manage to the right. To get:
Don’t want all the Microsoft entries, there is a Remove button that is activated when a line is selected, so do a bunch of removes.
As this is being done manually, click on Manual -> C++, that does nothing.
Click on the Add button, not shown in the previous image.
Add -> MinGW -> C++ to get a selection dialog.
Browse to the path to get here
Question: What belongs in the fields: Platform codegen flags, Platform linker flags, and ABI?
To continue, click Apply. It does not acknowledge the button click.
Click OK. The form closes. But debugger was not set.
Click Manage Kits again and select debuggers to get
Note that it reports 32 bit. I have always selected 64. I don’t know how important this is so continue
Back to here: image Sunday 08
After all that work, Qt Creator is still set up for MSVC 2017.
I don’t know what to do different. Please advise.OK @BKBK, you've tried lots of different things recently and now you have numerous overlapping installations. It is best to start from scratch again.
If you follow these steps carefully and thoroughly, you will have a working system:
- In Qt Creator go to the Kits tab and Remove your 2 Manual kits ("Desktop" and "Unnamed"):
- Close Qt Creator.
- Go to the folder where you installed Qt (C:\Qt ?) and run MaintenanceTool.exe. Uninstall everything.
- Uninstall everything in C:\MinGW too.
- Run the Qt installer again. Select these 2 items (no more, no less):
- Qt > Qt 5.12.0 > MinGW 7.3.0 64-bit
- Qt > Tools > MinGW 7.3.0 64 bit
- Run Qt Creator and compile an example.
That's it. You don't need to install or configure anything else.
If it still doesn't work, do not change any settings; doing so will complicate things further. Post screenshots and we'll have a look.
Question: What belongs in the fields: Platform codegen flags, Platform linker flags, and ABI?
Those fields are for cross-compilers. You don't need them if you follow the steps above carefully and thoroughly.
- In Qt Creator go to the Kits tab and Remove your 2 Manual kits ("Desktop" and "Unnamed"):
-
@SGaist said in QT install, fourth attempt:
MinGW
I am going with MinGW.
I found the MinGW web site and I think I installed it. Not positive, but lets see what happens.
Open QT Creator and get to here
Click Manage Kits to get:How important is this Auto-detected versus Manual. I cannot tell. But I have MinGW installed and do not want MSVC so try to remove all the MSVC and install the MinGW.
Start with the Auto-detected by clicking on the item to get
Go to Compiler -> C++ and direct it to the MiGW directory.
No, that does not work.
Click on button Manage to the right. To get:
Don’t want all the Microsoft entries, there is a Remove button that is activated when a line is selected, so do a bunch of removes.
As this is being done manually, click on Manual -> C++, that does nothing.
Click on the Add button, not shown in the previous image.
Add -> MinGW -> C++ to get a selection dialog.
Browse to the path to get here
Question: What belongs in the fields: Platform codegen flags, Platform linker flags, and ABI?
To continue, click Apply. It does not acknowledge the button click.
Click OK. The form closes. But debugger was not set.
Click Manage Kits again and select debuggers to get
Note that it reports 32 bit. I have always selected 64. I don’t know how important this is so continue
Back to here: image Sunday 08
After all that work, Qt Creator is still set up for MSVC 2017.
I don’t know what to do different. Please advise.@BKBK said in QT install, fourth attempt:
I found the MinGW web site and I think I installed it
Please don't!
Simply use Qt Online Installer or Qt Maintenance Tool (if Qt is already installed) and select Qt MinGW AND MinGW. It will install MinGW which is proven to work with Qt you're installing. -
OK @BKBK, you've tried lots of different things recently and now you have numerous overlapping installations. It is best to start from scratch again.
If you follow these steps carefully and thoroughly, you will have a working system:
- In Qt Creator go to the Kits tab and Remove your 2 Manual kits ("Desktop" and "Unnamed"):
- Close Qt Creator.
- Go to the folder where you installed Qt (C:\Qt ?) and run MaintenanceTool.exe. Uninstall everything.
- Uninstall everything in C:\MinGW too.
- Run the Qt installer again. Select these 2 items (no more, no less):
- Qt > Qt 5.12.0 > MinGW 7.3.0 64-bit
- Qt > Tools > MinGW 7.3.0 64 bit
- Run Qt Creator and compile an example.
That's it. You don't need to install or configure anything else.
If it still doesn't work, do not change any settings; doing so will complicate things further. Post screenshots and we'll have a look.
Question: What belongs in the fields: Platform codegen flags, Platform linker flags, and ABI?
Those fields are for cross-compilers. You don't need them if you follow the steps above carefully and thoroughly.
@JKSH Ok then, I can build the example project. I had to add a few more steps to configure the project, but then it built and ran.
@jsulm Too late, I had already done that. Then I followed the instructions from JKSH, deleted everything, installed a fifth time, and now am up and running.
Qt is working now.
Thank you all for your time and patience. - In Qt Creator go to the Kits tab and Remove your 2 Manual kits ("Desktop" and "Unnamed"):
-
@JKSH Ok then, I can build the example project. I had to add a few more steps to configure the project, but then it built and ran.
@jsulm Too late, I had already done that. Then I followed the instructions from JKSH, deleted everything, installed a fifth time, and now am up and running.
Qt is working now.
Thank you all for your time and patience.
