0

I have a typical application dev scenario, a library + application, both are qbs projects. In the library project I declared a Boolean property staticBuild default to true as follow:

Project { // the library

    property bool staticBuild: true

    Product {
        type: staticBuild ? "staticlibrary" : "dynamiclibrary"
        name: "Lib"
    }
}

In the application project I use a Depends item to add Lib as a dependency as follow:

Project { // Application

    Product {
        type: "application"
        Depends { name: "Lib" }
        Lib.staticBuild: false // want to link to a dll.
    }
}

but this property referencing does not work, I get error telling me that the property is not declared.

How could I fix this ?.

Houss_gc
  • 727
  • 5
  • 27

1 Answers1

0

First of all, the library does not even have that property; its parent project does. But even if it did, it would not be visible, much less settable, from the outside. Keep in mind that the library exists once, while there could be many dependencies on it. So if you want to make a decision about how the library is built, you need to do that at a higher level, from which both products take their information. This could be a common parent project (typically the top-level one), or a project-specific module that both products pull in. The main point is that the decision is made in a central place.

Christian Kandeler
  • 806
  • 5
  • 5
  • Say if I create a module having just one boolean property and I set the product type (static or shared) according to this property. The library pull this module a set the property, then the app which depend on the lib pull the same module and set the property. Will the app property setting override the lib property setting? – Houss_gc Jul 25 '17 at 12:23
  • No, every product gets its own instantiation of the module. You should only read from it for this purpose. – Christian Kandeler Jul 25 '17 at 16:09