Re: [cmake-developers] cmake daemon mode protocol

Hi Stephen, I think what I suggested so far is covered by the first way of interaction covered in http://thread.gmane.org/gmane.comp.lib.qt.creator/11794/focus=15411 . I am just proposing something that is convenient for me to use. On Sat, Jan 16, 2016 at 12:26 PM, Stephen Kelly

Re: [cmake-developers] cmake daemon mode protocol

Hi Stephen, Am 15.01.2016 00:38 schrieb "Stephen Kelly" : > > * Start daemon-mode without any additional parameters > > > > * Daemon responds with " > > { > > "type": "handShake", > > "version": "3.5.x", > > "supportedProtocols": "3.5" > > } > > As you

Re: [cmake-developers] cmake daemon mode protocol

Stephen Kelly wrote: > I recommend focussing on the tasks in my OP: > > http://thread.gmane.org/gmane.comp.lib.qt.creator/11794 To be more clear: The goal I have is to enable debugging, introspection of the buildsystem and the state during execution, code completion etc. Your goal seems to

Re: [cmake-developers] cmake daemon mode protocol

Tobias Hunger wrote: >> For this case, I suggest that if the user tries to 'open the source >> directory', you would use QTemporaryDir to build in a temporary location > and >> run the daemon there. I believe clion does something equivalent to that. >> Is that viable? I suppose you are suggesting

[cmake-developers] [CMake 0015922]: Unable to configure Fortan through minGW with Visual Studio 14

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15922 == Reported By:Alex Ghosh Assigned To:

[cmake-developers] [PATCH] Added FILTER subcommand to list command

In response to issue 0003986, I've implemented a FILTER subcommand to the "list" command that filters a list using a regular expression. This doesn't implement an optional "OUTPUT_VARIABLE" parameter. There was a discussion on the issue as to whether or not the user using a macro would be a