Executables

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Virtual machine code)
(Virtual machine code)
Line 41: Line 41:
  
 
== Virtual machine code ==
 
== Virtual machine code ==
 +
(see [[Wikipedia:UVC-based preservation]] for use of virtual machines in archival preservation)
 
* [[ART (Android Runtime)]]
 
* [[ART (Android Runtime)]]
 
* [[BEAM]] (Erlang)
 
* [[BEAM]] (Erlang)

Revision as of 20:08, 3 May 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

 [hide

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 Wikipedia:UVC-based preservation for use of virtual machines in archival preservation)

Macros or automated scripting

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