Index: native_client_sdk/doc_generated/devguide/devcycle/building.html |
diff --git a/native_client_sdk/doc_generated/devguide/devcycle/building.html b/native_client_sdk/doc_generated/devguide/devcycle/building.html |
index 12f540fe0e5dced2c49695c793674bfcc26fbd82..0868816c9afa5caaf96297a2f544b39857683ab7 100644 |
--- a/native_client_sdk/doc_generated/devguide/devcycle/building.html |
+++ b/native_client_sdk/doc_generated/devguide/devcycle/building.html |
@@ -481,9 +481,9 @@ newlib toolchain are in <code>toolchain/win_x86_newlib/x86_64-nacl/lib64</code>. |
<li>ARM toolchain: <code>toolchain/<platform>_arm_<c_library>/arm-nacl/include</code></li> |
</ul> |
<p>Many other libraries have been ported for use with Native Client; for more |
-information, see the <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> |
+information, see the <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a> |
project. If you port an open-source library for your own use, we recommend |
-adding it to naclports.</p> |
+adding it to webports.</p> |
<p>Besides the standard libraries, the SDK includes Pepper libraries. |
The PNaCl Pepper libraries are located in the the |
<code>nacl_sdk/pepper_<version>/lib/pnacl/<Release or Debug></code> directory. |
@@ -524,7 +524,7 @@ how to use ppapi_simple, <code>see examples/tutorial/using_ppapi_simple</code>.< |
<li>Since the Native Client toolchains use their own library and header search |
paths, the tools won’t find third-party libraries you use in your |
non-Native-Client development. If you want to use a specific third-party |
-library for Native Client development, look for it in <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a>, or port the library yourself.</li> |
+library for Native Client development, look for it in <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a>, or port the library yourself.</li> |
<li>The order in which you list libraries in your build commands is important, |
since the linker searches and processes libraries in the order in which they |
are specified. See the <code>\*_LDFLAGS</code> variables in the Makefiles of the SDK |