On 2014-09-04, at 05:03 PM, Smirnov Vladimir <[email protected]> wrote:
> 1. "product.destination must die". Is it right, that we should replace > it with install dir? How can i setup such behaviour: > having different products in project, which targets in different > folders/drives? Can you please elaborate on this use case and why you might need to do this? > What are plans to create API in qbs to access product targets before > full build (maybe inaccurate)? > 2. About generators API and modules. > Will qbs generate ONLY wrappers? Or it will create native IDE builds too? My Xcode plugin(s) support both just because I felt like it, but the latter is not as useful because it can't use the full power of Qbs and is inherently limited. What use cases do you have in mind? > If first: how can be makefile approach reached? Do we need setup "arch/ > libraries, optimization flags" etc for IDE's (e.g. MSVS)? As for me, it > is extrafluos now-WIP :) > If second is chosen, maybe qmake code could be useful? It already have > object model for output project formats (though its dependency graph not > ideal). > 3. (i wrote that on Gerrit) qbs clean command removes all outputs, when > doing translations, that is undesirable. Maybe we should have some > "unremovable" outputs? It could help to implement lupdate without > "action targets". > _______________________________________________ > QBS mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qbs -- Jake Petroules - jake.petroules at petroules.com Chief Technology Officer - Petroules Corporation _______________________________________________ QBS mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
