417
edits
(→Windows: Rename “Installing” section; add sections about updating and removing the software) |
m (→Windows: Minor formatting fixes) |
||
Line 156: | Line 156: | ||
Note: | Note: | ||
<blockquote>Messages such as | <blockquote>Messages such as: | ||
: <tt>warning: no previously-included files found matching 'docs\README.conditional-config\_static\README.txt'</tt> | : <tt>warning: no previously-included files found matching 'docs\README.conditional-config\_static\README.txt'</tt> | ||
Line 167: | Line 167: | ||
</blockquote> | </blockquote> | ||
After these steps, you should have a working FFGo. You can run it by double-clicking on either ''ffgo.exe'' or ''ffgo-noconsole.exe'' in a directory such as <tt>C:\Python</tt> | After these steps, you should have a working FFGo. You can run it by double-clicking on either ''ffgo.exe'' or ''ffgo-noconsole.exe'' in a directory such as <tt>C:\Python</tt><i>XY</i><tt>\Scripts</tt>, where <tt><i>XY</i></tt> corresponds to the Python version that was used in the <code>pip install FFGo ...</code> command. These two executables do the same, except ''ffgo.exe'' opens a Windows terminal (“console”) containing all FFGo messages, while ''ffgo-noconsole.exe'' doesn't. You can safely use the latter most of the time. Should FFGo refuse to start for some reason, running ''ffgo.exe'' and examining/reporting the printed messages would certainly be helpful. You may want to create shortcuts for these files by right-clicking on the ''.exe'' file of your choice, choosing ''Create Shortcut'' and dragging the newly-created shortcut to the final, desired place (e.g., your desktop). | ||
Another way to run FFGo is to open a Command Prompt and type: | Another way to run FFGo is to open a Command Prompt and type: |
edits