77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
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
|
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
|
Another way to look at it is that Connector/C++ is new and therefore perhaps less crufty, while MySQL++ is mature and featureful.
## <a name="gcc"><a name="gcc2"></a></a>Will it build under GCC?
Yes, with GCC version 3.0 and up, except on [MinGW](#mingw), which requires 3.4.5 at minimum.
The last version of MySQL++ that works with GCC 2.95.*x* is 1.7.9. It may be less painful to port the current version back to GCC 2.95 than to live with the limitations and bugs of this older version. The main thing breaking this backwards compatibility are the steps forward we’ve taken for Standard C++ compliance. If you work around or revert these, it should work on GCC 2.95 again.
The last version of MySQL++ that works with GCC 2.95.*x* is 1.7.9. It may be less painful to port the current version back to GCC 2.95 than to live with the limitations and bugs of this old version of MySQL++. The main thing breaking this backwards compatibility are the steps forward we’ve taken for Standard C++ compliance. If you work around or revert these, MySQL++ should work on GCC 2.95 again.
If you’re stuck on anything older than GCC 2.95, we recommend that you use the MySQL C API instead of trying to arm-twist MySQL++ into building under it.
## <a name="vstudio"></a>Will it build on Linux?
Yes; this is MySQL++’s primary platform. See [the `README-Linux.txt` file](/doc/trunk/README-Linux.txt).
## <a name="vstudio"></a>Will it build on the BSDs or other “real” Unices?
Yes. See [the `README-Unix.txt` file](/doc/trunk/README-Unix.txt).
The BSDs behave mostly the same as Linux for the purposes of building MySQL++.
If you're building on Solaris, see [the `README-Solaris.txt` file](/doc/trunk/README-Solaris.txt) for some platform-specific details. We have reports of people building it successfully on versions as old as Solaris 8. It gets the most testing with GCC, but we have heard occasional success reports from people using Sun CC. Beware that in some versions of Solaris, the “mysql” package is MySQL 4.0, which MySQL++ no longer works 100% with out of the box. (See above.) You want the “mysql5” package instead.
## <a name="vstudio"></a>Will it build under Visual C++?
Yes. See [the `README-Visual-C++.txt` file](/doc/trunk/README-Visual-C++.txt).
Yes. See [the `README-Visual-C++.txt` file](/doc/trunk/README-Visual-C%2B%2B.txt).
MySQL++ ships with project files for Visual C++ 2005 and 2008. The latter can be converted using Visual C++ 2010 or later, but may require some manual adjustment. For example, when Visual C++ 2013 converts the VS2008 project files, it changes the debug build output directory from `debug` to `debug\x64` but fails to update the linker settings for the executables.
We’d like to ship newer project files, but the [tool that generates them](http://bakefile.org/) can’t do that yet.
If you're still on an older version of Visual C++ than 2005, we strongly urge you to upgrade. Those old versions are seriously deficient in terms of Standard C++ support, even at the rather modest level required by MySQL++.
|
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
-
-
-
-
-
-
-
-
-
|
## <a name="mingw"></a>Will it build under MinGW?
Yes. See [the `README-MinGW.txt` file](/doc/trunk/README-MinGW.txt).
Occasionally a version of MinGW comes out that breaks MySQL++, but there has always been a usable workaround.
## <a name="solaris"></a>Will it build under Solaris?
Yes. See [the `README-Solaris.txt` file](/doc/trunk/README-Solaris.txt).
We have reports of people building it successfully on versions as old as Solaris 8. It gets the most testing with GCC, but we have heard occasional success reports from people using Sun CC.
Beware that in some versions of Solaris, the “mysql” package is MySQL 4.0, which MySQL++ no longer works 100% with out of the box. (See above.) You want the “mysql5” package instead.
|