Great, another tool that assumes a fixed project directory structure. I guess you can get it to work by iterating over all the QML files, taking the parent directory and giving the "highest" one to the --qmldir option.
Christian ________________________________________ From: Denis Shienkov <[email protected]> Sent: Tuesday, October 10, 2017 3:00 PM To: Christian Kandeler Cc: [email protected] Subject: Re: [Qbs] How to get a product's source directory from the artifact from inputsFromDependencies > Why? In particular, why do you care about the product directory, rather than > the one of the actual file? Because the qml directory is in appropriate product's source directory. And I need to specify the --qmldir <path/to/qml/directory/of/source/product> then. 2017-10-10 15:20 GMT+03:00 Christian Kandeler <[email protected]<mailto:[email protected]>>: Hi Denis, > I need to create e.g the 'zip' archive of output binaries of my project, > where my project contains some of application's products. > > I have looked on qbs\src\packages\archive\archive.qbs example, where are > used the windeployqt utility. It is fine, but I need to use the --qmldir > argument for the windeployqt utility (as my products are qml > applications). As I can see, we can get only the install-root paths from > the inputsFromDependencies: ["installable"] property.. but seems, it is > not enough for me, because I need to get by some way the full paths of > source directories of products of input artifacts. Why? In particular, why do you care about the product directory, rather than the one of the actual file? Christian _______________________________________________ Qbs mailing list [email protected]<mailto:[email protected]> http://lists.qt-project.org/mailman/listinfo/qbs _______________________________________________ Qbs mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
