diff options
author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-02-01 21:53:47 +0100 |
---|---|---|
committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-02-01 22:22:50 +0100 |
commit | d180c5d8d5430f1e826ccf1ee9849a14a091b9b8 (patch) | |
tree | ba2f7442e7771579f4c2bab9dc920aba2e736869 | |
parent | ef02e044df0034e6d3f97a90e43eaa07f7fe20fb (diff) |
Better message for analysis when configuration wasn't complete
Until now, when `./project make' was run after an insuccessful run of
`./project configure', it would just say to run `./project configure'. But
for a first time user, this could be confusing because when the
configuration is done in parallel, the error message can be very high on
the command-line outputs and not seen clearly.
With this commit, the error message is more complete and describes the
problem and what the users should do in which circumstance.
-rwxr-xr-x | project | 17 |
1 files changed, 13 insertions, 4 deletions
@@ -365,13 +365,22 @@ case $operation in if ! [ -f .build/software/configuration-done.txt ]; then cat <<EOF -The project isn't configured for this system, or the configuration wasn't -successful. To configure the project, please use this command: +The project is either (1) not configured on this system, or (2) the +configuration wasn't successful. + +(1) If it hasn't been configured at all, use the command below to configure +it (set a build directory and let it build its necessary software in it). $ ./project configure -[[ TIP: If you have already configured it once, run it with '-e' to use the -previous configuration. Run with '--help' for more info ]] +(2) If it has been configured, but the configuration failed in a step, you +can re-configure it using your previous settings with the command +below. All successful steps will be skipped, allowing a fast completion. + + $ ./project configure -e + +If there was a problem, please let us know by filling this online form: + http://savannah.nongnu.org/support/?func=additem&group=reproduce EOF exit 1 |