Re: [Qbs] ModuleProvider concept

2023-02-16 Thread Heiko Nardmann
Thanks for asking. No, I don't have a package manager there. Just some ZIP files with libraries so far ... On 16.02.23 17:31, Richard Weickelt wrote: On 16.02.2023 11:03, Heiko Nardmann wrote: *Create* the files in my imagined usecase means for me retrieving necessary files from Artifactory

Re: [Qbs] ModuleProvider concept

2023-02-16 Thread Richard Weickelt
On 16.02.2023 11:03, Heiko Nardmann wrote: *Create* the files in my imagined usecase means for me retrieving necessary files from Artifactory - corr. Qbs file and e.g. some static library - and provide them so that the project can resolve the dependencies for the build graph. Maybe you could

Re: [Qbs] ModuleProvider concept

2023-02-16 Thread Heiko Nardmann
*Create* the files in my imagined usecase means for me retrieving necessary files from Artifactory - corr. Qbs file and e.g. some static library - and provide them so that the project can resolve the dependencies for the build graph. And yes, I'll have a deeper look into the Qt module

Re: [Qbs] ModuleProvider concept

2023-02-16 Thread Christian Kandeler via Qbs
On 2/16/23 09:53, Heiko Nardmann wrote: I'm trying to understand the ModuleProvider concept. Is this something I should look for when trying to retrieve parts - "Depends" - of my project from e.g. Artifactory? If your modules cannot be "static", i.e. you need to query some external

[Qbs] ModuleProvider concept

2023-02-16 Thread Heiko Nardmann
Hi, I'm trying to understand the ModuleProvider concept. Is this something I should look for when trying to retrieve parts - "Depends" - of my project from e.g. Artifactory? Already looked at * https://doc.qt.io/qbs/qml-qbslanguageitems-moduleprovider.html *