[NaCl SDK] Remove references to naclports bundle

native_client_sdk/doc_generated/faq.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="frequently-asked-questions">
 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#what-is-native-client-good-for" id="id1">What is Native Client Good For?</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#why-did-google-build-native-client" id="id2">Why did Google build Native Client?</a></li>
 <li><a class="reference internal" href="#when-should-i-use-portable-native-client-instead-of-native-client" id="id3">When should I use Portable Native Client instead of Native Client?</a></li>
@@ skipping 225 matching lines @@
 cannot adapt to new architectures without recompilation, we therefore
 deem them better suited to a web store than to the open web.</p>
 <p>With Portable Native Client we deliver a system that has comparable
 portability to JavaScript and can adapt to new instruction set
 architectures without requiring recompilation. The web is better when
 it&#8217;s platform-independent, and we&#8217;d like it to stay that way.</p>
 <h3 id="do-i-have-to-use-c-or-c-i-d-really-like-to-use-another-language"><span id="other-languages"></span>Do I have to use C or C++? I&#8217;d really like to use another language.</h3>
 <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&#8217;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
 supported by compiling <a class="reference external" href="https://code.google.com/p/v8/">V8</a> to target PNaCl.</p>
 <p>The PNaCl toolchain is built on LLVM and can therefore generate code from
 languages such as <a class="reference external" href="http://www.rust-lang.org/">Rust</a>, <a class="reference external" href="https://golang.org">Go</a>, or Objective-C, but there may still be a few rough
 edges.</p>
 <p>If you&#8217;re interested in getting other languages working, please contact the
 Native Client team by way of the <a class="reference external" href="https://groups.google.com/group/native-client-discuss">native-client-discuss</a> mailing list, and read
 through <a class="reference internal" href="/native-client/reference/ideas.html"><em>contributor ideas</em></a>.</p>
@@ skipping 127 matching lines @@
 <h3 id="what-unix-system-calls-can-i-make-through-native-client">What UNIX system calls can I make through Native Client?</h3>
 <p>Native Client doesn&#8217;t directly expose any system calls from the host OS
 because of the inherent security risks and because the resulting
 application would not be portable across operating systems. Instead,
 Native Client provides portable cross-OS abstractions wrapping or
 proxying OS functionality or emulating UNIX system calls. For example,
 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>
 <h3 id="do-all-the-files-in-an-application-need-to-be-served-from-the-same-domain">Do all the files in an application need to be served from the same domain?</h3>
 <p>The <code>.nmf</code>, and <code>.nexe</code> or <code>.pexe</code> files must either be served from the
 same origin as the embedding page or an origin that has been configured
 correctly using <a class="reference external" href="http://en.wikipedia.org/wiki/Cross-origin_resource_sharing">CORS</a>.</p>
 <p>For applications installed from the Chrome Web Store the Web Store manifest
 must include the correct, verified domain of the embedding page.</p>
 <h2 id="portability">Portability</h2>
@@ skipping 85 matching lines @@
 you&#8217;re loading the correct <code>.nexe</code> file by building a separate
 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest file to
 let the browser select the correct <code>.nexe</code> file. Note: the need to
 select a processor-specific <code>.nexe</code> goes away with Portable Native
 Client.</li>
 <li>If things still aren&#8217;t working, <a class="reference internal" href="/native-client/help.html"><em>ask for help</em></a>!</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}