QBS Module for creating external binary rcc file.

[Arpegius]

QBS is great, but any time I try to use, it lacks of some component.
Like right now, I cannot find any references on this topic.
So I create one Module:
https://gist.github.com/ArpegiusWhooves/9b9d95eb238b995e45fa
I mostly work, except for Scanner. I am not sure about certain topics:

• The print function wont print anything, but if I change it for throw, work as I expected. (qtcreator problem? is there another way to make warring that shows in qtcreator?)
• What is the correct way of return dependencies from Scanner?
• If scanner seams to return correct dependencies, the rule don't know about them, why?
• What is the correct way to add dynamic dependencies to Rule? Is there a way to create auxiliaryInputs from input file?

I want to rebuild RCC file any time its contents file changes. Right now I have no luck.

[sierdzio]

You can ask it on dedicated QBS mailing list, that is where QBS developers are most active.

[Arpegius]

@sierdzio Thx, but I don't like mailing list idea at all.

Well I have to answer the question myself:

• The print function comes from QtScript module. It print directly to stdout and cannot be redirected. Until some one get the great idea fo exporting qbs::Internal::Loggin to scripts, we can only wait, or throw Errors.
• Just array of string.
• Scanner only return dependencies, it don't add files known to Product. Such files Should be added manually (or maybe by Probe), but I have all files in one folder and simply add them (not perfect but works):

Group {
   name: "Binnary Resources"
   files : "data/**"
   fileTags: [] // suppress all tags
}

• AFAIT Defining auxiliaryInputs for such rule is not needed.

[sierdzio]

@Arpegius said:

@sierdzio Thx, but I don't like mailing list idea at all.

Well, that's your decision.

Until some one get the great idea fo exporting qbs::Internal::Loggin to scripts, we can only wait, or throw Errors.

Again, this is something you could propose on the emailing list, or, since you don't like that, you can go directly to Qt bugtracker and fill in a feature request/ bug report. Maybe somebody from QBS team will pick it up.