File: README

package info (click to toggle)
psi-plus 1.4.1456-2.2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 26,188 kB
  • sloc: cpp: 211,254; ansic: 19,786; javascript: 13,687; xml: 4,056; sh: 1,610; makefile: 437; objc: 407; python: 277; ruby: 171
file content (44 lines) | stat: -rw-r--r-- 1,283 bytes parent folder | download | duplicates (13)
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
Psi Build Scripts
-----------------

First, prepare your environment according to the prereqs in psideps/README.

To create packages for Windows, set QTDIR64 and QTDIR32, and pass VERSION to
make. For example:

  cd admin/build
  QTDIR64=c:/qt/4.8.2-w64 QTDIR32=c:/qt/4.8.2 make VERSION=0.15-mybuild

You must set both Qt paths. The scripts do not support packaging just for one
arch.

For Mac:

  cd admin/build
  QTDIR=/usr/local/Trolltech/Qt-4.8.2 make VERSION=0.15-mybuild

It is also possible to prepare a dev environment using similar scripting:

Configure for Windows 64-bit:

  QTDIR64=c:/qt/4.8.2-w64 admin/build/devconfig.sh x86_64

Configure for Windows 32-bit:

  QTDIR32=c:/qt/4.8.2 admin/build/devconfig.sh i386

Configure for Mac:

  QTDIR=/usr/local/Trolltech/Qt-4.8.2 admin/build/devconfig.sh ""

Executing one of these commands will cause all Psi dependencies to be
downloaded, configure run against these dependencies, and a file named devenv
generated with all necessary environment variables to build. Then you can
proceed as follows:

  . admin/build/devenv
  make (or mingw32-make, if on Windows)

You can then run the Psi executable from within the shell to test it and
everything needed will be found, without having to create a full distribution
directory.