Lines Matching refs:nexe
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.
525 My ``.nexe`` files never finish loading. What gives?
540 * Make sure that the ``.nexe`` files are being served from a web
548 * The ``.nexe`` files must have been compiled using SDK version 0.5 or
550 * You must load the correct ``.nexe`` file for your machine's specific
552 you're loading the correct ``.nexe`` file by building a separate
553 ``.nexe`` for each architecture, and using a ``.nmf`` manifest file to
554 let the browser select the correct ``.nexe`` file. Note: the need to
555 select a processor-specific ``.nexe`` goes away with Portable Native
