On 11-Mar-14 14:55, johannes.mato...@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? Cheers, Joerg _______________________________________________ QBS mailing list QBS@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs
