377
edits
FFGo: Difference between revisions
m
→Installing FFGo and its dependencies: Move note about harmless warnings on 'pip install' to a better place (more specific)
(→Installing FFGo and its dependencies: Favor using the Python Launcher for Windows over specifying a full path to pip executable, because said path seems to heavily depend on the Windows version) |
m (→Installing FFGo and its dependencies: Move note about harmless warnings on 'pip install' to a better place (more specific)) |
||
| Line 250: | Line 250: | ||
{{Note|<code>pip install ffgo</code> has the same effect as <code>pip install FFGo</code>.}} | {{Note|<code>pip install ffgo</code> has the same effect as <code>pip install FFGo</code>.}} | ||
<p> | |||
< | Also note that messages such as: | ||
</p> | |||
<blockquote> | |||
<tt>warning: no previously-included files found matching 'docs\README.conditional-config\_static\README.txt'</tt> | |||
</blockquote> | |||
when running the <code>pip install ...</code> command are completely normal and harmless, just ignore them. This command should print something like: | <p> | ||
when running the <code>pip install ...</code> command are completely normal and harmless, just ignore them. This command should print something like: | |||
</p> | |||
<blockquote> | |||
<tt>Successfully installed CondConfigParser FFGo Pillow geographiclib</tt> | |||
</blockquote> | |||
towards the end if all went well. | <p> | ||
</ | towards the end if all went well. | ||
</p> | |||
</li> | |||
</ol> | |||
After these steps, you should have a working FFGo. You can run it by double-clicking on either <tt>ffgo.exe</tt> or <tt>ffgo-noconsole.exe</tt> 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 <tt>ffgo.exe</tt> opens a Windows terminal (“console”) containing all FFGo messages, while <tt>ffgo-noconsole.exe</tt> doesn't. You can safely use the latter most of the time. Should FFGo refuse to start for some reason, running <tt>ffgo.exe</tt> and examining/reporting the printed messages would certainly be helpful. You may want to create shortcuts for these files by right-clicking on the <tt>.exe</tt> file of your choice, choosing <i>Create Shortcut</i> and dragging the newly-created shortcut to the final, desired place (e.g., your desktop). | After these steps, you should have a working FFGo. You can run it by double-clicking on either <tt>ffgo.exe</tt> or <tt>ffgo-noconsole.exe</tt> 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 <tt>ffgo.exe</tt> opens a Windows terminal (“console”) containing all FFGo messages, while <tt>ffgo-noconsole.exe</tt> doesn't. You can safely use the latter most of the time. Should FFGo refuse to start for some reason, running <tt>ffgo.exe</tt> and examining/reporting the printed messages would certainly be helpful. You may want to create shortcuts for these files by right-clicking on the <tt>.exe</tt> file of your choice, choosing <i>Create Shortcut</i> and dragging the newly-created shortcut to the final, desired place (e.g., your desktop). | ||