Executables

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Virtual machine code)
Line 28: Line 28:
 
(can't be run by themselves, but are used at runtime by other executables)
 
(can't be run by themselves, but are used at runtime by other executables)
  
* [[Assembly manifest (Windows)]] (.manifest)
 
 
* [[DOS device driver]] (.sys)
 
* [[DOS device driver]] (.sys)
 
* [[Dynamic library (OS X or iOS)]] (.dylib)
 
* [[Dynamic library (OS X or iOS)]] (.dylib)
 
* [[Dynamic-link library (Windows)]] (.dll)
 
* [[Dynamic-link library (Windows)]] (.dll)
 
* [[Turbo Pascal chain file]] (.chn)
 
* [[Turbo Pascal chain file]] (.chn)
 +
 +
== Meta-info files used in execution of programs/packages ==
 +
 +
* [[Assembly manifest (Windows)]] (.manifest)
 +
* [[Program Information File]] (PIF)
  
 
== Virtual machine code ==
 
== Virtual machine code ==

Revision as of 14:20, 18 April 2015

File Format
Name Executables
Ontology

{{{caption}}}

Container formats for machine executable code. These often define different sections to be loaded into memory. Some formats may be compatible with different CPU architectures.

Contents

Directly executable

Shared libraries, chained files, etc.

(can't be run by themselves, but are used at runtime by other executables)

Meta-info files used in execution of programs/packages

Virtual machine code

See also

See also Source code for code in a higher-level programming language that needs to be compiled, assembled, or interpreted, and Development for other files used in the development process, including object and library files that get linked into a finished executable. See Archiving for some forms of self-extracting archives and installer packages.

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox