> Yeah, I've already figured it myself, but the main problem is the fact that > now it's impossible to write qbs script which would work with both qbs-1.3 > and qbs-1.4, and moreover, would it break again with qbs-1.5/1.6?
This should hopefully not change again in a major incompatible way but at some point there will be changes to make installation of bundles significantly easier than writing half a dozen complex Groups for every bundle Product. Also, my advice is to simply drop support for Qbs 1.3 in your project. Once QBS-788 is resolved it should make writing project files compatible with multiple versions of Qbs much easier, though. > Awesome example, and I have one related question, is it possible somehow to > get access to binary's bundle properties to install plugins/resources (which > are different products) to the correct place? Yes. See http://doc.qt.io/qbs/bundle-module.html#path-specific-properties <http://doc.qt.io/qbs/bundle-module.html#path-specific-properties> Note that these properties return partial path strings relative to the directory containing the bundle. So for example bundle.frameworksFolderPath might look like "CoolApp.app/Contents/Frameworks". -- Jake Petroules - jake.petroules at petroules.com
_______________________________________________ QBS mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
