What version number is this target.
For shared libraries
SOVERSION can be used to specify the build version and API version respectively. When building or installing appropriate symlinks are created if the platform supports symlinks and the linker supports so-names. If only one of both is specified the missing is assumed to have the same version number.
SOVERSION is ignored if
NO_SONAME property is set.
For shared libraries and executables on Windows the
VERSION attribute is parsed to extract a
<major>.<minor> version number. These numbers are used as the image version of the binary.
For shared libraries and executables on Mach-O systems (e.g. macOS, iOS), the
SOVERSION property corresponds to the compatibility version and
VERSION corresponds to the current version (unless Mach-O specific overrides are provided, as discussed below). See the
FRAMEWORK target property for an example.
For shared libraries, the
MACHO_CURRENT_VERSION properties can be used to override the compatibility version and current version respectively. Note that
SOVERSION will still be used to form the
install_name and both
VERSION may also affect the file and symlink names.
Versions of Mach-O binaries may be checked with the
otool -L <binary> command.
© 2000–2020 Kitware, Inc. and Contributors
Licensed under the BSD 3-clause License.