Home | History | Annotate | Download | only in tools

Lines Matching refs:nexe

6 """Tool for automatically creating .nmf files from .nexe/.pexe/.bc executables.
45 MAIN_NEXE = 'main.nexe' # Name of entry point for execution
184 files->main.nexe for dynamic nexes, and program for static nexes
216 # the first nexe found in main_files.
231 Example: { '/path/to/my.nexe': ArchFile(my.nexe),
266 files are relative to the .nexe with the matching architecture. This is
273 main_nexes = [f for f in self.main_files if f.endswith('.nexe')]
275 # map from each arch to its corresponding main nexe.
293 # staged. Its path should be relative to the main .nexe with the same
298 if arch_file.name.endswith('.nexe'):
358 NaCl will map url requests based on architecture. The startup NEXE
362 as the startup nexe. The application itself is then placed under the
389 if need.endswith(".nexe"):
394 # Otherwise, treat it like another another file named main.nexe.
546 usage='Usage: %prog [options] nexe [extra_libs...]', description=__doc__)
569 parser.add_option('-N', '--nexe-prefix', dest='nexe_prefix', default='',
578 'directory as the .nexe that matches its architecture.')
618 parser.error('No nexe files specified. See --help for more info')