| /external/chromium_org/native_client_sdk/doc_generated/devguide/devcycle/ |
| vs-addin.html | 70 <li>Compile your module into a .nexe or .pexe file using the Native Client SDK
104 module built and running as a .nexe file. This offers the ability to port
112 builds the corresponding type of Native Client module (either a .nexe or
119 systems respectively. You need both platforms to build a full set of .nexe
125 <p>The NaClARM platform is targeted at ARM-based processors. You can build .nexe
128 an ARM-based .nexe file and then run the module from a Chrome browser on an ARM
140 manifest file will contain a single .pexe file rather than multiple .nexe
144 Native Client SDK to transform the .pexe file into a NaCl64 .nexe file and runs
325 <li><code>Application (.nexe)</code> for <code>NaCl32</code>, <code>NaCl64</code>, and <code>NaClARM</code></li>
382 or .nexe files that Visual Studio builds. These will be placed in th
[all...] |
| /external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/ |
| vs-addin.rst | 42 * Compile your module into a .nexe or .pexe file using the Native Client SDK
86 module built and running as a .nexe file. This offers the ability to port
97 builds the corresponding type of Native Client module (either a .nexe or
107 systems respectively. You need both platforms to build a full set of .nexe
116 The NaClARM platform is targeted at ARM-based processors. You can build .nexe
119 an ARM-based .nexe file and then run the module from a Chrome browser on an ARM
136 manifest file will contain a single .pexe file rather than multiple .nexe
141 Native Client SDK to transform the .pexe file into a NaCl64 .nexe file and runs
365 * ``Application (.nexe)`` for ``NaCl32``, ``NaCl64``, and ``NaClARM``
441 or .nexe files that Visual Studio builds. These will be placed in th
[all...] |
| building.rst | 36 Native Client also supports architecture-specific **nexe** files.
37 These **nexe** files are **also** operating-system-independent,
50 **nexe** applications.
137 architecture-specific **.nexe** (e.g., for debugging purposes).
152 Disassembler for both **pexe** files and **nexe** files
375 support building **nexe** files. Run the tool with the ``--version``
393 **.nexe**.
428 architecture, and using the newlib library, you can compile a 32-bit **.nexe**
436 -Lnacl_sdk/pepper_<version>/lib/newlib/Release -o hello_world_x86_32.nexe \
439 To compile a 64-bit **.nexe**, you can run the same command but use -m64 instea
[all...] |
| /external/chromium_org/native_client_sdk/src/doc/ |
| faq.rst | 57 not one ``.nexe`` file per supported architecture.
216 Store. Native Client's ``.nexe`` files are architecture-dependent and
367 even the ``.pexe`` to ``.nexe`` translator, a simplified compiler
407 generate a ``.nexe`` targetting one specific architecture using the
411 How can my web application determine which ``.nexe`` to load?
415 x86-32, x86-64 or ARM ``.nexe`` explicitly---the Native Client runtime
416 examines a manifest file (``.nmf``) to pick the right ``.nexe`` file for
453 The ``.nmf``, and ``.nexe`` or ``.pexe`` files must either be served from the
473 * Build and supply a separate ``.nexe`` file for each architecture, and
476 ``.nexe`` files will run on which architectures
[all...] |
| index.rst | 53 Client, NaCl runs architecture-dependent (**nexe**) modules, which are
54 packaged into an application. At runtime, the browser decides which nexe to
|
| overview.rst | 165 based toolchain produces multiple architecture-dependent (**nexe**) modules,
167 which nexe to load based on the architecture of the client machine.
206 to run pexe modules. Internally, the translator compiles a pexe to a nexe
207 (described above), and then executes the nexe within the Native Client sandbox
211 Native Client also supports the execution of nexe modules directly in the
|
| /external/chromium_org/native_client_sdk/doc_generated/reference/ |
| nacl-manifest-format.html | 18 <li><a class="reference internal" href="#nexe-matching" id="id8">Nexe matching</a></li>
118 "main.nexe": {
140 <code>"main.nexe"</code> field of the <code>files</code> dictionary.</p>
148 "main.nexe" : {
149 "x86-64": {"url": "pi_generator_x86_64.nexe"},
150 "x86-32": {"url": "pi_generator_x86_32.nexe"}
202 <h3 id="nexe-matching">Nexe matching</h3>
205 <p>For Native Client, the main nexe for the application is determined b
[all...] |
| /external/chromium_org/native_client_sdk/doc_generated/devguide/coding/ |
| application-structure.html | 34 architecture-specific executable files (with .nexe extensions).</li>
102 for a given architecture?specifically, the URL of the .nexe file, given by the
109 "url": "hello_tutorial_x86_32.nexe"
112 "url": "hello_tutorial_x86_64.nexe"
115 "url": "hello_tutorial_arm.nexe"
134 a NaCl .nexe file.</p>
|
| /external/chromium_org/native_client_sdk/doc_generated/ |
| faq.html | 52 <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>
68 <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>
118 not one <code>.nexe</code> file per supported architecture.</li>
232 Store. Native Client’s <code>.nexe</code> files are architecture-dependent and
333 even the <code>.pexe</code> to <code>.nexe</code> translator, a simplified compiler
359 generate a <code>.nexe</code> targetting one specific architecture using the
362 <h3 id="how-can-my-web-application-determine-which-nexe-to-load">How can my web application determine which <code>.nexe</code> to load?</h3
[all...] |
| index.html | 38 Client, NaCl runs architecture-dependent (<strong>nexe</strong>) modules, which are
39 packaged into an application. At runtime, the browser decides which nexe to
|
| io2014.html | 117 <p>Our project combines voronoi.cc with several C++ libraries to produce a NEXE
120 <p>The resulting application combines the NEXE with some Javascript to load
188 remote get nexe nexe
189 add-symbol-file nexe
|
| /external/chromium_org/third_party/skia/platform_tools/nacl/ |
| httpd.py | 149 if path.endswith('.nexe'):
163 nexe = '.' + last_nexe
168 decoder = decode_dump.CoreDecoder(nexe, nmf, addr, None, None)
|
| /external/skia/platform_tools/nacl/ |
| httpd.py | 149 if path.endswith('.nexe'):
163 nexe = '.' + last_nexe
168 decoder = decode_dump.CoreDecoder(nexe, nmf, addr, None, None)
|
| /external/chromium_org/chrome/ |
| interactive_ui_tests.isolate | 108 '<(PRODUCT_DIR)/nacl_irt_x86_64.nexe',
|
| /external/chromium_org/chrome/test/chromeos/autotest/files/client/deps/chrome_test/ |
| setup_test_links.sh | 23 ln -f -s /opt/google/chrome/nacl_irt_*.nexe "$this_dir/"
|
| /external/chromium_org/native_client_sdk/doc_generated/reference/sandbox_internals/ |
| index.html | 13 in a <strong>pexe</strong> is translated to a machine-specific <strong>nexe</strong> before
|
| /external/chromium_org/native_client_sdk/src/tools/lib/ |
| elf.py | 16 """Determine properties of a nexe by parsing elf header.
|
| /external/chromium_org/ppapi/native_client/ |
| chrome_main.scons | 229 # For static linking, assume the nexe and nmf files are already
268 # Put what used to be specified under 'program' into 'main.nexe'.
269 obj['files']['main.nexe'] = {}
271 obj['files']['main.nexe'][k] = v.copy()
282 # Run sel_ldr on the nexe to trace the NEEDED libraries.
302 nmf_data = {'program': dict((arch, {'url': '%s_%s.nexe' % (exe_name, arch)})
323 '${STAGING_DIR}/%s.nexe' % env.ProgramNameForNmf(exe_name))
486 # Set a given file to be the nexe's stdin.
492 # Set a given file to be the nexe's stdout or stderr. The tester also
|
| /external/chromium_org/ppapi/native_client/src/trusted/plugin/ |
| temporary_file.h | 18 // the object file created by llc. The second holds the nexe produced by
|
| /external/chromium_org/ppapi/native_client/tests/breakpad_crash_test/ |
| crash_in_syscall.html | 51 embed.lastError.indexOf('Nexe crashed during startup') != -1);
|
| untrusted_crash.html | 51 embed.lastError.indexOf('Nexe crashed during startup') != -1);
|
| /external/chromium_org/chrome/test/nacl/ |
| nacl_browsertest_util.h | 88 // Run a simple test that checks that a nexe loads correctly. Useful for
185 // Currently, translation from pexe to non-sfi nexe is supported only for
|
| /external/chromium_org/native_client_sdk/src/build_tools/ |
| build_app.py | 41 re.search(r'_unstripped_.*?\.nexe', f)):
56 if ext in ('.nexe', '.so'):
|
| build_sdk.py | 380 ['irt_core_newlib_x32.nexe', 'irt_core_x86_32.nexe'],
381 ['irt_core_newlib_x64.nexe', 'irt_core_x86_64.nexe'],
407 if platform == 'win' and not pair[0].endswith('.nexe'):
416 ['irt_core_newlib_arm.nexe', 'irt_core_arm.nexe'],
417 ['irt_core_newlib_arm.nexe', 'irt_core_arm.nexe'],
[all...] |
| /external/chromium_org/components/nacl/renderer/ |
| json_manifest.cc | 46 // "x86-32": {"url": "myprogram_x86-32.nexe"},
47 // "x86-64": {"url": "myprogram_x86-64.nexe"},
48 // "arm": {"url": "myprogram_arm.nexe"}
51 // "x86-32": {"url": "interpreter_x86-32.nexe"},
52 // "x86-64": {"url": "interpreter_x86-64.nexe"},
53 // "arm": {"url": "interpreter_arm.nexe"}
289 // "pnacl-translate", which would cause the creation of a nexe.
|
