Re: [cmake-developers] kwsysProcess threadsafety

2018-01-05 Thread Sebastian Holtermann
> > 2) Use libuv instead I just saw the libuv library in the CMake sources. > libuv for process management is on the list. I think it is waiting for > porting to all of CMake's platforms to actually happen. Does that mean it's only there for some specific scenarios and shouldn't be used in

Re: [cmake-developers] kwsysProcess threadsafety

2018-01-05 Thread Ben Boeckel
On Fri, Jan 05, 2018 at 20:34:53 +0100, Sebastian Holtermann wrote: > 2) Use libuv instead libuv for process management is on the list. I think it is waiting for porting to all of CMake's platforms to actually happen. I'm seeing this PR hung up on process:

Re: [cmake-developers] kwsysProcess threadsafety

2018-01-05 Thread clinton
Cool. I'd like to have parallel automoc and uic. How about this 4th option? Don't use threads. A single thread is able to spawn multiple processes, and wait on multiple processes, and react when 1 or more processes change state. I'm probably not familiar enough with kwsysProcess to know if

Re: [cmake-developers] kwsysProcess threadsafety

2018-01-05 Thread Sebastian Holtermann
On Freitag, 5. Januar 2018 13:00:30 CET clin...@elemtech.com wrote: > Cool. I'd like to have parallel automoc and uic. > > How about this 4th option? > Don't use threads. A single thread is able to spawn multiple processes, and > wait on multiple processes, and react when 1 or more processes

[cmake-developers] kwsysProcess threadsafety

2018-01-05 Thread Sebastian Holtermann
Hello! As you might have noticed I tried to parallelize AUTOMOC/UIC. https://gitlab.kitware.com/cmake/cmake/merge_requests/1632 The issue that's blocking it now is that the kwsysProcess framework isn't thread safe. As a consequence it is not possible for threads to start processes concurrently

Re: [cmake-developers] Optionally disabling static lib dependencies with COMPILE_DEPENDS

2018-01-05 Thread John Wordsworth
I realise I wasn't very clear in my previous explanation. Hopefully this paints a better picture; - We have 40 or so developers spread across Visual Studio 2015 (MSBuild - Windows), Xcode (macOS) and Make/Clang (Linux). 80% use Windows. - We have a core set of libs in use by a number of projects