|
Boost-Commit : |
From: ghost_at_[hidden]
Date: 2007-12-20 16:18:47
Author: vladimir_prus
Date: 2007-12-20 16:18:47 EST (Thu, 20 Dec 2007)
New Revision: 42217
URL: http://svn.boost.org/trac/boost/changeset/42217
Log:
Explain a couple of gcc limitations with precompiled headers
Text files modified:
trunk/tools/build/v2/doc/src/tasks.xml | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)
Modified: trunk/tools/build/v2/doc/src/tasks.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/tasks.xml (original)
+++ trunk/tools/build/v2/doc/src/tasks.xml 2007-12-20 16:18:47 EST (Thu, 20 Dec 2007)
@@ -575,7 +575,7 @@
and add that precompiled header to the sources of the target whose compilation
you want to speed up:
<programlisting>
-cpp-pch pch : header.hpp ;
+cpp-pch pch : pch.hpp ;
exe main : main.cpp pch ;</programlisting>
You can use the <code>c-pch</code> if you want to use the precompiled
header in C programs.
@@ -602,6 +602,15 @@
it in the source file, even if the same header is included from
the precompiled header. This makes sure that your project will build
even if precompiled headers are not supported.</para></listitem>
+
+ <listitem><para>On the gcc compiler, the name of the header being
+ precompiled must be equal to the name of the <code>cpp-pch</code>
+ target. This is gcc requirement.</para></listitem>
+
+ <listitem><para>Prior to version 4.2, the gcc compiler did not
+ handle anonymous namespaces in precompiled headers, which
+ limit their utility. See the <ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29085">bug
+ report</ulink> for details.</para></listitem>
</itemizedlist>
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk