2012/8/29 Konstantin Tokarev <[email protected]>:
>
> 29.08.2012, 07:55, "Loaden" <[email protected]>:
>> See:
>> void QbsProject::createBuildProject(const QString &buildProjectName, 
>> QtSupport::BaseQtVersion *qtVersion)
>> {
>>     if (qtVersion) {
>>         if (qtVersion->defaultBuildConfig() == 
>> QtSupport::BaseQtVersion::DebugBuild || qtVersion->defaultBuildConfig() == 
>> QtSupport::BaseQtVersion::BuildAll) {
>>             buildConfiguration["qbs.buildVariant"] = "debug";
>>         } else {
>>             buildConfiguration["qbs.buildVariant"] = "release";
>>         }
>>         buildConfiguration["qt/core.qtPath"] = 
>> qtVersion->sourcePath().toString();
>>
>>     } else {
>>         buildConfiguration["qbs.buildVariant"] = "debug";
>>     }
>>
>> I don't like the design.
>> I thought QbsProjectManager should like CMakeProjectManager.
>> No need Qt depends!
>
> Actually, missing Qt dependence is a big gap in CMakeProjectManager which 
> needs to be fixed.
>
> --
> Regards,
> Konstantin
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/qt-creator

Konstantin, would you mind explaining your point of view? I can see
that Qt dependence is an advantage when building a Qt project, but
when doing a non-Qt development, I agree with Loaden that it is a pain
to have a dependency on qtVersion etc as in the current design of qbs.
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to