<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>*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.</p>
<p>And yes, I'll have a deeper look into the Qt module provider ...</p>
<p>Thanks!</p>
<p><br>
</p>
<p><i>Kind regards,</i></p>
<p> Heiko</p>
<div class="moz-cite-prefix">On 16.02.23 10:37, Christian Kandeler
via Qbs wrote:<br>
</div>
<blockquote type="cite"
cite="mid:a9857191-4e61-adbc-5c2a-ac8920e856a2@qt.io">On 2/16/23
09:53, Heiko Nardmann wrote:
<br>
<blockquote type="cite">
<br>
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?
<br>
<br>
</blockquote>
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.
<br>
<br>
For a real-world example, you might want to look at the Qt module
provider that's shipped with qbs.
<br>
<br>
<br>
Christian
<br>
<br>
</blockquote>
</body>
</html>