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
|
Visual C++ Version Compatibility
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MySQL++ is fully functional with Visual C++ 2005 and 2008.
MySQL++ also works with VC++ 2003 (a.k.a. VC++ 7.1), with the
exception of the SSQLS feature. There was partial support for
SSQLS with VC++ 2003 in MySQL++ v2, but a feature we added in
MySQL++ v3.0 crashes the VC++ 2003 compiler when you try to use
even simple SSQLS, so we had to remove support for this entirely
for that platform. (See the v3.0 section in the Breakages chapter
of the user manual for details.)
Older versions of Visual C++ are basically hopeless when it
comes to building current versions of MySQL++. They have too
many weaknesses in their Standard C++ implementation to build a
modern library like MySQL++. If you cannot upgrade your compiler,
my advice is that you're best off programming straight to the
MySQL C API rather than try to make MySQL++ build.
Where Are the Project Files, and Why So Many Versions?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are three sets of .sln and .vcproj files shipped with
MySQL++, in the vc2003, vc2005 and vc2008 subdirectories.
Other than the SSQLS issue brought up above, there no functional
difference between these versions. We ship separate project
files for each version of Visual Studio partly to save you from
having to walk through the project conversion wizard, and partly
so you can build the library with multiple versions of Visual C++
without conflicts among the object files.
Prerequisites
~~~~~~~~~~~~~
You need to have the Windows version of the MySQL server installed
on your development system, even if you always access a MySQL
server on a different machine. This is because in addition to
installing the server itself, the official MySQL Windows binaries
also install the client-side development files that MySQL++
needs in order to communicate with a MySQL server.
You have to do a Custom install to enable installation of these
development files. If you get an error about mysql-version.h or
mysql.h when building MySQL++, go back and reinstall the MySQL
server, paying careful attention to the options.
If you've installed the development files and are still getting
header file include errors, read on.
Building the Library and Example Programs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you installed the MySQL server somewhere other than
C:\Program Files\MySQL\MySQL Server 5.0\
you need to change the project file settings. If you're willing to
install Bakefile (see below), you can do this quickly by changing
the variable MYSQL_WIN_DIR at the top of the file mysql++.bkl,
then regenerating the project files by running rebake.bat.
Otherwise, you'll need to change the include and library paths
in all of the project files by hand.
You must build both the Debug and Release versions of the library,
because a release build of your program won't work with a Debug
version of the MySQL++ DLL. Since version 3.0, the VC++ build
of MySQL++ names these two DLLs differently: mysqlpp_d.dll for
the Debug version, and mysqlpp.dll for the Release version.
This lets you keep them in the same PATH directory, without a
concern as to whether the correct one will be used.
With the library built, run at least the resetdb and simple1
examples to ensure that the library is working correctly.
In addition to the other generic examples, there are a few
Visual C++ specific examples that you might want to look at in
examples\vstudio. See README-examples.txt for further details.
Once you're sure the library is working correctly, you can run
the install.hta file at the project root to install the library
files and headers in a directory of your choosing.
(Aside: You may not have come across the .hta extension before.
It's for a rarely-used feature of Microsoft's Internet Explorer,
called HTML Applications. Know what Adobe AIR is? Kinda like
that, only without the compilation into a single binary blob,
the cross-platform compatibility, and the power of Flash and
ActionScript 3. These limitations don't cause a problem here.
In fact, AIR would be vast overkill here. Just open install.hta
in a text editor to see how it works.)
Using MySQL++ in Your Own Projects
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is covered in the user manual, chapter 9.
Working With Bakefile
~~~~~~~~~~~~~~~~~~~~~
MySQL++'s top-level Visual Studio project files aren't
maintained directly. Instead, we use a tool called Bakefile
(http://bakefile.org/) to generate them from mysql++.bkl. Since
there are so many project files in MySQL++, it's often simpler to
edit this source file and "re-bake" the project files from it than
to make your changes in Visual Studio.
To do this, download the native Windows version of Bakefile from the
web site given above. Install it, and then put the installation
directory in your Windows PATH. Then, open up a command window, cd
into the MySQL++ directory, and type "rebake". This will run
rebake.bat, which rebuilds the Visual Studio project files from
mysql++.bkl.
There's more information about using Bakefile in HACKERS.txt.
If You Run Into Problems...
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Especially if you have linking problems, make sure your project
settings match the above. Visual C++ is very picky about things
like run time library settings. When in doubt, try running one
of the example programs. If it works, the problem is likely in
your project settings, not in MySQL++.
|
