Marble/MarblePythonInstructions

From KDE TechBase
Revision as of 17:18, 30 December 2013 by Benjaminkaiser (talk | contribs) (Created page with "= Installing Marble's Python Bindings = === General requirements === Marble's Python Bindings only depend on [http://www.riverbankcomputing.com/software/pyqt/intro PyQt] and [...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Installing Marble's Python Bindings

General requirements

Marble's Python Bindings only depend on PyQt and SIP and do not require the kdebindings-python package provided by some distributions (these are only for some other KDE Python bindings).

Getting the Dependencies

  • deb-based distributions (Debian, Ubuntu...):
$ sudo apt-get install python-sip python-qt4
  • OpenSuSE: All the necessary dependencies:
$ sudo zypper install python-sip python-qt4
  • Fedora/RHEL: All the dependencies used for building kdelibs can be installed by running:
$ sudo yum install python-sip python-qt4
  • Arch Linux: All the dependencies used for building kdelibs can be installed by running:
$ sudo pacman -Sy python-sip python-pyqt4

Installing the Marble Python bindings

To install the Marble Python bindings we will need to compile Marble from source. The following commands will download and compile Marble:

$ git clone git://anongit.kde.org/marble.git ~/.marble -b KDE/4.11 $ cd ~/.marble $ mkdir -p build $ cd build $ cmake ../ -DCMAKE_BUILD_TYPE=Release -DEXPERIMENTAL_PYTHON_BINDINGS=TRUE -DQTONLY=FALSE -DCMAKE_INSTALL_PREFIX=/usr/local $ make $ sudo make install

On Arch Linux you will have to add the following options to cmake so it looks like this:

$ cmake ../ -DQT_QMAKE_EXECUTABLE=qmake-qt4 -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DEXPERIMENTAL_PYTHON_BINDINGS=TRUE -DQTONLY=FALSE

For an example of build instructions visit Marble's sources page. Just make sure to add the -DEXPERIMENTAL_PYTHON_BINDINGS=TRUE -DQTONLY=FALSE flags to cmake