File: raspberry.rst

package info (click to toggle)
python-vispy 0.16.1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 9,112 kB
  • sloc: python: 61,648; javascript: 6,800; ansic: 2,104; makefile: 141; sh: 6
file content (121 lines) | stat: -rw-r--r-- 3,616 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
======================================
Installation on Raspberry Pi 3 Model B
======================================


Distribution
============

For this installation a recent `Rasbian Stretch with Desktop
<https://www.raspberrypi.org/downloads/raspbian/>`_ is used. Download the
image and write it onto a fast micro SDHC (class 10) with enough capacity
(at least 16GB).

You might use other distributions for raspberry, but there have been only tests
with Raspbian so far.


Raspbian/Raspberry setup
========================

1. Perform first time startup (language etc.)
2. start `raspi_config` at console and make sure to select the KMS driver
   (Full or Fake). Best experiences were obtained with Full KMS driver::

    7 Advanced Options
        A1 Expand Filesystem - resize root partition to use all SD space
        A7 GL Driver
            G1 (Full KMS) OpenGL desktop driver with full KMS
3. Reboot


Checking OpenGL capabilities
============================

Now start `glxgears` on a console and check the framerate. You should get
something around 60 FPS.

To retrieve more information about the OpenGL status of the system start
`glxinfo` and `glxheads` on a console and observe the output.

Depending in the MESA version (this is something not reliably explored)
there will be the error message::

    libGL error MESA-LOADER failed to retrieve device information

You can ignore this for now, but if you have any information on the source of
this error and how to resolve, please let vispy-devs know.


Backend requirements
====================

VisPy requires at least one toolkit for opening a window and creates an OpenGL
context. This can be done using one Qt, GLFW, SDL2, Wx, or Pyglet.

.. warning::

   For Raspbian/Raspberry we rely on Qt4 for now!


Package requirements
====================

The only mandatory requirement for VisPy is the `numpy <http://numpy.org>`_
package. This is already distributed with Raspbian. Nevertheless you need to
install some system packages to get VisPy compiled, installed and running:

- `python3-pyqt4` - Python3 bindings for Qt4
- `python3-pyqt4-opengl` - Python3 bindings for Qt's OpenGL module
- `cython3` - C-Extensions for Python3

Please use the Raspbian package manager to retrieve these packages.


Installation options
====================

You have several options to install VisPy. Make sure to use the system ``python3``
at all times. We recommend to use the latest development version.

**To install the latest release version**, you can do:

.. code-block:: console

   $ pip3 install --upgrade vispy

**If you want to run the latest development version**, you can clone the
repository to your local machine and install with ``develop`` to enable easy
updates to latest ``main``:

.. code-block:: console

   $ git clone git://github.com/vispy/vispy.git  # creates "vispy" folder
   $ cd vispy
   $ python3 setup.py develop

To run the latest development version without cloning the repository, you
can also use this line:

.. code-block:: console

   $ pip3 install git+https://github.com/vispy/vispy.git


Testing installation
====================

It is strongly advised to run the vispy test suite right after installation to
check if everything is ok. To do this, just type:

.. code-block:: python

   >>> import vispy
   >>> vispy.test()
   ...

Please note that the test suite may be unstable on some systems. Any potential
instability in the test suite does not necessarily imply instability in the
working state of the provided VisPy examples.

If you have feedback or questions, please use the VisPy :doc:`community` channels.