PNaCl documentation: explain how PNaCl can build with a different C++ standard library, and how to …

native_client_sdk/src/doc/devguide/devcycle/building.rst

Index: native_client_sdk/src/doc/devguide/devcycle/building.rst
diff --git a/native_client_sdk/src/doc/devguide/devcycle/building.rst b/native_client_sdk/src/doc/devguide/devcycle/building.rst
index fd0f56561b5eb646b033e9bd57885e738a2c203a..65a8b18b16ca71091f0a4cbe8236751de2c7784e 100644
--- a/native_client_sdk/src/doc/devguide/devcycle/building.rst
+++ b/native_client_sdk/src/doc/devguide/devcycle/building.rst
@@ -68,6 +68,21 @@ The Native Client SDK comes with two C libraries: `newlib
 glibc <dynamic-loading>` for information about these libraries, including
 factors to help you decide which to use.
 
+C++ libraries
+-------------
+
+Native Client can only use GCC's `libstdc++
+<http://gcc.gnu.org/libstdc++>`_, whereas Portable Native Client can use
+either `libstdc++ <http://gcc.gnu.org/libstdc++>`_ (the current default)
+or LLVM's `libc++ <http://libcxx.llvm.org/>`_. The
+``-stdlib=[libstdc++|libc++]`` command line argument can be used to
+choose which standard library to use.
+
+C++11 library support is only complete in libc++ but other non-library
+language features should work regardless of which standard library is
+used. The ``-std=[c++98|c++11]`` command line argument can be used to
+indicate which C++ language standard to use.

[Derek Schuff, 2013/10/02 18:10:15]

we should really indicated that libc++ is basically beta.

[JF, 2013/10/02 18:15:46]

Done.

+
 SDK toolchains
 --------------