Yes I have seen his reply and took the time to check the Qbs repository, but that's not what I'm trying to do. What I'm trying to do is basically what Qt Creator is doing with CMake.
To elaborate further: I don't want to generate a solution/whatever and then open this solution/whatever with my IDE. I just want to use the Qbs command line tool to build, clean and debug a Qbs project, without resorting to (e.g. generate) non-qbs-native files. And it's pretty much doable, but like with CMake before its server mode, it relies on a lot of parsing Qbs command line tool outputs, and this is not very reliable nor future proof, thus the idea of a clear query command in the command line tool :) I hope it's a bit clearer :) 2017-12-15 12:12 GMT+01:00 Christian Kandeler <[email protected]>: > On Fri, 15 Dec 2017 11:41:04 +0100 > Damien Courtois <[email protected]> wrote: > > > ---------- Forwarded message ---------- > > From: Damien Courtois <[email protected]> > > Date: 2017-12-15 11:39 GMT+01:00 > > Subject: Re: [Qbs] qbs run --dry-run not working ? > > To: Christian Kandeler <[email protected]> > > Cc: "[email protected]\" <[email protected]>"@qt-project.org > > > > > > The IDE is VSCode. And since extensions are typescript modules, I can > only > > use the Qbs command line tool. > > > > I understand that the command line tool was not designed for being used > > like this, but I think that if it provided a command to query > informations > > about a project, it would really ease integration into a lot of tools. > Take > > the example of CMake: it's integrated in Qt Creator, and now even in > Visual > > Studio 2017. This integration was possible by parsing the output of > CMake, > > and since the server mode, it became even easier (well, at least now it's > > standardized. I still don't understand why they had to create the whole > > server mode / handshake / whatever mess instead of just outputting things > > directly, but anyways :p) > > > > Is this something you would consider ? And if this is not your priority > > (which I would totally understand) are you accepting contributions ? > > Have you seen Jake's reply about project generators? It may well be that > qbs producing native project files is the better alternative here. I'm not > too knowledgeable about either our generator stuff or about VSCode, so I > suggest you discuss your requirements with him. > If it turns out that that's not the right approach, we can come back to > the command line tool. > > > Christian > _______________________________________________ > Qbs mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qbs >
_______________________________________________ Qbs mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
