From qbs at mein-briefkasten.net Mon Jun 7 13:07:06 2021 From: qbs at mein-briefkasten.net (qbs at mein-briefkasten.net) Date: Mon, 7 Jun 2021 13:07:06 +0200 Subject: [Qbs] Settings module properties globally in root qbs project?! Message-ID: <59C01A90-1832-43A2-9427-675AAEB88A1F@mein-briefkasten.net> Hello, I’m currently migrating our project to qbs 1.19 and make use of the new codesign module. When doing so especially on iOS I need to switch between different mobile provisions and thus code signing identities depending on the type of build and my project contains of many sub-projects. When setting the right codesign properties in the main app qbs file only I get many resolve errors for missing code sign identities for each lib sub project. I can resolve this issue to set the right properties using the qbs command line, e.g. > qbs resolve config:release profile:qt5_15_3 at ios ... -f app_standalone.qbs --build-directory ~/build/ios-test1 modules.codesign.signingIdentity:”my identity” modules.codesign.provisioningProfilesPath:”path-to-profiles” But then every user has to do configure this on its own, but I would like to setup the default configuration in the root qbs project. Is this somehow possible? Of course I could create a qbs module for this, but then I would need to Depend on it in every lib/exe product qbs file. I would prefer a global solution. Cheers, Maximilian From abbapoh at gmail.com Mon Jun 7 13:24:18 2021 From: abbapoh at gmail.com (=?utf-8?B?0JjQstCw0L0g0JrQvtC80LjRgdGB0LDRgNC+0LI=?=) Date: Mon, 7 Jun 2021 13:24:18 +0200 Subject: [Qbs] Settings module properties globally in root qbs project?! In-Reply-To: <59C01A90-1832-43A2-9427-675AAEB88A1F@mein-briefkasten.net> References: <59C01A90-1832-43A2-9427-675AAEB88A1F@mein-briefkasten.net> Message-ID: <1D2DD9DD-96DD-469C-AACD-47361E8BAF7F@gmail.com> Hello! The module approach you’ve suggested is probably the best way of doing this. Requires some additional work, unfortunately. I’d also suggest adding helper items that inherit base items provided by Qbs, such as CppApplication, DynamicLibrary, etc - in that case, you can use these items as a drop-in replacement and have a single place where you can add new functionality, such as the dependency on the module that sets identities. I have a small project to illustrate the idea - e.g. see https://github.com/ABBAPOH/qbsfish/blob/master/qbs/imports/MyApp.qbs Qbs itself uses the same approach Ivan > 7 июня 2021 г., в 13:07, qbs at mein-briefkasten.net написал(а): > > Hello, > > I’m currently migrating our project to qbs 1.19 and make use of the new codesign module. > > When doing so especially on iOS I need to switch between different mobile provisions and thus code signing identities depending on the type of build and my project contains of many sub-projects. When setting the right codesign properties in the main app qbs file only I get many resolve errors for missing code sign identities for each lib sub project. > > I can resolve this issue to set the right properties using the qbs command line, e.g. > >> qbs resolve config:release profile:qt5_15_3 at ios ... -f app_standalone.qbs --build-directory ~/build/ios-test1 modules.codesign.signingIdentity:”my identity” modules.codesign.provisioningProfilesPath:”path-to-profiles” > > But then every user has to do configure this on its own, but I would like to setup the default configuration in the root qbs project. > > Is this somehow possible? > > Of course I could create a qbs module for this, but then I would need to Depend on it in every lib/exe product qbs file. I would prefer a global solution. > > Cheers, > Maximilian > _______________________________________________ > Qbs mailing list > Qbs at qt-project.org > https://lists.qt-project.org/listinfo/qbs -------------- next part -------------- An HTML attachment was scrubbed... URL: