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
122
123
124
125
|
See README for further details about Quackle, its licensing, and its
copyright.
Quackle was first ported to Windows by John Fultz, jfultz@wolfram.com, who
is also the original author of this ReadMe.
I maintain the Windows version so that it can be built with either
Visual C++ or the GNU-based MinGW compiler. As of Quackle 0.97,
I use the mingw tools bundled with Qt 4.7.4 to build the release version.
The build ought to work with Visual C++ Express, as well, but I'm not
sure whether Microsoft disables useful optimizations in that version,
so I won't guarantee that you'll get nice and fast optimized binaries.
All build commands are run from Windows' regular command shell. The
tools are:
Free Tools Build:
------------------------------------
MinGW
Qt 4.8
git
cygwin (optional) - if you want to debug, you'll need gdb from cygwin.
Microsoft Tools Build:
------------------------------------
Visual C++
Qt 4.8
git
Installer build:
------------------------------------
Inno Setup 5
Also, you'll need to make sure the following things are set appropriately
in your environment...
* INCLUDE needs to include Qt's include\ directory
* LIB needs to include Qt's lib\ directory
* PATH needs to include MinGW's bin\ directory and Qt's bin/ directory.
* cygwin's bin directory (if present) should be on PATH, and it must
be after MinGW.
Building is very straightforward. The following steps will get you to a
working executable...
* Make sure your PATH includes Qt's 'bin' directory. If you're building
with MinGW, make sure your PATH includes MinGW's 'bin' directory, and
that it's earlier than Qt's 'bin' directory on the PATH (otherwise,
attempts to run it from the build layout may fail with DLL errors).
* In the directories quackle\, quackle\quackleio, and quackle\quacker,
do the following...
qmake
Free tools: Microsoft tools:
mingw32-make <target> nmake <target>
<target> can be debug, release, or empty if you want to build both.
* You can now run quackle\quacker\release\Quackle.exe
* If, when running Visual Studio builds, you get a "fatal error CVT1100",
then it can be fixed as follows:
+ In the Solution Explorer, open up Quackle, then Generated Files
+ Look for any copies of quacker.res
+ Right-click on each one and choose Exclude From Project
* Recent versions of Visual Studio no longer build XP-compatible binaries
by default. To change this in the project file, bring up the
Quackle Properties page, and under the General configuration,
change the "Platform Toolset" to one which indicates Windows XP
compatibility. Do this for the Quackle, quackleio, and libquackle
projects (the minimum projects which are part of a standard Quackle install).
Additional things to know:
--------------------------
* To build the Quackle installer,
+ Copy QtCore4.dll and QtGui4.dll from Qt's bin/ directory into quackle\
+ If you're building with MinGW, copy mingwm10.dll, libstdc++-6.dll, and
libgcc_s_dw2-1.dll from MinGW's bin/ directory into quackle\
+ From the Quackle directory, run the following...
<full path to Inno Setup's ISCC.exe> installer.iss /FQuackleInstaller /O. /Q
+ Find the file QuackleInstaller.exe in the quackle\ directory.
* MinGW doesn't seem to come with a debugger, but the cygwin gdb
seems to work great on MinGW-generated binaries. Watch for
conflicts between MinGW and cygwin if both are on the path at
once, though.
* If you're more comfortable with project files you can run
qmake -tp vc
to generate project files. I've included a 'quackle.sln' which contains
all of the projects including all of the various utilities. If you're
not interested in the additional utilities, you can simply ignore
Visual C++'s warnings about missing project files. Only the quackle,
quackleio, and quacker projects are absolutely necessary, and if you
run qmake -tp vc in the directories mentioned above, you'll have those
project files.
Building Qt libraries
---------------------
You can download the mingw or Visual Studio versions of the prebuilt
Qt libraries.
To build your own libraries, download
qt-win-opensource-src-<ver>.zip
from Trolltech or a mirror. Unpack it someplace. Set your
PATH so that it contains Qt's bin directory. It should also
include MinGW's bin directory if you're building for MinGW, or
the results of having run VSVARS32.BAT (found in Common7\Tools)
if you're building on Visual Studio.
If you have cygwin installed, make sure that you do *not* have
it on your PATH. Then run
configure -debug-and-release
and follow the directions given at the end of the [moderately lengthy]
configure process.
Here's a helpful document on the process:
https://qt-project.org/doc/qt-4.8/install-win.html
|
