1VERSION
2-------
3
4What version number is this target.
5
6For shared libraries ``VERSION`` and :prop_tgt:`SOVERSION` can be used
7to specify the build version and API version respectively.  When building or
8installing appropriate symlinks are created if the platform supports
9symlinks and the linker supports so-names.  If only one of both is
10specified the missing is assumed to have the same version number.  For
11executables ``VERSION`` can be used to specify the build version.  When
12building or installing appropriate symlinks are created if the
13platform supports symlinks.
14
15Windows Versions
16^^^^^^^^^^^^^^^^
17
18For shared libraries and executables on Windows the ``VERSION``
19attribute is parsed to extract a ``<major>.<minor>`` version number.
20These numbers are used as the image version of the binary.
21
22Mach-O Versions
23^^^^^^^^^^^^^^^
24
25For shared libraries and executables on Mach-O systems (e.g. macOS, iOS),
26the :prop_tgt:`SOVERSION` property corresponds to the *compatibility version*
27and ``VERSION`` corresponds to the *current version* (unless Mach-O specific
28overrides are provided, as discussed below).
29See the :prop_tgt:`FRAMEWORK` target property for an example.
30
31For shared libraries, the :prop_tgt:`MACHO_COMPATIBILITY_VERSION` and
32:prop_tgt:`MACHO_CURRENT_VERSION` properties can be used to
33override the *compatibility version* and *current version* respectively.
34Note that :prop_tgt:`SOVERSION` will still be used to form the
35``install_name`` and both :prop_tgt:`SOVERSION` and ``VERSION`` may also
36affect the file and symlink names.
37
38Versions of Mach-O binaries may be checked with the ``otool -L <binary>``
39command.
40