Author: mysqlpp
Date: Tue Jul 7 16:12:27 2009
New Revision: 2548
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2548&view=rev
Log:
More tweaks to discussion about the pointlessness of trying to find a
subset of headers to include.
Modified:
trunk/doc/userman/incorporating.dbx
Modified: trunk/doc/userman/incorporating.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/incorporating.dbx?rev=2548&r1=2547&r2=2548&view=diff
==============================================================================
--- trunk/doc/userman/incorporating.dbx (original)
+++ trunk/doc/userman/incorporating.dbx Tue Jul 7 16:12:27 2009
@@ -15,12 +15,13 @@
that uses MySQL++. In modules that use <link
linkend="ssqls">SSQLS v1</link>, you also need to include
<filename>ssqls.h</filename>.<footnote><para>MySQL++ has many header
- files, but the only one that isn’t intertwined with the rest
- is <filename>ssqls.h</filename>. <filename>mysql++.h</filename>
- includes all of the others in the correct order. Some disregard
- this advice, thinking they can speed their build times by finding
- a subset of MySQL++ headers to include. This isn’t likely,
- due to MySQL++’s monolithic nature.</para></footnote></para>
+ files, but the only one that isn’t intertwined with the rest is
+ <filename>ssqls.h</filename>. <filename>mysql++.h</filename> brings
+ in all of the others in the correct order. Some have tried to speed
+ their build times by finding a subset of MySQL++ headers to include,
+ but <filename>mysql++.h</filename> already does as much of this as
+ is practical. MySQL++’s monolithic nature rules out finding
+ a true subset of the library headers.</para></footnote></para>
<para>At this point, your project probably still won’t compile,
and it certainly won’t link. The remaining steps are dependent
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
