> I am trying to implement custom deploy module
> In that module I have created a rule that consumes files tagged “deployable”
> and produces files tagged “deployPackage”
> Also I have a rule for some image pre-processing. It produces artifacts
> tagged “processedImage”
> For workaround I added “processedImage” and “application” tags to deploy rule
> inputs, but it looks like not flexible solution. If user of this module adds
> some other modules that produce different type of content with different
> tags, my deploy rule will skip that content.
> I am trying to find some mechanism to add “deployable” tag to artifacts
> produced by imagePreprocessor and cpp modules. This example fails to add the
> tag to executable:
>
> CppApplication{
> type: “deployPackage”
> files: [ … ]
> Group{
> fileTagsFilter: “application”
> overrideTags: false
> fileTags: “deployable”
> }
> Depends{ name: “deployModule” }
> }
This should work with the upcoming qbs 1.10 release. I assume you are using a
released version such as 1.9.x? If so, you might want to try with the 1.10
branch. If that doesn't work for you either, please file a bug report and
attach a minimal, but complete example to reproduce the problem.
Christian
_______________________________________________
Qbs mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qbs
