"use all kits"?
-
What
is the point in selecting "all kits " when all I really need is the one with "connectivity" component
because I am using "Bluetooth"
AND
I do not really know I NEED connectivity until the "build" fails ? -
@AnneRanch said in "use all kits"?:
What
is the point in selecting "all kits " when all I really need is the one with "connectivity" component
because I am using "Bluetooth"There would be no point. The option does not mean, "Select one of these that matches my project's requirements." The reason this option exists is as a convenience to developers that need to build their project for several different environments with different Qt versions.
AND
I do not really know I NEED connectivity until the "build" fails ?Sure you do. You know that your code uses, for example, anything from the QtBluetooth namespace. That tells you there and then that you need the bluetooth module in whatever Qt version you build your code with.
If you build your own Qt libraries then you get Qt Bluetooth support if you are on a supported platform, all the prerequisites are in the build environment, and you do not disable the add-on deliberately (e.g. -skip qtconnectivity).
If you use the binary installer then you get the Bluetooth add on by downloading it from the installer or Maintenance Tool. It takes all of 30 seconds to find the add-on containing Bluetooth in the installer.
-
@AnneRanch said in "use all kits"?:
What
is the point in selecting "all kits " when all I really need is the one with "connectivity" component
because I am using "Bluetooth"There would be no point. The option does not mean, "Select one of these that matches my project's requirements." The reason this option exists is as a convenience to developers that need to build their project for several different environments with different Qt versions.
AND
I do not really know I NEED connectivity until the "build" fails ?Sure you do. You know that your code uses, for example, anything from the QtBluetooth namespace. That tells you there and then that you need the bluetooth module in whatever Qt version you build your code with.
If you build your own Qt libraries then you get Qt Bluetooth support if you are on a supported platform, all the prerequisites are in the build environment, and you do not disable the add-on deliberately (e.g. -skip qtconnectivity).
If you use the binary installer then you get the Bluetooth add on by downloading it from the installer or Maintenance Tool. It takes all of 30 seconds to find the add-on containing Bluetooth in the installer.
@ChrisW67 Thanks , I believe my problem is still with confusion with terminology.
I add "modules" to project file , BUT install "components". - in Bluetooth case "connectivity" , which is NOT in
every QT release.QT += core gui bluetooth concurrent quickwidgets
Then in my case of Bluetooth I have to have (Linux) "package "
" development library" I can link with Linux packageAND the project will not compile because it "cannot find " WHAT
package or library ? ( which one ?)The worst part it used to work and I cannot eliminate that I may have an issue with Linux itself.