[QBS] Questions about QBS best practices
tobias.hunger at digia.com
Fri Jun 14 12:58:13 CEST 2013
On 14.06.2013 12:38, Smirnov Vladimir wrote:
> What do you mean by properties support?
Being able to set e.g. Qt.declarative.qmlDebugging:true from within creator.
> I've downloaded latest trunks of
> qbs and QtC just an hour ago, compiled them together, but haven't
> noticed any changes.
My change is in the 2.8 branch of QtC. This is essential for Qbs users
and I did not want to make you wait for it:)
You will notice a lineedit labeled "Properties" below the Build Variant.
I e.g. use that to set "cpp.cFlags:-Qunused-arguments
cpp.cxxFlags:-Qunused-arguments". This quietens warnings from clang when
> QtC qbs plugin creates such a profile in qbs.conf:
> it disappearing just as before.
Yeap. Creator will manage the profiles it creates as it sees fit. You
can of course edit those via Tools->Options->Build & Run->(Kit|Qt
Version|Compiler) in Creator.
> Moreover, i couldn't just pass custom buildVariant to qbs! (screen
> attached) or any other parameters... (i can do that for make - oh, i
> understand that it is separate tool, but... its annoing).
The profile is the one set up for the kit you are using. Use a different
kit and you get a different profile. The build variant is either "debug"
or "release" (no other values are allowed there AFAIK) and you can
change those with a dropdown box.
> I shill wondered, what is a correct way (without system ENV settings)
> set dozen of absolute path. For all build variants... qbs config still
> useless with QtC ;)
Yeap, qbs config is not needed when working with QtC, just as it should
be IMHO. Creator has all the information required to build sets up its
profiles as configured.
Tobias Hunger, Senior Software Engineer - Digia, Qt
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
Sitz der Gesellschaft: Berlin. USt-IdNr: DE xxx xxx xxx
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
More information about the Qbs