[Qbs] Unexpected behavior of MSVC generator

Иван Комиссаров abbapoh at gmail.com
Sat Feb 16 18:14:04 CET 2019

I can comment. If you want a real generator, you should use cmake=)

Being serious, it is not a recursion, it is a proxy - solution is the proxy for the IDE to call the build tool (which is QBS).
Creating a «proper» solution that invokes compilers directly is a very challenging task… Imagine you have a custom (not the *.cpp -> *.o) rule for generating some files with a bunch of JS code. How are you going to invoke this code? Well, you probably would like to call QBS… But if you’re calling it for *some* cases why not call it in *all* cases and save some time?

What’s the point of implementing a rule for cpp files directly in the solution and not implementing it for other cases? I don’t see any use cases.

> 16 февр. 2019 г., в 16:10, Denis Shienkov <denis.shienkov at gmail.com> написал(а):
> Hi all,
> It was surprised for me, that a generated MSVC solution file has
> a build commands which are calls the QBS to build the generated
> MSVC solution... It is recursion!!! o_O
> WTF? But it has not a sense!
> If I want to build a project using the QBS, then I know that I
> will use the QBS!
> But when I want to generate the MSVC project, then I will expect
> that the QBS will generate the 'native' MSVC solution, which I
> will use in the Visual Studio IDE on a host without of the QBS!
> Any comments?
> BR,
> Denis
> _______________________________________________
> Qbs mailing list
> Qbs at qt-project.org
> https://lists.qt-project.org/listinfo/qbs

More information about the Qbs mailing list