Do not set SONAME for MODULE library targets (#15705)

The SONAME field is only useful for shared libraries that application
link against.
This commit is contained in:
Felix Geyer
2015-08-20 14:13:28 +02:00
committed by Brad King
parent 899458ab20
commit f799ffb5cb
6 changed files with 23 additions and 36 deletions

View File

@@ -1,11 +1,11 @@
NO_SONAME
---------
Whether to set "soname" when linking a shared library or module.
Whether to set "soname" when linking a shared library.
Enable this boolean property if a generated shared library or module
Enable this boolean property if a generated shared library
should not have "soname" set. Default is to set "soname" on all
shared libraries and modules as long as the platform supports it.
shared libraries as long as the platform supports it.
Generally, use this property only for leaf private libraries or
plugins. If you use it on normal shared libraries which other targets
link against, on some platforms a linker will insert a full path to

View File

@@ -0,0 +1,7 @@
modules-no-soname
-----------------
* The ``SONAME`` field is no longer set for ``MODULE`` libraries
created with the :command:`add_library` command. ``MODULE``
libraries are meant for explicit dynamic loading at runtime.
They cannot be linked so ``SONAME`` is not useful.