| - |
The installation of anthillpro does not provide a log of everything that is occurring (except for what you will see in the command prompt window). Because of this, it may be necessary to prepare your command prompt window beforehand so you can retrieve any debugging information should the installation go awry.
|
+ |
The installation of uBuild does not provide a log of everything that is occurring (except for what you will see in the command prompt/terminal window). Because of this, it may be necessary to prepare your command prompt/terminal window beforehand so you can retrieve any debugging information should the installation go awry.
|
| - |
<font size=3>'''IT IS BEST PRACTICE NOT to double-click''' </font> the installation script, and instead run it from the command line, as the installation script will exit and history will be lost!
|
+ |
<font size=3>'''IT IS BEST PRACTICE NOT to double-click''' </font> the installation script, and instead run it from the command line, as after the installation script completes it will exit and command history will be lost!
|
| |
There are a few options (depending on OS) to help with debugging. |
|
There are a few options (depending on OS) to help with debugging. |
| |
Any output from a script/prompt can be redirected to a file. This can be achieved by invoking the ">" key while typing a script to execute. For example, the following will redirect to a file: <pre>install.sh > install.out</pre> |
|
Any output from a script/prompt can be redirected to a file. This can be achieved by invoking the ">" key while typing a script to execute. For example, the following will redirect to a file: <pre>install.sh > install.out</pre> |
| - |
<br/>
|
+ |
Unfortunately, this will not capture any input one will type on the command line and should be considered as a '''last resort''' if none of the following work.
|
| |
= Operating System Specific = |
|
= Operating System Specific = |
