A software build is the process of converting source code files into standalone software artifact(s) that can be run on a computer, or the result of doing so.
In software production, builds optimize software for performance and distribution, packaging into formats such as '.exe'; '.deb'; '.apk'.
_q.jpg)
A linker or link editor is a computer program that combines intermediate software build files such as object and library files into a single executable file such as a program or library. A linker is often part of a toolchain that includes a compiler and/or assembler that generates intermediate files that the linker processes. The linker may be integrated with other toolchain tools such that the user does not interact with the linker directly.
A simpler version that writes its output directly to memory is called the loader, though loading is typically considered a separate process.
Build automation is the practice of building software systems in a relatively unattended fashion. The build is configured to run with minimized or no software developer interaction and without using a developer's personal computer. Build automation encompasses the act of configuring the build system as well the resulting system itself.
Build automation encompasses both sequencing build operations via non-interactive interface tools and running builds on a shared server.
View the full Wikipedia page for Build automationIn computing, a plug-in (also spelled plugin), add-in (also addin, add-on, or addon) or extension is a software component that extends the functionality of an existing software system without requiring the system to be re-built. A plug-in feature is one way that a system can be customizable.
Applications support plug-ins for a variety of reasons including:
View the full Wikipedia page for Plug-in (computing)In software development, a fork is a codebase that is created by duplicating an existing codebase and, generally, is subsequently modified independently of the original. Software built from a fork initially has identical behavior as software built from the original code, but as the source code is increasingly modified, the resulting software tends to have increasingly different behavior compared to the original. A fork is a form of branching, but generally involves storing the forked files separately from the original; not in the repository. Reasons for forking a codebase include user preference, stagnated or discontinued development of the original software or a schism in the developer community. Forking proprietary software (such as Unix) is prohibited by copyright law without explicit permission, but free and open-source software, by definition, may be forked without permission.
View the full Wikipedia page for Fork (software development)A codebase (or code base) is a collection of source code that is maintained as a unit. Typically, it can be used to build one or more software components including applications and libraries.
A codebase is typically stored in a source control repository of a version control system. A repository can contain build-generated files (which are therefore not source code), but typically such files are excluded from a repository, and therefore the codebase. A repository may contain data files (such as configuration) that are required for building or running the resulting software. But version control is not a required aspect of a codebase. Even the Linux kernel was maintained without version control for many years.
View the full Wikipedia page for Codebase