diff options
Diffstat (limited to 'native_client_sdk/doc_generated')
7 files changed, 19 insertions, 18 deletions
diff --git a/native_client_sdk/doc_generated/cds2014/python.html b/native_client_sdk/doc_generated/cds2014/python.html index a26bd35..59f80a5 100644 --- a/native_client_sdk/doc_generated/cds2014/python.html +++ b/native_client_sdk/doc_generated/cds2014/python.html @@ -221,7 +221,7 @@ and our Python port.</p> <p>The same approach to deploying Python apps can be used for the other interpreted languages that have been ported to PNaCl.</p> <p>Check out the range of interpreters, libraries, and tools -<a class="reference external" href="https://code.google.com/p/naclports/wiki/PortList">already ported to PNaCl and ready to be integrated with your Web App</a>.</p> +<a class="reference external" href="https://chromium.googlesource.com/webports/+/master/docs/port_list.md">already ported to PNaCl and ready to be integrated with your Web App</a>.</p> <p>While our in-browser environment is rapidly evolving to become a complete development solution, for the broadest range of development options, check out the diff --git a/native_client_sdk/doc_generated/devguide/devcycle/building.html b/native_client_sdk/doc_generated/devguide/devcycle/building.html index 12f540f..0868816 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 diff --git a/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html b/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html index 0c525b1..5ee1f1a 100644 --- a/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html +++ b/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html @@ -316,8 +316,9 @@ the list of shared library dependencies using tools such as <code>objdump_</code executable code modules that the application directly depends on, including modules from the application itself (<code>.nexe</code> and <code>.so</code> files), modules from the Native Client SDK (e.g., <code>libppapi_cpp.so</code>), and perhaps also modules from -<a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> or from <a class="reference external" href="../../community/middleware">middleware systems</a> that the application uses. You must provide all -of those modules as part of the application deployment process.</p> +<a class="reference external" href="https://chromium.googlesource.com/webports">webports</a> or from <a class="reference external" href="../../community/middleware">middleware +systems</a> that the application uses. You must +provide all of those modules as part of the application deployment process.</p> <p>As explained in <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing Your Application</em></a>, there are two basic ways to deploy a <a class="reference external" href="/apps">Chrome app</a>:</p> <ul class="small-gap"> diff --git a/native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html b/native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html index 4892aeb..83e692c 100644 --- a/native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html +++ b/native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html @@ -230,10 +230,10 @@ directory) to learn additional techniques for writing Native Client applications and using the Pepper APIs.</li> <li>See the <a class="reference internal" href="/native-client/devguide/devcycle/building.html"><em>Building</em></a>, <a class="reference internal" href="/native-client/devguide/devcycle/running.html"><em>Running</em></a>, and <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>Debugging pages</em></a> for information about how to build, run, and debug Native Client applications.</li> -<li>Check the <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> project to see -what libraries have been ported for use with Native Client. If you port an -open-source library for your own use, we recommend adding it to naclports -(see <a class="reference external" href="http://code.google.com/p/naclports/wiki/HowTo_Checkin">How to check code into naclports</a>).</li> +<li>Check the <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a> project to +see what libraries have been ported for use with Native Client. If you port an +open-source library for your own use, we recommend adding it to webports +(see <a class="reference external" href="https://chromium.googlesource.com/webports/+/master/CONTRIBUTING.md">How to check code into webports</a>).</li> </ul> </section> diff --git a/native_client_sdk/doc_generated/faq.html b/native_client_sdk/doc_generated/faq.html index 8b05b15..8c158e2 100644 --- a/native_client_sdk/doc_generated/faq.html +++ b/native_client_sdk/doc_generated/faq.html @@ -243,7 +243,7 @@ it’s platform-independent, and we’d like it to stay that way.</p> <p>Right now only C and C++ are supported directly by the toolchain in the SDK. C# and other languages in the .NET family are supported via the <a class="reference external" href="https://github.com/elijahtaylor/mono">Mono port</a> for Native Client. Moreover, there are several ongoing projects to support -additional language runtimes (e.g. <a class="reference external" href="https://code.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Fexamples%2Ftools">naclports supports Lua, Python and Ruby</a>) +additional language runtimes (e.g. <a class="reference external" href="https://chromium.googlesource.com/webports">webports includes Lua, Python and Ruby</a>) as well as to compile more languages to LLVM’s intermediate representation (e.g. support <a class="reference external" href="http://halide-lang.org/">Halide</a>, Haskell with <a class="reference external" href="http://www.haskell.org/ghc/docs/latest/html/users_guide/code-generators.html">GHC</a> or support Fortran with <a class="reference external" href="https://flang-gsoc.blogspot.ie/2013/09/end-of-gsoc-report.html">flang</a>), or transpile languages to C/C++ (source-to-source compilation). Even JavaScript is @@ -391,8 +391,8 @@ Native Client provides an <code>mmap()</code> system call that behaves much like the standard UNIX <code>mmap()</code> system call.</p> <h3 id="is-my-favorite-third-party-library-available-for-native-client">Is my favorite third-party library available for Native Client?</h3> <p>Google has ported several third-party libraries to Native Client; such libraries -are available in the <a class="reference external" href="https://code.google.com/p/naclports">naclports</a> project. We encourage you to contribute -libraries to naclports, and/or to host your own ported libraries, and to let the +are available in the <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a> project. We encourage you to contribute +libraries to webports, and/or to host your own ported libraries, and to let the team know about it on <a class="reference external" href="https://groups.google.com/group/native-client-discuss">native-client-discuss</a> when you do. You can also read through <a class="reference internal" href="/native-client/reference/ideas.html"><em>contributor ideas</em></a> to find ideas of new projects to port.</p> diff --git a/native_client_sdk/doc_generated/reference/ideas.html b/native_client_sdk/doc_generated/reference/ideas.html index 2050481..2c30c64 100644 --- a/native_client_sdk/doc_generated/reference/ideas.html +++ b/native_client_sdk/doc_generated/reference/ideas.html @@ -93,13 +93,13 @@ tested, and used in a demo application.</li> </ul> <h4 id="open-source-porting">Open Source Porting</h4> <ul class="small-gap"> -<li><strong>Project:</strong> Port substantial open source projects to work in naclports.</li> -<li><strong>Brief explanation:</strong> naclports contains a large collection of open source +<li><strong>Project:</strong> Port substantial open source projects to work in webports.</li> +<li><strong>Brief explanation:</strong> webports contains a large collection of open source projects that properly compile and run on the PNaCl platform. This project -involves adding new useful projects to naclports, and upstreaming any patches +involves adding new useful projects to webports, and upstreaming any patches to the original project: running on PNaCl effective involves porting to a new architecture and operating system. Project ideas include: Gimp, Inkscape, Gtk.</li> -<li><strong>Expected results:</strong> New open source projects are usable from naclports.</li> +<li><strong>Expected results:</strong> New open source projects are usable from webports.</li> <li><strong>Knowledge Prerequisite:</strong> C/C++.</li> <li><strong>Mentor:</strong> Brad Nelson.</li> </ul> diff --git a/native_client_sdk/doc_generated/reference/pnacl-c-cpp-language-support.html b/native_client_sdk/doc_generated/reference/pnacl-c-cpp-language-support.html index 3b76173..6d9a8e0 100644 --- a/native_client_sdk/doc_generated/reference/pnacl-c-cpp-language-support.html +++ b/native_client_sdk/doc_generated/reference/pnacl-c-cpp-language-support.html @@ -163,7 +163,7 @@ replaced with calls to <code>abort()</code>. The usual <code>-fno-exceptions</co supported, though the default is <code>-fexceptions</code>. PNaCl will support full zero-cost exception handling in the future.</p> <aside> -When using <a class="reference external" href="https://code.google.com/p/naclports">naclports</a> or other prebuilt static libraries, you don’t +When using <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a> or other prebuilt static libraries, you don’t need to recompile because the exception handling support is implemented at link time (when all the static libraries are put together with your application). |