[Qbs] ModuleProvider concept

[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 provider ...

Thanks!


/Kind regards,/

   Heiko

On 16.02.23 10:37, Christian Kandeler via Qbs wrote:
> 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 resource to *create* the files (rather than just fill in 
> property values), then that would fit the use case.
>
> For a real-world example, you might want to look at the Qt module 
> provider that's shipped with qbs.
>
>
> Christian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qbs/attachments/20230216/29b4443b/attachment.htm>