| /external/chromium_org/native_client_sdk/src/tools/ |
| ncval.py | 32 usage = 'Usage: %prog [options] <.nexe | .so>'
33 epilog = 'Example: ncval.py my_nexe.nexe'
51 nexe = args[0]
58 if not os.path.exists(nexe):
59 raise Error('executable not found: %s' % nexe)
60 if not os.path.isfile(nexe):
61 raise Error('not a file: %s' % nexe)
67 cmd = [ncval, nexe]
73 sys.stderr.write('Validating %s failed:\n' % nexe)
76 Log('Changing the modification time of %s to 0.' % nexe)
[all...] |
| sel_ldr.py | 36 usage = 'Usage: %prog [options] <.nexe>'
37 epilog = 'Example: sel_ldr.py my_nexe.nexe'
60 nexe = args[0]
65 if not os.path.exists(nexe):
66 raise Error('executable not found: %s' % nexe)
67 if not os.path.isfile(nexe):
68 raise Error('not a file: %s' % nexe)
70 arch, dynamic = create_nmf.ParseElfHeader(nexe)
78 irt = os.path.join(SCRIPT_DIR, 'irt_core_%s.nexe' % arch_suffix)
|
| nacl_llvm.mk | 102 $(1)_x86_32.nexe : $(1).bc
105 $(1)_x86_64.nexe : $(1).bc
108 $(1)_arm.nexe : $(1).bc
129 # NOTE: For Debug builds we translate the .bc file to a .nexe instead of
169 EXECUTABLES=$(OUTDIR)/$(1)_x86_32.nexe $(OUTDIR)/$(1)_x86_64.nexe $(OUTDIR)/$(1)_arm.nexe
194 # the .bc -> .nexe translated app.
196 GDB_DEBUG_TARGET = $(abspath $(OUTDIR))/$(TARGET)_$(SYSARCH).nexe
|
| nacl_gcc.mk | 296 all: $(OUTDIR)/$(1)_x86_32.nexe
297 $(OUTDIR)/$(1)_x86_32.nexe: $(foreach src,$(2),$(call SRC_TO_OBJ,$(src),_x86_32)) $(foreach dep,$(4),$(STAMPDIR)/$(dep).stamp)
303 all: $(OUTDIR)/$(1)_x86_64.nexe
304 $(OUTDIR)/$(1)_x86_64.nexe: $(foreach src,$(2),$(call SRC_TO_OBJ,$(src),_x86_64)) $(foreach dep,$(4),$(STAMPDIR)/$(dep).stamp)
310 all: $(OUTDIR)/$(1)_arm.nexe
311 $(OUTDIR)/$(1)_arm.nexe: $(foreach src,$(2),$(call SRC_TO_OBJ,$(src),_arm)) $(foreach dep,$(4),$(STAMPDIR)/$(dep).stamp)
341 $(OUTDIR)/$(1)_x86_32.nexe: $(OUTDIR)/$(2)_x86_32.nexe
346 $(OUTDIR)/$(1)_x86_64.nexe: $(OUTDIR)/$(2)_x86_64.nexe
[all...] |
| create_nmf.py | 6 """Tool for automatically creating .nmf files from .nexe/.pexe executables.
58 MAIN_NEXE = 'main.nexe' # Name of entry point for execution
105 """Determine properties of a nexe by parsing elf header.
232 files->main.nexe for dynamic nexes, and program for static nexes
264 [ '/path/to/my.nexe',
274 Example: { '/path/to/my.nexe': ArchFile(my.nexe),
356 Example: { '/path/to/my.nexe': ArchFile(my.nexe),
426 # for .nexe and .so files specified on the command line stag
[all...] |
| /external/chromium_org/ppapi/native_client/tests/ppapi_browser/extension_mime_handler/ |
| nacl.scons | 17 nexe = env.ProgramNameForNmf('ppapi_extension_mime_handler') variable
20 nexe,
31 env.File('$STAGING_DIR/' + nexe + '$PROGSUFFIX')])
36 env.Depends(env.Alias(nexe), dest_copy)
39 env.Publish(nexe, 'run',
48 files=env.ExtractPublishedFiles(nexe))
|
| /external/chromium_org/v8/tools/ |
| nacl-run.py | 81 def GetNaClArchFromNexe(nexe):
83 p = subprocess.Popen(['file', nexe], stdout=subprocess.PIPE)
94 def GetNaClResources(nexe):
96 nacl_arch = GetNaClArchFromNexe(nexe)
108 irt = "irt_core_x86_64.nexe"
113 irt = "irt_core_x86_32.nexe"
119 print("Invalid nexe %s" % nexe)
|
| /external/chromium_org/components/nacl/browser/ |
| pnacl_translation_cache_unittest.cc | 42 void StoreNexe(const std::string& key, const std::string& nexe);
67 const std::string& nexe) {
70 new net::DrainableIOBuffer(new net::StringIOBuffer(nexe), nexe.size()));
117 std::string nexe(buf->data(), buf->size());
118 return nexe;
262 std::string nexe; local
|
| /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/ppapi/native_client/tests/ppapi_browser/manifest/ |
| nacl.scons | 50 # the 'good' nexe in the root directory will fail.
53 # the 'good' nexe in the subdirectory will succeed.
|
| /external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/ |
| dynamic-loading.rst | 76 downloading a .nexe file that's on the order of 30KB, rather than a .nexe
173 it demonstrates how to build Native Client modules (.nexe files) and shared
196 into a Native Client executable (.nexe).
199 to build x86 32-bit and 64-bit .nexe and .so files, and to generate a .nmf
274 create_nmf.py -o dlopen.nmf glibc/Release/dlopen_x86_32.nexe \
275 glibc/Release/dlopen_x86_64.nexe glibc/Release/libeightball_x86_32.so \
308 modules from the application itself (.nexe and .so files), modules from the
386 If your .nexe isn't loading, the best place to look for information that can
392 **/main.nexe: error while loading shared libraries: /main.nexe: failed to allocate code and data space for exec (…)
[all...] |
| vs-addin.rst | 39 * Compile your module into a .nexe or .pexe file using the Native Client SDK
83 module built and running as a .nexe file. This offers the ability to port
94 builds the corresponding type of Native Client module (either a .nexe or
104 systems respectively. You need both platforms to build a full set of .nexe
113 The NaClARM platform is targeted at ARM-based processors. You can build .nexe
116 an ARM-based .nexe file and then run the module from a Chrome browser on an ARM
133 manifest file will contain a single .pexe file rather than multiple .nexe
138 Native Client SDK to transform the .pexe file into a NaCl64 .nexe file and runs
359 * ``Application (.nexe)`` for ``NaCl32``, ``NaCl64``, and ``NaClARM``
435 or .nexe files that Visual Studio builds. These will be placed in th
[all...] |
| /external/chromium_org/ppapi/native_client/tests/ppapi_browser/bad/ |
| nacl.scons | 83 # Bad nexe tests that won't work in PNaCl (native)
84 # For example, partly_invalid.nexe has inline assembly in its source files.
85 # Just bail out here for PNaCl, since the NMF will require the .nexe
|
| /external/chromium_org/native_client_sdk/src/tools/tests/ |
| create_nmf_test.py | 29 static_nexe = os.path.join(DATA_DIR, 'test_static_arm.nexe')
33 dyn_nexe = os.path.join(DATA_DIR, 'test_dynamic_x86_32.nexe')
34 static_nexe = os.path.join(DATA_DIR, 'test_static_x86_32.nexe')
39 dyn_nexe = os.path.join(DATA_DIR, 'test_dynamic_x86_64.nexe')
40 static_nexe = os.path.join(DATA_DIR, 'test_static_x86_64.nexe')
51 static_nexe = os.path.join(DATA_DIR, 'test_static_arm.nexe')
58 dyn_nexe = os.path.join(DATA_DIR, 'test_dynamic_x86_32.nexe')
59 static_nexe = os.path.join(DATA_DIR, 'test_static_x86_32.nexe')
71 dyn_nexe = os.path.join(DATA_DIR, 'test_dynamic_x86_64.nexe')
72 static_nexe = os.path.join(DATA_DIR, 'test_static_x86_64.nexe')
[all...] |
| /external/chromium_org/ppapi/native_client/tests/nacl_browser/inbrowser_test_runner/ |
| nacl.scons | 46 # TODO(eugenis): enable when Valgrind learns to autodetect the nexe name
|
| /external/chromium_org/native_client_sdk/src/doc/ |
| faq.rst | 57 not one ``.nexe`` file per supported architecture.
209 Store. Native Client's ``.nexe`` files are architecture-dependent and
374 even the ``.pexe`` to ``.nexe`` translator, a simplified compiler
416 generate a ``.nexe`` targetting one specific architecture using the
420 How can my web application determine which ``.nexe`` to load?
424 x86-32, x86-64 or ARM ``.nexe`` explicitly---the Native Client runtime
425 examines a manifest file (``.nmf``) to pick the right ``.nexe`` file for
463 The ``.nmf``, and ``.nexe`` or ``.pexe`` files must either be served from the
483 * Build and supply a separate ``.nexe`` file for each architecture, and
486 ``.nexe`` files will run on which architectures
[all...] |
| /external/chromium_org/ppapi/native_client/tests/ppapi_browser/ |
| progress_event_listener.js | 134 // loaded and another when the .nexe is loaded.
|
| /external/chromium_org/ppapi/native_client/tools/browser_tester/browserdata/ |
| nacltest.js | 786 // Deliberately global - this is what the nexe expects.
810 // This function takes an array of messages and asserts that the nexe
898 this_.rpc.log('A nexe load error occured, aborting testing.');
|
