Build number

from Wikipedia, the free encyclopedia

A build number or build number is a sequential number that is often automatically assigned during a build process and is often part of the version number of software . For some software products, the date or even the exact time of the build is also given. In large software projects, the build number is often further subdivided, e.g. B. in build revision numbers.

relevance

The build number usually only changes when there are minor changes to software, for example after installing software updates . In order to find out whether the current version of a software is actually being used, there is usually no way around the sub-version numbers. The build number is often one of the smallest subdivisions of software updates because it is based on the build process.

Examples

The operating system Windows from Microsoft , the build number is even further in a revision number ( English RevisionNumber divided). The full version number can be read from the registration key BuildLabEx under HKEY_LOCAL_MACHINE\​Software\​Microsoft\​Windows NT\​CurrentVersion. However, it is easier to winver.exedisplay the build number via the control panel or via the program , for example Windows 10 1903 (Build 18875.1000)for an insider preview of Windows 10 1903.

Under Linux is the build number preceded by the pound , #u. a. unameoutput with the system program. Example ( Debian  10 "Buster"): 

max@MeinRechner:~$ uname -a
Linux MeinRechner 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux
                  │  │ │ │  │     │            │  │  │      │          │
                  │  │ │ │  │     │            │  │  │      │          └── Builddatum
                  │  │ │ │  │     │            │  │  │      │
                  │  │ │ │  │     │            │  │  │      └── Paketnummer: 5+deb10u2
                  │  │ │ │  │     │            │  │  │
                  │  │ │ │  │     │            │  │  └──         / Revisionsnummer     \
                  │  │ │ │  │     │            │  └───── Kernel-   Nebenversionsnummer   4.19.37
                  │  │ │ │  │     │            └────────         \ Hauptversionsnummer /
                  │  │ │ │  │     │
                  │  │ │ │  │     └── Buildnummer
                  │  │ │ │  │
                  │  │ │ │  └────── Architektur bzw. Plattform
                  │  │ │ │
                  │  │ │ └── Paketrevisionsnummer: 5
                  │  │ └────        / Basis-Revisionsnummer  \
                  │  └────── Paket-   Nebenversionsnummer      4.19.0 ist die Basisversion des Kernels
                  └─────────        \ Hauptversionsnummer    /

Since the Linux kernel with some Linux distributions is compiled by the user himself ( translated into German ), the build number is an indication of a changed kernel configuration. B. can be managed with. When the kernel is compiled again, it is given a new build number and can therefore be distinguished. This function depends on the hidden file that caches the current build number as a text file . The call deletes all files created by the build process in the kernel sources and by also deleting this text file, the counter for the build number is also reset. With it, and thus the counter for the build number, is retained.  make menuconfig .versionmake mrpropermake clean

See also

Individual evidence

  1. ↑ Mitch Frazier: Add an Auto-Incrementing Build-Number to Your Build Process. Linux Journal , June 8, 2008, accessed August 17, 2019 .
  2. ↑ Markus Kasanmascheff: Windows 10: This is how you display the version, build number and edition. netzwelt.de , May 1, 2019, accessed on August 17, 2019 .