-
Notifications
You must be signed in to change notification settings - Fork 12
/
README
92 lines (58 loc) · 2.5 KB
/
README
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
Initial setup
=============
git submodule init
git submodule update
Install build dependencies
==========================
On MeeGo:
sudo ./dependencies.meego.sh
On Ubuntu:
sudo ./dependencies.ubuntu.sh
On Arch Linux:
sudo ./dependencies.arch.sh
On Mac OS X (using Homebrew):
sudo ./dependencies.osx.sh
On Red Hat Linux, CentOS 6 and Fedora:
sudo ./dependencies.fedora.sh
On openSUSE:
sudo ./dependencies.opensuse.sh
Additional dependencies for Mac OS X
====================================
The dependencies script on Mac OS X does not install a C++ toolchain or
the Qt libraries. Instead, you should install Xcode and the Qt SDK
manually:
http://developer.apple.com/tools/xcode/
http://qt.nokia.com/downloads/sdk-mac-os-cpp
Build and install
=================
./build_and_install
By default, this will do a Release build. If you want to do a Debug
build, you have to uncomment the correct line in environment.sh
If you want to build PySide against the Qt SDK, you have to set the
environment variable QT_SDK_HOME - this variable needs to be set before
"environment.sh" is sourced, and before "build_and_install" is run.
To build Qt Mobility bindings (or to rebuild a specific module), pass
the module names you want to build as command line arguments, e.g.:
./build_and_install mobility
Python 3 Support
================
By default scripts build PySide for Python 2. To build Python 3 version
uncomment the following line in "environment.sh":
#export PYSIDE_BUILDSCRIPTS_USE_PYTHON3=yes
This will use "python3" to determine the Python version and will also
take care of passing the right build arguments to Shiboken's CMake.
The buildscripts are configured so that the default installation path
for PySide will be different if PySide is compiled for Python 3. This
has the advantage that you can have PySide for Python 2 and 3 installed
without any conflicts.
Please note that some parts of PySide (notably pyside-tools and PySide
Mobility) are not yet able to handle Python 3 from the CMake scripts, so
they will still get built against Python 2 (PySide bugs 1148 and 1149).
Updating to the latest version
==============================
git submodule foreach git checkout master
git submodule foreach git pull
Working with the build
======================
source /path/to/environment.sh
python /path/to/app.py