Yes, here's an example. I define common install paths, which are different in
libs subproject (i.e. in root project libs are installed to
"MyApp.app/Contents/Frameworks" and in libs subproject they are simply
installed to "lib/" folder).
Project {
id: root
property string app_target: "bla"
property string install_app_path: qbs.targetOS.contains("osx") ? "" : "bin"
property string install_library_path: ...
...
SubProject {
filePath: "libs/libs.qbs"
Properties {
app_target: root.app_target
install_binary_path: root.install_binary_path
install_library_path: root.install_library_path
install_plugin_path: root.install_plugin_path
install_data_path: root.install_data_path
}
}
}
Btw, is there a way to refer to a surrounding project without explicitly using
it's id (project.app_target doesn't work).
Иван Комиссаров
28.06.2013, в 12:01, Christian Kandeler <[email protected]>
написал(а):
> On 06/27/2013 07:37 PM, Иван Комиссаров wrote:
>> Nice, but SubProject should have something like "overrideProperties"
>> which means that subproject should use variables from parent project.
>> Right now, it seems that only properties that are not present in
>> subproject are inherited from parent project.
>
> Yes, because that seems the right thing to do.
>
>> So i have to manually override those properties.
>
> Exactly. I do not think it is generally expected that properties you
> explicitly set get overridden just because your project is embedded in
> another one that happens to have some property of the same name.
> Can you give an example where your proposed feature would make sense
> *and* save a considerable amount of code compared to the current solution?
>
>
> Christian
>
> _______________________________________________
> QBS mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/qbs
>
_______________________________________________
QBS mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qbs
