native_client_sdk/doc_generated/faq.html - Issue 909383002: NaCl docs: add project ideas

Unified Diff: native_client_sdk/doc_generated/faq.html

Issue 909383002: NaCl docs: add project ideas (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Rebase. Created 5 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « chrome/common/extensions/docs/templates/json/chrome_sidenav.json ('k') | native_client_sdk/doc_generated/reference/ideas.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: native_client_sdk/doc_generated/faq.html

diff --git a/native_client_sdk/doc_generated/faq.html b/native_client_sdk/doc_generated/faq.html

index e165eee9d61b6eca0bf757bfc425f7cbacece6ad..8b05b15e31ef9e7f0737f766d526b7f48fecb2f7 100644

--- a/native_client_sdk/doc_generated/faq.html

+++ b/native_client_sdk/doc_generated/faq.html

@@ -23,49 +23,50 @@

<li><a class="reference internal" href="#openness-and-supported-architectures-and-languages" id="id11">Openness, and Supported Architectures and Languages</a>

<li><a class="reference internal" href="#is-native-client-open-is-it-a-standard" id="id12">Is Native Client open? Is it a standard?</a></li>

-<li><a class="reference internal" href="#what-are-the-supported-instruction-set-architectures" id="id13">What are the supported instruction set architectures?</a></li>

-<li><a class="reference internal" href="#do-i-have-to-use-c-or-c-i-d-really-like-to-use-another-language" id="id14">Do I have to use C or C++? I’d really like to use another language.</a></li>

-<li><a class="reference internal" href="#do-you-only-support-chrome-what-about-other-browsers" id="id15">Do you only support Chrome? What about other browsers?</a></li>

-<li><a class="reference internal" href="#what-s-the-difference-between-npapi-and-pepper" id="id16">What’s the difference between NPAPI and Pepper?</a></li>

-<li><a class="reference internal" href="#is-npapi-part-of-the-native-client-sdk" id="id17">Is NPAPI part of the Native Client SDK?</a></li>

-<li><a class="reference internal" href="#does-native-client-support-simd-vector-instructions" id="id18">Does Native Client support SIMD vector instructions?</a></li>

-<li><a class="reference internal" href="#can-i-use-native-client-for-3d-graphics" id="id19">Can I use Native Client for 3D graphics?</a></li>

-<li><a class="reference internal" href="#does-native-client-support-concurrency-parallelism" id="id20">Does Native Client support concurrency/parallelism?</a></li>

+<li><a class="reference internal" href="#how-can-i-contribute-to-native-client" id="id13">How can I contribute to Native Client?</a></li>

+<li><a class="reference internal" href="#what-are-the-supported-instruction-set-architectures" id="id14">What are the supported instruction set architectures?</a></li>

+<li><a class="reference internal" href="#do-i-have-to-use-c-or-c-i-d-really-like-to-use-another-language" id="id15">Do I have to use C or C++? I’d really like to use another language.</a></li>

+<li><a class="reference internal" href="#do-you-only-support-chrome-what-about-other-browsers" id="id16">Do you only support Chrome? What about other browsers?</a></li>

+<li><a class="reference internal" href="#what-s-the-difference-between-npapi-and-pepper" id="id17">What’s the difference between NPAPI and Pepper?</a></li>

+<li><a class="reference internal" href="#is-npapi-part-of-the-native-client-sdk" id="id18">Is NPAPI part of the Native Client SDK?</a></li>

+<li><a class="reference internal" href="#does-native-client-support-simd-vector-instructions" id="id19">Does Native Client support SIMD vector instructions?</a></li>

+<li><a class="reference internal" href="#can-i-use-native-client-for-3d-graphics" id="id20">Can I use Native Client for 3D graphics?</a></li>

+<li><a class="reference internal" href="#does-native-client-support-concurrency-parallelism" id="id21">Does Native Client support concurrency/parallelism?</a></li>

</ul>

</li>

-<li><a class="reference internal" href="#coming-soon" id="id21">Coming Soon</a>

+<li><a class="reference internal" href="#coming-soon" id="id22">Coming Soon</a>

-<li><a class="reference internal" href="#do-native-client-modules-have-access-to-external-devices" id="id22">Do Native Client modules have access to external devices?</a></li>

+<li><a class="reference internal" href="#do-native-client-modules-have-access-to-external-devices" id="id23">Do Native Client modules have access to external devices?</a></li>

</ul>

</li>

-<li><a class="reference internal" href="#security-and-privacy" id="id23">Security and Privacy</a>

+<li><a class="reference internal" href="#security-and-privacy" id="id24">Security and Privacy</a>

-<li><a class="reference internal" href="#what-happens-to-my-data-when-i-use-native-client" id="id24">What happens to my data when I use Native Client?</a></li>

-<li><a class="reference internal" href="#how-does-native-client-prevent-sandboxed-code-from-doing-bad-things" id="id25">How does Native Client prevent sandboxed code from doing Bad Things?</a></li>

-<li><a class="reference internal" href="#how-does-google-know-that-the-safety-measures-in-native-client-are-sufficient" id="id26">How does Google know that the safety measures in Native Client are sufficient?</a></li>

+<li><a class="reference internal" href="#what-happens-to-my-data-when-i-use-native-client" id="id25">What happens to my data when I use Native Client?</a></li>

+<li><a class="reference internal" href="#how-does-native-client-prevent-sandboxed-code-from-doing-bad-things" id="id26">How does Native Client prevent sandboxed code from doing Bad Things?</a></li>

+<li><a class="reference internal" href="#how-does-google-know-that-the-safety-measures-in-native-client-are-sufficient" id="id27">How does Google know that the safety measures in Native Client are sufficient?</a></li>

</ul>

</li>

-<li><a class="reference internal" href="#development" id="id27">Development</a>

+<li><a class="reference internal" href="#development" id="id28">Development</a>

-<li><a class="reference internal" href="#how-do-i-debug" id="id28">How do I debug?</a></li>

-<li><a class="reference internal" href="#how-do-i-build-x86-32-x86-64-or-arm-nexes" id="id29">How do I build x86-32, x86-64 or ARM <code>.nexes</code>?</a></li>

-<li><a class="reference internal" href="#how-can-my-web-application-determine-which-nexe-to-load" id="id30">How can my web application determine which <code>.nexe</code> to load?</a></li>

-<li><a class="reference internal" href="#is-it-possible-to-build-a-native-client-module-with-just-plain-c-not-c" id="id31">Is it possible to build a Native Client module with just plain C (not C++)?</a></li>

-<li><a class="reference internal" href="#what-unix-system-calls-can-i-make-through-native-client" id="id32">What UNIX system calls can I make through Native Client?</a></li>

-<li><a class="reference internal" href="#is-my-favorite-third-party-library-available-for-native-client" id="id33">Is my favorite third-party library available for Native Client?</a></li>

-<li><a class="reference internal" href="#do-all-the-files-in-an-application-need-to-be-served-from-the-same-domain" id="id34">Do all the files in an application need to be served from the same domain?</a></li>

+<li><a class="reference internal" href="#how-do-i-debug" id="id29">How do I debug?</a></li>

+<li><a class="reference internal" href="#how-do-i-build-x86-32-x86-64-or-arm-nexes" id="id30">How do I build x86-32, x86-64 or ARM <code>.nexes</code>?</a></li>

+<li><a class="reference internal" href="#how-can-my-web-application-determine-which-nexe-to-load" id="id31">How can my web application determine which <code>.nexe</code> to load?</a></li>

+<li><a class="reference internal" href="#is-it-possible-to-build-a-native-client-module-with-just-plain-c-not-c" id="id32">Is it possible to build a Native Client module with just plain C (not C++)?</a></li>

+<li><a class="reference internal" href="#what-unix-system-calls-can-i-make-through-native-client" id="id33">What UNIX system calls can I make through Native Client?</a></li>

+<li><a class="reference internal" href="#is-my-favorite-third-party-library-available-for-native-client" id="id34">Is my favorite third-party library available for Native Client?</a></li>

+<li><a class="reference internal" href="#do-all-the-files-in-an-application-need-to-be-served-from-the-same-domain" id="id35">Do all the files in an application need to be served from the same domain?</a></li>

</ul>

</li>

-<li><a class="reference internal" href="#portability" id="id35">Portability</a>

+<li><a class="reference internal" href="#portability" id="id36">Portability</a>

-<li><a class="reference internal" href="#do-i-have-to-do-anything-special-to-make-my-application-run-on-different-operating-systems" id="id36">Do I have to do anything special to make my application run on different operating systems?</a></li>

-<li><a class="reference internal" href="#how-easy-is-it-to-port-my-existing-native-code-to-native-client" id="id37">How easy is it to port my existing native code to Native Client?</a></li>

+<li><a class="reference internal" href="#do-i-have-to-do-anything-special-to-make-my-application-run-on-different-operating-systems" id="id37">Do I have to do anything special to make my application run on different operating systems?</a></li>

+<li><a class="reference internal" href="#how-easy-is-it-to-port-my-existing-native-code-to-native-client" id="id38">How easy is it to port my existing native code to Native Client?</a></li>

</ul>

</li>

-<li><a class="reference internal" href="#troubleshooting" id="id38">Troubleshooting</a>

+<li><a class="reference internal" href="#troubleshooting" id="id39">Troubleshooting</a>

-<li><a class="reference internal" href="#my-pexe-isn-t-loading-help" id="id39">My <code>.pexe</code> isn’t loading, help!</a></li>

-<li><a class="reference internal" href="#my-nexe-files-never-finish-loading-what-gives" id="id40">My <code>.nexe</code> files never finish loading. What gives?</a></li>

+<li><a class="reference internal" href="#my-pexe-isn-t-loading-help" id="id40">My <code>.pexe</code> isn’t loading, help!</a></li>

+<li><a class="reference internal" href="#my-nexe-files-never-finish-loading-what-gives" id="id41">My <code>.nexe</code> files never finish loading. What gives?</a></li>

</ul>

</li>

</ul>

@@ -220,6 +221,8 @@ to consider Native Client for standardization.

We consistenly try to document our design and implementation and hope to

standardize Portable Native Client when it gains more traction. A good

example is our <a class="reference internal" href="/native-client/reference/pnacl-bitcode-abi.html">PNaCl bitcode reference manual</a>.

+<h3 id="how-can-i-contribute-to-native-client">How can I contribute to Native Client?</h3>

+Read about <a class="reference internal" href="/native-client/reference/ideas.html">contributor ideas</a>.

<h3 id="what-are-the-supported-instruction-set-architectures">What are the supported instruction set architectures?</h3>

Portable Native Client uses an architecture-independent format (the

<code>.pexe</code>) which can currently be translated to execute on processors

@@ -249,7 +252,8 @@ supported by compiling <a class="reference external" href="https://code.google.c

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.

If you’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.

+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">contributor ideas</a>.

<h3 id="do-you-only-support-chrome-what-about-other-browsers">Do you only support Chrome? What about other browsers?</h3>

We aim to support multiple browsers. However, a number of features that

we consider requirements for a production-quality system that keeps the

@@ -389,7 +393,9 @@ the standard UNIX <code>mmap()</code> system call.

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

-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.

+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">contributor ideas</a> to find ideas of new projects

+to port.

<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>

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