If using 'ninja', tell the user to run 'ninja' not 'make' (#4568)
authorAndrew V. Jones <andrew.jones@vector.com>
Fri, 5 Jun 2020 02:18:16 +0000 (03:18 +0100)
committerGitHub <noreply@github.com>
Fri, 5 Jun 2020 02:18:16 +0000 (19:18 -0700)
commit4593ac048f355856232482bdc4964ce90d64169b
tree0dbf5238c54c8e01093eda0b369716d6ecd277fd
parenta2fc412f22552ae0e8f9c36650d1de2d362638dd
If using 'ninja', tell the user to run 'ninja' not 'make' (#4568)

## Issue

If you call CVC4's `configure` script with `--ninja`, then you get a misleading status message:

```
[avj@tempvm CVC4]$ ./configure.sh --ninja --python3 | tail -n 5
Now change to 'build' and type make, followed by make check or make install.

-- Configuring done
-- Generating done
-- Build files have been written to: /home/avj/working/CVC4/build
```

## Solution

This commit simply fixes the status message to tell the user to run the correct command based on the specified generator:

```
[avj@tempvm CVC4]$ ./configure.sh --ninja --python3 | tail -n 5
Now change to 'build' and type 'ninja', followed by 'ninja check' or 'ninja install'.

-- Configuring done
-- Generating done
-- Build files have been written to: /home/avj/working/CVC4/build
```

Signed-off-by: Andrew V. Jones <andrew.jones@vector.com>
CMakeLists.txt