Re: [cmake-developers] Debugger for CMake

2017-02-14 Thread Ben Boeckel
On Mon, Feb 13, 2017 at 20:18:02 -0700, Justin Berger wrote: > I agree on the maximizing code reuse, but that doesn't require them to use > the same operational mode -- the two modes do fundamentally different > things; even while sharing most internal components. Is the idea that you > could only

Re: [cmake-developers] Debugger for CMake

2017-02-14 Thread Konstantin Podsvirov
19:54, 14 February 2017 г., Ben Boeckel :On Mon, Feb 13, 2017 at 20:18:02 -0700, Justin Berger wrote: I agree on the maximizing code reuse, but that doesn't require them to use the same operational mode -- the two modes do fundamentally different things; even while sharing

Re: [cmake-developers] #16633: make CTestTestfile.cmake output dir possible to control

2017-02-14 Thread Brad King
On 02/14/2017 10:54 AM, Giel van Schijndel wrote: > I think it may be easier to do this inside CMake by generating the "new" > form of the add_test() command in the produced CTestTestfile.cmake. From > some experiments I've got the impression that that's always executed > with paths relative to

Re: [cmake-developers] #16633: make CTestTestfile.cmake output dir possible to control

2017-02-14 Thread Giel van Schijndel
On Tue, Feb 14, 2017 at 08:23:58 -0500, Brad King wrote: > On 02/13/2017 10:00 AM, Giel van Schijndel wrote: >> I've written it as a reStructuredText document here [2]. >> [2]: >> https://gitlab.kitware.com/muggenhor/cmake/blob/ctest-alt-dir/Help/ctest_alt_dir.rst > > Thanks for the nice

Re: [cmake-developers] #16633: make CTestTestfile.cmake output dir possible to control

2017-02-14 Thread Brad King
On 02/13/2017 10:00 AM, Giel van Schijndel wrote: > I've written it as a reStructuredText document here [2]. > [2]: > https://gitlab.kitware.com/muggenhor/cmake/blob/ctest-alt-dir/Help/ctest_alt_dir.rst Thanks for the nice write-up! >From the doc: > generate a relative path from the

Re: [cmake-developers] Debugger for CMake

2017-02-14 Thread Brad King
On 02/13/2017 10:18 PM, Justin Berger wrote: > I agree on the maximizing code reuse, but that doesn't require them to use > the same operational mode -- the two modes do fundamentally different things Right. We shouldn't necessarily expect the server to start and then decide whether it is a code