> The documentation for ctest_configure(), ctest_build(), and ctest_submit()
> isn't completely clear on what happens if one of these steps fails. Let's
> say I have the following dashboard script (this is pseudocode, arguments
> have been deliberately omitted for brevity, this example won't
On Thu, Jun 30, 2016 at 5:10 PM, Ruslan Baratov <ruslan_bara...@yahoo.com>
wrote:
> On 30-Jun-16 23:57, Shawn Waldon wrote:
>
> On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:
>
>> On 30-Jun-16 23:40, Brad King wrote:
>>
>>> On 06/30/2016 04:28 PM, R
On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:
> On 30-Jun-16 23:40, Brad King wrote:
>
>> On 06/30/2016 04:28 PM, Ruslan Baratov wrote:
>>
>>> On 30-Jun-16 23:18, Brad King wrote:
>>>
On 06/30/2016 03:56 PM, Ruslan Baratov wrote:
> What is the public-use way to specify
s decision is necessary to discuss here.
>
> Dear list, does anyone have experience and recommendations?
>
> 15.01.2016, 02:49, "Shawn Waldon" <shawn.wal...@kitware.com>:
> > Hi,
> >
> > Recently I had to build a project on windows whose required build git.
>
9cb6cda92245779f9c3868d6bcc88edb4f02db6b Mon Sep 17 00:00:00 2001
From: Shawn Waldon <shawn.wal...@kitware.com>
Date: Thu, 14 Jan 2016 18:18:41 -0500
Subject: [PATCH] git: add search paths for default git for windows install
---
Modules/FindGit.cmake | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
