[QBS] FW: Preserving independent module-properties when applying rules

Joerg Bornemann joerg.bornemann at digia.com
Thu Mar 13 14:37:53 CET 2014

On 11-Mar-14 14:55, Johannes.Matokic at microchip.com wrote:

> Unfortunately I don't have any good idea of how this could be done better.
> For the moment I use a combination of two workarounds:
> 1. For external modules I add support for the properties to my preprocessor module
> 2. For internal modules I add a project property that contains a mapping file-name -> property
> Both are not really nice but at least they work and the overhead is acceptable.
> One idea (although I don't think that it's a good one) might be to allow enumeration and programmatic generation of module properties. This way one could use them in situations we haven't thought of yet.
> Enumeration could be done with functions like file.moduleCount(), file.moduleAt(index), file.modulePropertyCount(module), file.modulePropertyAt(module, index) or something similar.

I don't think that I completely understand this approach.
How would your initial use case be solved with those functions?



More information about the Qbs mailing list