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
|
INSTALLING V ON WINDOWS PLATFORMS (3.1, 95, NT)
Believe it or not, all the object code generated by the
various compilers available for Windows is incompatible
across compilers! This means it is not practical to
distribute V already compiled for every compiler avaiable.
For one thing, I just can't afford to buy that many compilers.
This incompatibility means two IMPORTANT things.
1) You must compile V with your compiler. I've tried to supply
project or make files required for the major compilers, but
not all are available.
2) You must be very careful about the compilation model you
specify. For Windows 3.1, the best model is usually called
Large. While WIN32 doesn't have the memory model problem,
it does have calling convention problems. You MUST be
careful to compile the V library AND your own applications
using the same memory model or calling conventions. These
options are usually buried somewhere on an options menu.
I can't provide exact information about this. It is your job
to understand your compiler enough to do this.
You also must be sure that the byte alignment is correct.
Various compilers default to different alignments, and
you MUST use word alignment (2 byte) in order for some
of the data structures used to build dialog boxes dynamically
to work correctly. This is a limitation of the Windows API!
I've selected a calling convention for the V project files
I provide. You should check what they are, and be sure they
match. I don't think they are always the default settings.
NOTES ON VARIOUS WINDOWS COMPILERS
----------------------------------
Mingw32 - The Windows 32bit GNU C++ compiler
--------------------------------------------
This is getting close to being my compiler of choice. It is
a completely FREE compiler that produces good code and really
works. The main disadvantage at this point is that the debugger
is not really ready yet. That should change soon.
See the ObjectCentral web page under the Windows and NT category
for a link and more information about Mingw32.
BORLAND C++
-----------
Windows specific files for Borland 5.0 are kept on the directory
BCCIDE. That directory includes .IDE files for Borland C++, .RC,
.DEF, and .ICO files. The project files assume that BCC is on drive C:.
If you have BCC 4.5, or keep BCC on a drive other than C:, then you
will have modify the project files to change the include file search
paths. Note that the BCC 5.0 project files only work for WIN32. I
couldn't get BCC 5.02 to compile the 16 bit version. There is a
project file for BCC 4.5 that builds a 16 bit version.
WATCOM C++
----------
Watcom project files are found in the WATCOM directory. There are
various subdirectories with different WIN32 and Win3.1 project
files.
MICROSOFT C++
-------------
The releases of Microsoft's C++ compilers have gotten so
frequent and so expensive that I just haven't been able to
afford to keep up with them. Fortunately, most versions seem
to be able to use project files from earlier versions.
The distribution includes make/project files for Microsoft
VC++. There are 16 bit versions for MSVC 1.52, and for
MSVC 4.0, which were built using the cheap Standard Edition.
They should be compatible or convertable to the more
expensive later versions.
OTHER COMPILERS
---------------
If you want to compile V with a different compiler, it isn't
too hard. To build the library, you include ALL the files in
the [v\srcwin] directory. Specify [v\includew] in the include
search path. V has been designed to work only with the LARGE
model for Win3.1. It works with whatever calling convention
you need for WIN32 (which is different for every compiler).
|
