doc: modifying PATH is not needed anymore on Windows, .pth files are not created either

This commit is contained in:
dessant 2017-01-05 04:58:00 +02:00
parent 3decc2fe99
commit 3ec2be1405
1 changed files with 6 additions and 17 deletions

View File

@ -25,9 +25,6 @@ be installed for each Python version that you want to use Kivy.
.. _install-win-dist: .. _install-win-dist:
.. |nowinfound| replace:: issues
.. _nowinfound: https://github.com/kivy/kivy/issues/3957
Installation Installation
------------ ------------
@ -49,10 +46,6 @@ install.
python -m pip install kivy python -m pip install kivy
#. Add deps to ``PATH`` to avoid |nowinfound|_ (run in `python.exe` folder)::
set PATH=%PATH%;%cd%\share\sdl2\bin;%cd%\share\glew\bin
That's it. You should now be able to ``import kivy`` in python or run a basic That's it. You should now be able to ``import kivy`` in python or run a basic
example:: example::
@ -279,10 +272,6 @@ Compile Kivy
python -m pip install kivy\. python -m pip install kivy\.
#. Set correct paths for binaries::
set PATH=%PATH%;%cd%\share\sdl2\bin;%cd%\share\glew\bin
If the compilation succeeds without any error, Kivy should be good to go. You If the compilation succeeds without any error, Kivy should be good to go. You
can test it with running a basic example:: can test it with running a basic example::
@ -314,20 +303,20 @@ favorite location, do the following:
``your-path\kivy\deps`` where ``your-path`` is the path where your kivy is ``your-path\kivy\deps`` where ``your-path`` is the path where your kivy is
located. located.
#. Remove the ``python\Lib\site-packages\kivy`` directory altogether. #. Remove the ``python\Lib\site-packages\kivy`` directory altogether.
#. From ``python\Lib\site-packages`` move **all** the ``kivy.deps.*.pth`` #. From ``python\Lib\site-packages`` move **all** ``kivy.deps.*.dist-info``
files and **all** ``kivy.deps.*.dist-info`` directories to ``your-path`` directories to ``your-path`` right next to ``kivy``.
right next to ``kivy``.
Now you can safely compile kivy in its current location with one of these Now you can safely compile kivy in its current location with one of these
commands:: commands::
> make > make
> mingw32-make > mingw32-make
> python -m pip install -e location > python -m pip install -e .
> python setup.py build_ext --inplace > python setup.py build_ext --inplace
**If kivy fails to be imported,** you probably didn't delete all the *.pth **If kivy fails to be imported,** you probably didn't delete all the
files and and the kivy or kivy.deps* folders from site-packages. ``*.dist-info`` folders and and the kivy or ``kivy.deps*`` folders from
site-packages.
Making Python available anywhere Making Python available anywhere
-------------------------------- --------------------------------