OLD | NEW |
1 {{+bindTo:partials.standard_nacl_article}} | 1 {{+bindTo:partials.standard_nacl_article}} |
2 | 2 |
3 <section id="frequently-asked-questions"> | 3 <section id="frequently-asked-questions"> |
4 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1> | 4 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1> |
5 <div class="contents local" id="contents" style="display: none"> | 5 <div class="contents local" id="contents" style="display: none"> |
6 <ul class="small-gap"> | 6 <ul class="small-gap"> |
7 <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> | 7 <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> |
8 <ul class="small-gap"> | 8 <ul class="small-gap"> |
9 <li><a class="reference internal" href="#why-did-google-build-native-client" id=
"id2">Why did Google build Native Client?</a></li> | 9 <li><a class="reference internal" href="#why-did-google-build-native-client" id=
"id2">Why did Google build Native Client?</a></li> |
10 <li><a class="reference internal" href="#when-should-i-use-portable-native-clien
t-instead-of-native-client" id="id3">When should I use Portable Native Client in
stead of Native Client?</a></li> | 10 <li><a class="reference internal" href="#when-should-i-use-portable-native-clien
t-instead-of-native-client" id="id3">When should I use Portable Native Client in
stead of Native Client?</a></li> |
(...skipping 225 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
236 portability to JavaScript and can adapt to new instruction set | 236 portability to JavaScript and can adapt to new instruction set |
237 architectures without requiring recompilation. The web is better when | 237 architectures without requiring recompilation. The web is better when |
238 it’s platform-independent, and we’d like it to stay that way.</p> | 238 it’s platform-independent, and we’d like it to stay that way.</p> |
239 <h3 id="do-i-have-to-use-c-or-c-i-d-really-like-to-use-another-language"><span i
d="other-languages"></span>Do I have to use C or C++? I’d really like to u
se another language.</h3> | 239 <h3 id="do-i-have-to-use-c-or-c-i-d-really-like-to-use-another-language"><span i
d="other-languages"></span>Do I have to use C or C++? I’d really like to u
se another language.</h3> |
240 <p>Right now only C and C++ are supported directly by the toolchain in the SDK.
C# | 240 <p>Right now only C and C++ are supported directly by the toolchain in the SDK.
C# |
241 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 | 241 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 |
242 Native Client. Moreover, there are several ongoing projects to support | 242 Native Client. Moreover, there are several ongoing projects to support |
243 additional language runtimes (e.g. <a class="reference external" href="https://c
ode.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Fexamples%2Ftools">n
aclports supports Lua, Python and Ruby</a>) | 243 additional language runtimes (e.g. <a class="reference external" href="https://c
ode.google.com/p/naclports/source/browse#svn%2Ftrunk%2Fsrc%2Fexamples%2Ftools">n
aclports supports Lua, Python and Ruby</a>) |
244 as well as to compile more languages to LLVM’s intermediate representation | 244 as well as to compile more languages to LLVM’s intermediate representation |
245 (e.g. support <a class="reference external" href="http://halide-lang.org/">Halid
e</a>, Haskell with <a class="reference external" href="http://www.haskell.org/g
hc/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 | 245 (e.g. support <a class="reference external" href="http://halide-lang.org/">Halid
e</a>, Haskell with <a class="reference external" href="http://www.haskell.org/g
hc/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 |
246 transpile languages to C/C++ (source-to-source compilation).</p> | 246 transpile languages to C/C++ (source-to-source compilation). Even JavaScript is |
| 247 supported by compiling <a class="reference external" href="https://code.google.c
om/p/v8/">V8</a> to target PNaCl.</p> |
| 248 <p>The PNaCl toolchain is built on LLVM and can therefore generate code from |
| 249 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 Ob
jective-C, but there may still be a few rough |
| 250 edges.</p> |
247 <p>If you’re interested in getting other languages working, please contact
the | 251 <p>If you’re interested in getting other languages working, please contact
the |
248 Native Client team by way of the <a class="reference external" href="https://gro
ups.google.com/group/native-client-discuss">native-client-discuss</a> mailing li
st.</p> | 252 Native Client team by way of the <a class="reference external" href="https://gro
ups.google.com/group/native-client-discuss">native-client-discuss</a> mailing li
st.</p> |
249 <h3 id="do-you-only-support-chrome-what-about-other-browsers">Do you only suppor
t Chrome? What about other browsers?</h3> | 253 <h3 id="do-you-only-support-chrome-what-about-other-browsers">Do you only suppor
t Chrome? What about other browsers?</h3> |
250 <p>We aim to support multiple browsers. However, a number of features that | 254 <p>We aim to support multiple browsers. However, a number of features that |
251 we consider requirements for a production-quality system that keeps the | 255 we consider requirements for a production-quality system that keeps the |
252 user safe are difficult to implement without help from the | 256 user safe are difficult to implement without help from the |
253 browser. Specific examples are an out-of-process plugin architecture and | 257 browser. Specific examples are an out-of-process plugin architecture and |
254 appropriate interfaces for integrated 3D graphics. We have worked | 258 appropriate interfaces for integrated 3D graphics. We have worked |
255 closely with Chromium developers to deliver these features and we are | 259 closely with Chromium developers to deliver these features and we are |
256 eager to collaborate with developers from other browsers.</p> | 260 eager to collaborate with developers from other browsers.</p> |
(...skipping 216 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
473 you’re loading the correct <code>.nexe</code> file by building a separate | 477 you’re loading the correct <code>.nexe</code> file by building a separate |
474 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest
file to | 478 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest
file to |
475 let the browser select the correct <code>.nexe</code> file. Note: the need to | 479 let the browser select the correct <code>.nexe</code> file. Note: the need to |
476 select a processor-specific <code>.nexe</code> goes away with Portable Native | 480 select a processor-specific <code>.nexe</code> goes away with Portable Native |
477 Client.</li> | 481 Client.</li> |
478 <li>If things still aren’t working, <a class="reference internal" href="/n
ative-client/help.html"><em>ask for help</em></a>!</li> | 482 <li>If things still aren’t working, <a class="reference internal" href="/n
ative-client/help.html"><em>ask for help</em></a>!</li> |
479 </ul> | 483 </ul> |
480 </section> | 484 </section> |
481 | 485 |
482 {{/partials.standard_nacl_article}} | 486 {{/partials.standard_nacl_article}} |
OLD | NEW |