VERSION.rst 1.1 KB

1234567891011121314151617181920212223242526272829
  1. VERSION
  2. -------
  3. What version number is this target.
  4. For shared libraries ``VERSION`` and :prop_tgt:`SOVERSION` can be used
  5. to specify the build version and API version respectively. When building or
  6. installing appropriate symlinks are created if the platform supports
  7. symlinks and the linker supports so-names. If only one of both is
  8. specified the missing is assumed to have the same version number. For
  9. executables ``VERSION`` can be used to specify the build version. When
  10. building or installing appropriate symlinks are created if the
  11. platform supports symlinks.
  12. Windows Versions
  13. ^^^^^^^^^^^^^^^^
  14. For shared libraries and executables on Windows the ``VERSION``
  15. attribute is parsed to extract a ``<major>.<minor>`` version number.
  16. These numbers are used as the image version of the binary.
  17. Mach-O Versions
  18. ^^^^^^^^^^^^^^^
  19. For shared libraries and executables on Mach-O systems (e.g. OS X, iOS),
  20. the :prop_tgt:`SOVERSION` property correspond to *compatibility version* and
  21. ``VERSION`` to *current version*. See the :prop_tgt:`FRAMEWORK` target
  22. property for an example. Versions of Mach-O binaries may be checked with the
  23. ``otool -L <binary>`` command.