Object file
≈ 4 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
An object file is a file that contains machine code or bytecode, as well as other data and metadata, generated by a compiler or assembler from source code during the compilation or assembly process. The machine code that is generated is known as object code. The object code is usually relocatable, and not usually directly executable. There are various formats for object files, and the same machine code can be packaged in different object file formats. An object file may also work like a shared library. The metadata that object files may include can be used for linking or debugging; it includes information to resolve symbolic cross-references between different modules, relocation information, stack unwinding information, comments, program symbols, and debugging or profiling information. Other metadata may include the date and time of compilation, the compiler name and version, and other identifying information. The term "object program" dates from at least the 1950s: A linker is used to combine the object code into one executable program or library pulling in precompiled system libraries as needed.
An object file is a file that contains machine code or bytecode, as well as other data and metadata, generated by a compiler or assembler from source code during the compilation or assembly process. The machine code that is generated is known as object code. The object code is usually relocatable, and not usually directly executable. There are various formats for object files, and the same machine code can be packaged in different object file formats. An object file may also work like a shared library. The metadata that object files may include can be used for linking or debugging; it includes information to resolve symbolic cross-references between different modules, relocation information, stack unwinding information, comments, program symbols, and debugging or profiling information. Other metadata may include the date and time of compilation, the compiler name and version, and other identifying information. The term "object program" dates from at least the 1950s: A linker is used to combine the object code into one executable program or library pulling in precompiled system libraries as needed.
Absolute files
Many early computers, or small microcomputers, support only an absolute object format. Programs are not relocatable; they need to be assembled or compiled to execute at specific, predefined addresses. The file contains no relocation or linkage information. These files can be loaded into read/write memory, or stored in read-only memory. For example, the Motorola 6800 MIKBUG monitor contains a routine to read an absolute object file (SREC Format) from paper tape. DOS COM files are a more recent example of absolute object files.
References
Further reading
Code: [ftp://ftp.iecc.com/pub/linker/] Errata: * (NB. Description of the Microsoft REL file format for relocatable objects, also used by Digital Research.) [https://www.seasip.info/Cpm/amsfid.html#PRL%20file%20format (16 pages) (1+23 pages) (1 page) (NB. Describes the history and relationship of IEEE 695 with CUFOM and MUFOM.) (NB. Supersedes IEEE 695-1985 (1985-09-09)).
Text derived from https://en.wikipedia.org/w/index.php?oldid=1375395570 under CC BY-SA 4.0; modifications have been made.