Is Ninja installed with Qt 6?
-
I did what I thought was a full installation of 6.2 beta 3, but when I opened an existing project (CMake-based) with Qt Creator 5 RC1, I got an error complaining that Ninja wasn't installed. Pretty sure it was "CMake was unable to find a build program corresponding to 'Ninja'"
Then I opened it up with Qt Creator 4, and there were no issues reported.
Now when I open it with Qt Creator 5, I no longer get the complaint about Ninja. I'd report this, but I don't know how to repro it. I don't know why it would've gone away, because as far as I can tell I don't have Ninja installed.
After more searching, I finally found reference to Ninja being available as an installation option. It is buried under "Developer and Designer Tools" and deselected by default. If the new default for Qt is to use Ninja, shouldn't it be installed by default?
-
@Stokestack said in Is Ninja installed with Qt 6?:
If the new default for Qt is to use Ninja
It's not.
Your project was configured to use Ninja.
Qt supports:
- CMake + Ninja
- CMake + Make
- qmake + Make
- Qbs + Ninja
- Qbs + Make
-
@JKSH Thanks. Then the question is why didn't I get a complaint when opening it in the earlier Qt Creator, and also not when I opened it again in the current one?
I did find the following here:
"We recommend to use CMake's Ninja generator. This is also configure's default."
Not sure when configure is invoked, however.
-
@Stokestack said in Is Ninja installed with Qt 6?:
I did find the following here:
"We recommend to use CMake's Ninja generator. This is also configure's default."That's talking about building Qt, not building user projects.
Scroll down lower in the article: "Once you have installed Qt, you can use CMake or qmake to build your projects."
Ninja is not a requirement.
Not sure when configure is invoked, however.
configure
is the script that starts the Qt build process.There is no
configure
script for your own projects.why didn't I get a complaint when opening it in the earlier Qt Creator, and also not when I opened it again in the current one?
I don't know.
Update us if you can reproduce the issue -- otherwise, there's not much else we can say or do.