[Qt-creator] Why Creator's Qbs plugin need to special process for Qt?

Theo de Vries t.j.a.devries at gmail.com
Thu Aug 30 10:37:00 CEST 2012


2012/8/29 Konstantin Tokarev <annulen at yandex.ru>:
>
> 29.08.2012, 07:55, "Loaden" <loaden at gmail.com>:
>> 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
> Qt-creator at qt-project.org
> 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.



More information about the Qt-creator mailing list