> You mean in the project files? You can do that only on Product level, not
> for the entire project:
Yes, it was about the Product, I misspelled.
This is what I did, works as I need
Product {
...
Depends { name: "Qt"; submodules: ["core", "network"]; required: false}
moduleProvide
>> qbs build ... moduleProviders.Qt.qmakeFilePaths:/invalid
> Yes, it works. But is it possible to do such a disconnection from the
> project itself?
You mean in the project files? You can do that only on Product level, not
for the entire project:
Project {
// cannot set global modulePro
ject: [Qbs] How to explicitly prohibit the use of qt-framework in project
Hi !
I need to check the build of the project for the case where qt-framework
is not installed
For this I have created the following construction:
Depends { name: "Qt"; submodules: ["core", "ne
On 10/19/20 8:26 PM, Карелин Павел wrote:
Depends { name: "Qt"; submodules: ["core", "network"]; required: false}
condition: Qt.core.present
Then in QtC I created a profile without qt-framework, and I tried to
build the project. ... and the project was built.
It turned out that QBS found qt-fr
ject: [Qbs] How to explicitly prohibit the use of qt-framework in project
Hi !
I need to check the build of the project for the case where qt-framework
is not installed
For this I have created the following construction:
Depends { name: "Qt"; submodules: ["core", "ne
Hi !
I need to check the build of the project for the case where qt-framework
is not installed
For this I have created the following construction:
Depends { name: "Qt"; submodules: ["core", "network"]; required: false}
condition: Qt.core.present
Then in QtC I created a profile without qt-fram
