Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-03-28 Thread Nikolaus Demmel
Hi Stephen, > On 03/25/2016 09:25 AM, Tobias Hunger wrote: >> I am personally rather unsure about how to proceed. I can help make >> this branch production/merge ready, but I do not want to maintain it >> indefinitely after it is merged. It touches to many CMake internals >> for me to be comfortab

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-03-25 Thread Tobias Hunger
Am 24.03.2016 16:13 schrieb "Aleix Pol" : > Hey, > I'll be going to Berlin the weekend of the 14th May (Board meeting, > I'll be busy during the weekend). > > Would it make sense for me to book one day before/after to meet and > hack on this? Hey Aleix, I did already do some work on that front, t

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-03-24 Thread Aleix Pol
Hey, I'll be going to Berlin the weekend of the 14th May (Board meeting, I'll be busy during the weekend). Would it make sense for me to book one day before/after to meet and hack on this? Aleix On Thu, Feb 18, 2016 at 2:20 PM, Aleix Pol wrote: > On Wed, Feb 17, 2016 at 10:59 PM, Stephen Kelly

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-22 Thread Tobias Hunger
Am 22.02.2016 23:14 schrieb "Stephen Kelly" : > If anyone can get me a working java environment and a way to asynchronously > write stdin/stdout on long-running processes, I can write a plugin for > eclipse which would be independent of cevelop afaict. > > Do you know enough java to help get starte

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-22 Thread Stephen Kelly
Alexander Neundorf wrote: > On Monday, February 22, 2016 22:30:42 Stephen Kelly wrote: >> Jean-Michaël Celerier wrote: >> > There is also https://www.cevelop.com/ which is an Eclipse derivative, >> > they may be interested ? >> >> I went all hipster reach-out.io and tweeted at them. :) > > looks

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-22 Thread Alexander Neundorf
On Monday, February 22, 2016 22:30:42 Stephen Kelly wrote: > Jean-Michaël Celerier wrote: > > There is also https://www.cevelop.com/ which is an Eclipse derivative, > > they may be interested ? > > I went all hipster reach-out.io and tweeted at them. :) looks like that's an FP7-project, so I woul

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-22 Thread Stephen Kelly
Jean-Michaël Celerier wrote: > There is also https://www.cevelop.com/ which is an Eclipse derivative, > they may be interested ? I went all hipster reach-out.io and tweeted at them. :) -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.or

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-22 Thread Jean-Michaël Celerier
There is also https://www.cevelop.com/ which is an Eclipse derivative, they may be interested ? Best, Jean-Michaël www.i-score.org On Fri, Feb 19, 2016 at 11:36 AM, Stephen Kelly wrote: > Alexander Neundorf wrote: > > > On Wednesday, February 17, 2016 22:59:36 Stephen Kelly wrote: > >> On 02/1

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-19 Thread Alexander Neundorf
On Friday, February 19, 2016 11:36:35 Stephen Kelly wrote: > Alexander Neundorf wrote: > > On Wednesday, February 17, 2016 22:59:36 Stephen Kelly wrote: > >> On 02/15/2016 07:24 PM, Tobias Hunger wrote: > >> > Hi Dominik, > >> > > >> > Am 15.02.2016 19:01 schrieb "Dominik Haumann" > >> > >> > >

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-19 Thread Stephen Kelly
Alexander Neundorf wrote: > On Wednesday, February 17, 2016 22:59:36 Stephen Kelly wrote: >> On 02/15/2016 07:24 PM, Tobias Hunger wrote: >> > Hi Dominik, >> > >> > Am 15.02.2016 19:01 schrieb "Dominik Haumann" >> > > > >> > >: >> > > 1. Wouldn't it make sense you have a

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-18 Thread Alexander Neundorf
On Wednesday, February 17, 2016 22:59:36 Stephen Kelly wrote: > On 02/15/2016 07:24 PM, Tobias Hunger wrote: > > Hi Dominik, > > > > Am 15.02.2016 19:01 schrieb "Dominik Haumann" > > > >: > > > 1. Wouldn't it make sense you have a developer sprint ASAP for this? > > > >

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-18 Thread Aleix Pol
On Wed, Feb 17, 2016 at 10:59 PM, Stephen Kelly wrote: > On 02/15/2016 07:24 PM, Tobias Hunger wrote: > > Hi Dominik, > > Am 15.02.2016 19:01 schrieb "Dominik Haumann" : >> 1. Wouldn't it make sense you have a developer sprint ASAP for this? > > I'd be in, but I do not have the time to organize on

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-17 Thread Milian Wolff
On Mittwoch, 17. Februar 2016 22:59:36 CET Stephen Kelly wrote: > On 02/15/2016 07:24 PM, Tobias Hunger wrote: > > Hi Dominik, > > > > Am 15.02.2016 19:01 schrieb "Dominik Haumann" > > > >: > > > 1. Wouldn't it make sense you have a developer sprint ASAP for this? > > >

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-17 Thread Stephen Kelly
On 02/15/2016 07:24 PM, Tobias Hunger wrote: > > Hi Dominik, > > Am 15.02.2016 19:01 schrieb "Dominik Haumann" >: > > 1. Wouldn't it make sense you have a developer sprint ASAP for this? > > I'd be in, but I do not have the time to organize one. I could > probably get a ro

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-02-15 Thread Tobias Hunger
Hi Dominik, Am 15.02.2016 19:01 schrieb "Dominik Haumann" : > 1. Wouldn't it make sense you have a developer sprint ASAP for this? I'd be in, but I do not have the time to organize one. I could probably get a room in our office though (in Berlin). > 2. Reading about this deamon approach, rtags c

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-01-14 Thread Stephen Kelly
Brad King wrote: > I think the responses in this thread have indicated there is interest > in working toward the full daemon approach. Perhaps discussion should > now proceed on the daemon protocol design over in the thread Tobias > started on cmake-developers: > > cmake daemon mode protocol >

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-01-13 Thread Brad King
On 01/12/2016 05:36 PM, Milian Wolff wrote: > Also, while above you say there are two orthogonal features (which is > correct), there is an important fact that has not yet been stressed enough: > > The daemon approach of Stephen allows for the implementation of both. And both > of these features ar

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-01-12 Thread Alexander Neundorf
On Tuesday, January 12, 2016 10:05:08 Brad King wrote: > On 01/12/2016 05:15 AM, Tobias Hunger wrote: > > I read Brad's reply as meaning that your cleanup work is a great > > benefit to cmake, but will probably not be available in the > > foreseeable future (if at all). > > Most of Stephen's work

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-01-12 Thread Stephen Kelly
Brad King wrote: >> Alexander goes back to the generator approach we discussed a year ago >> and explicitly says he won't work on that, so nothing will happen >> there. > > The generate-json-description approach remains a valid alternative. > Aleix's work on it got pretty far before Stephen propos

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-01-12 Thread Brad King
On 01/12/2016 05:15 AM, Tobias Hunger wrote: > I read Brad's reply as meaning that your cleanup work is a great > benefit to cmake, but will probably not be available in the > foreseeable future (if at all). Most of Stephen's work completed so far is already in CMake 3.4, and a bit more is in 'mas

Re: [cmake-developers] [Qt-creator] CMake daemon for user tools

2016-01-12 Thread Tobias Hunger
Hello Stephen, thanks again for your work and interest in IDE integration! I read Bard's reply as meaning that your cleanup work is a great benefit to cmake, but will probably not be available in the foreseeable future (if at all). Alexander goes back to the generator approach we discussed a yea