Author: mysqlpp
Date: Sun May 18 13:46:29 2008
New Revision: 2291
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2291&view=rev
Log:
Removed the tutorial section covering buried MySQL++ headers: it's
covered in the configuration chapter now.
Modified:
trunk/doc/userman/tutorial.dbx
Modified: trunk/doc/userman/tutorial.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/tutorial.dbx?rev=2291&r1=2290&r2=2291&view=diff
==============================================================================
--- trunk/doc/userman/tutorial.dbx (original)
+++ trunk/doc/userman/tutorial.dbx Sun May 18 13:46:29 2008
@@ -180,52 +180,6 @@
fields in the row objects by name, instead of index. This is slower,
but obviously clearer. We’re also printing out the entire
table, not just one column.</para>
- </sect2>
-
-
- <sect2 id="headers">
- <title>#including MySQL++ Headers</title>
-
- <para>You’ll notice above that we’re including
- <filename>mysql++.h</filename> in the examples. There are many
- headers in MySQL++, but this brings in all but one of them for you.
- MySQL++ has a pretty cohesive design: it doesn’t have very
- many pieces that are truly independent of the others. So,
- there’s not much advantage in including the few headers you
- think you need individually: you’re likely to also drag in all
- the rest indirectly.</para>
-
- <para>The one header that <filename>mysql++.h</filename>
- doesn’t
- bring in for you is <filename>ssqls.h</filename>, which is only
- useful if you use the optional <xref linkend="ssqlsintro"/>
- feature.</para>
-
- <para>By default on Unixy systems, MySQL++ installs its headers into
- a <filename>mysql++</filename> subdirectory of one of the main
- system include directories, either <filename>/usr/include</filename>
- or <filename>/usr/local/include</filename>. Since it’s typical
- for either or both of these directories to be in your
- program’s include path already, you might be wondering if you
- can include the main MySQL++ header like this:</para>
-
- <programlisting>#include <mysql++/mysql++.h></programlisting>
-
- <para>The answer is, yes you can. You don’t need to do anything
- special to make it work.</para>
-
- <para>Since MySQL is usually installed in much the same way
- (<filename>/usr/include/mysql</filename> is common, for example),
- you might then ask if you can get away without having the MySQL C
- API header directory to your program’s include path. You can,
- but <filename>mysql++.h</filename> requires a little help from your
- program to find the C API headers when you do this:</para>
-
- <programlisting>#define MYSQLPP_MYSQL_HEADERS_BURIED
-#include <mysql++/mysql++.h></programlisting>
-
- <para>This tells it to prefix all includes for C API headers with
- <filename>mysql/</filename>.</para>
</sect2>
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
