Author: wyoung
Date: Fri Jun 21 04:02:35 2013
New Revision: 2744
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2744&view=rev
Log:
Mentioned Connector/C in the userman in several places where we
previously only said "MySQL C API".
Modified:
trunk/doc/userman/configuration.dbx
trunk/doc/userman/incorporating.dbx
trunk/doc/userman/intro.dbx
trunk/doc/userman/tutorial.dbx
Modified: trunk/doc/userman/configuration.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/configuration.dbx?rev=2744&r1=2743&r2=2744&view=diff
==============================================================================
--- trunk/doc/userman/configuration.dbx (original)
+++ trunk/doc/userman/configuration.dbx Fri Jun 21 04:02:35 2013
@@ -12,31 +12,39 @@
<sect2 id="mysql-loc">
<title>The Location of the MySQL Development Files</title>
- <para>MySQL++ is built on top of the MySQL C API. It relies on
- this low-level library for all communication with the database
- server. Consequently, the build process for MySQL++ may fail if
- it can’t find the C API headers and library.</para>
+ <para>MySQL++ is built on top
+ of the MySQL C API. (Now called <ulink
+ url="https://dev.mysql.com/downloads/connector/c/";>Connector/C</ulink>.)
+ MySQL++ relies on this low-level library for all communication
+ with the database server. Consequently, the build process for
+ MySQL++ may fail if it can’t find the C API headers and
+ library.</para>
<para>On platforms that use Autoconf<footnote><para>Linux,
Solaris, the BSDs, Mac OS X command line (as opposed to the
Xcode IDE), Cygwin... Basically, Unix or anything that works
like it.</para></footnote>, the <filename>configure</filename>
script can usually figure out the location of the C API
- development files by itself. It simply tries a bunch of common
- installation locations until it finds one that works. If
- your MySQL server was installed in a nonstandard location,
- you will have to tell the <filename>configure</filename>
+ development files by itself<footnote><para>I don’t say
+ “Connector/C” here because the name change generally
+ hasn’t percolated out to Unixy systems. It’s more
+ commonly used on Windows systems, since the separate Connector/C
+ download lets them avoid installing a MySQL server just to get
+ development headers and libraries.</para></footnote> It simply
+ tries a bunch of common installation locations until it finds one
+ that works. If your MySQL server was installed in a nonstandard
+ location, you will have to tell the <filename>configure</filename>
script where these files are with some combination
of the <computeroutput>--with-mysql</computeroutput>,
<computeroutput>--with-mysql-include</computeroutput>, and
<computeroutput>--with-mysql-lib</computeroutput> flags. See
<filename>README-Unix.txt</filename> for details.</para>
- <para>No other platform allows this sort of auto-discovery,
- so the build files for these platforms simply hard-code the
- default installation location for whatever version of MySQL is
- in GA state at the time that version of MySQL++ was released. For
- example, the Visual C++ project files currently assume MySQL is in
+ <para>No other platform allows this sort of auto-discovery, so
+ the build files for these platforms simply hard-code the default
+ installation location for the current GA version of Connector/C
+ at the time that version of MySQL++ was released. For example,
+ the Visual C++ project files currently assume MySQL is in
<filename>c:\Program Files\MySQL\MySQL Server 5.1</filename>. If
you’re using some other release of MySQL or you installed it
somewhere else, you will have to modify the build files. How you
Modified: trunk/doc/userman/incorporating.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/incorporating.dbx?rev=2744&r1=2743&r2=2744&view=diff
==============================================================================
--- trunk/doc/userman/incorporating.dbx (original)
+++ trunk/doc/userman/incorporating.dbx Fri Jun 21 04:02:35 2013
@@ -204,10 +204,15 @@
and so will require changing.</para>
<para>The trickiest line is the <varname>LDLIBS</varname>
- one. MySQL++ programs need to get built against both the MySQL and
- MySQL++ libraries, because MySQL++ is built on top of the MySQL
- C API library. If you’re building a threaded program,
- use <filename>-lmysqlclient_r</filename> instead. (See <xref
+ one. MySQL++ programs need to get built against both the MySQL
+ and MySQL++ libraries, because MySQL++ is built on top of the
+ MySQL C API library<footnote><para>The MySQL C API library
+ is most commonly called <filename>libmysqlclient</filename>
+ on Unixy systems, though it is also known as <ulink
+
url="https://dev.mysql.com/downloads/connector/c/";>Connector/C</ulink>.</para></footnote>
+ If you’re building a threaded program, use
+ <filename>-lmysqlclient_r</filename> instead of
+ <filename>-lmysqlclient</filename> here. (See <xref
linkend="threads"/> for more details on building thread-aware
programs.)</para>
Modified: trunk/doc/userman/intro.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/intro.dbx?rev=2744&r1=2743&r2=2744&view=diff
==============================================================================
--- trunk/doc/userman/intro.dbx (original)
+++ trunk/doc/userman/intro.dbx Fri Jun 21 04:02:35 2013
@@ -5,9 +5,11 @@
<sect1 id="intro">
<title>Introduction</title>
- <para>MySQL++ is a powerful C++ wrapper for MySQL’s C API. Its
- purpose is to make working with queries as easy as working with STL
- containers.</para>
+ <para>MySQL++ is a powerful C++ wrapper for MySQL’s
+ C API<footnote><para>The MySQL C API is also known as <ulink
+
url="https://dev.mysql.com/downloads/connector/c/";>Connector/C</ulink>.</para></footnote>.
+ Its purpose is to make working with queries as easy as working with
+ STL containers.</para>
<para>The latest version of MySQL++ can be found at <ulink
url="http://tangentsoft.net/mysql++/";>the official web
Modified: trunk/doc/userman/tutorial.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/tutorial.dbx?rev=2744&r1=2743&r2=2744&view=diff
==============================================================================
--- trunk/doc/userman/tutorial.dbx (original)
+++ trunk/doc/userman/tutorial.dbx Fri Jun 21 04:02:35 2013
@@ -65,12 +65,14 @@
<para>All of the program arguments are optional.</para>
- <para>If you don’t give <option>-s</option>, the underlying
- MySQL C API assumes the server is on the local machine. It chooses
+ <para>If you don’t give <option>-s</option>,
+ the underlying MySQL C API (a.k.a. <ulink
+ url="https://dev.mysql.com/downloads/connector/c/";>Connector/C</ulink>)
+ assumes the server is on the local machine. It chooses
one of several different IPC options based on the platform
- configuration. There are many different forms you can give as
- <varname>server_addr</varname> with <option>-s</option> to override
- this default behavior:</para>
+ configuration. There are many different forms you can give
+ as <varname>server_addr</varname> with <option>-s</option> to
+ override this default behavior:</para>
<itemizedlist>
<listitem>
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
