82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
-
+
-
+
|
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 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?
## <a name="linux"></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?
## <a name="bsd" id="unix"></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.
|