IMPORTED INTERFACE libraries now behave as normal INTERFACE library / IMPORTED GLOBAL libraries can now be ALIASed.
Changes introduced by this merge-request:
- The commands
target_compile_definitions,target_compile_features,target_compile_options,target_include_directories,target_link_librariesandtarget_sourcescan now be used withIMPORTEDlibraries. -
ALIASing anIMPORTEDlibrary is now possible, too, as long as the aliasedIMPORTEDtarget is globally visible (aka was created with optionGLOBAL).
Thereby, there is no longer any difference in behavior between normal INTERFACE targets and IMPORTED INTERFACE targets. Only the behavior of IMPORTED INTERFACE targets that are non-GLOBAL differs slightly: they still cannot be aliased.
This merge-request fixes #15689 (closed), #15569 (closed) and #17197 (closed).
Topic-rename: generalize-importedtargets-behavior
Edited by Deniz Bahadir