File: README.TXT

package info (click to toggle)
libqtpas 2.6+2.0.8+dfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 5,860 kB
  • sloc: cpp: 56,595; pascal: 13,727; sh: 44; makefile: 18
file content (79 lines) | stat: -rw-r--r-- 2,156 bytes parent folder | download | duplicates (8)
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
Compile Pascal Qt Interface from source:
========================================
 * Download and unpack the sources 
 * cd into the resulting unpacked directory
 * This directory contains amongs other things a Qt Project File Qt5Pas.pro
 * run qmake -query to inspect your Qt installation
 * qmake (creates Makefile based upon Qt5Pas.pro)
 * make (compiles)
 * make install (obtain super user rights with sudo or su)
 * make clean (cleans directory, do this when switching Qt versions)

Linux Note:
-----------
To use a different Qt then the system wide Qt,
use /PathToOtherQt/bin/qmake and learn about LD_LIBRARY_PATH
(export LD_LIBRARY_PATH=/PathToOtherQt/lib)


Mac OsX Note: 
-------------
qmake may create a xcode project 
instead of a g++ Makefile 
use xcodebuild to compile

to create a g++ Makefile:
QMAKESPEC=macx-g++ qmake

The qmake project is configured to create a 
framework instead of a plain library 

Windows Note:
-------------
Verify the QTDIR,QMAKESPEC environment variables.
e.g. QMAKESPEC=win32-g++ and that make -v
and gcc -v produce the expected result.
Be sure that mingw32 shipped with Qt5 is in PATH,
so bindings are built with correct mingw32 version.
eg. for Qt-5.6.1 you can set all paths in cmd and 
build bindings.

set PATH=C:\Qt5Directory\Tools\mingw492_32\bin;C:\Qt5Directory\5.6\mingw49_32\bin;%PATH%
qmake -query
qmake
mingw32-make



Installation
============
When compiling from source,
you can use make install.

When using the binary packages,
see below. 

If preferred, first strip
the libraries before installation.

Linux Binary Installation
-------------------------
The libraries should be copied
to the distribution specific 
system library directory
e.g. /usr/lib. 
Ensure the symlinks are correct.
The .so.OneDigit link is used when running a program.(google soname)
The .so link is used when linking during development

Windows Binary Installation
---------------------------
The dll can be copied to e.g. 
the Qt bin directory, as this 
directory is already in the 
PATH environment variable.

Mac OsX Binary Installation
---------------------------
The provided package installs
to /Library/Frameworks