On 8/3/21 8:23 PM, Ross Boylan wrote:
If this is the intended behavior, I suggest the intentions should change.
At a minimum, some clues in a README.Debian would be helpful.
Ross
There are many ways to use Qt Creator. You can use it to make a Hello
World C application. In this case, you only need GCC or clang compiler
installed.
You can use it to make a regular C++ application, then you need a C++
compiler installed.
If you want Qt, you need to install the Qt modules you want to use. Qt
Creator is not there to hand-hold you. In reality, if you installed
upstream version, you would get the entire bundled Qt which Debian
doesn't provide as a single package.
So, you have two choices here,
1. find the -dev modules to install that your program uses and
install them, or
2. download some Qt version from upstream, and compile it with your
parameters and then point Qt Creator at it.
#2 is not that difficult - that's what I've done for a decade.
As a regular user, you would expect a program to work mostly out of the
box. But as a developer, you are expected to receive a little less
hand-holding here.
So, if you run `cmake` or `qmake` and then `make` in a terminal and it
works and Qt Creator still fails (after you define your kits, which
actually should be automatic for system installed libraries), that's a
bug. If the terminal method also fails, it's not a creator bug.
- Adam