061d20be38
When creating an IMPORTED target for a library that has been found on disk, it may not be known whether the library is STATIC or SHARED. However, the library may still be linked using the file found from disk. Use of an IMPORTED target is still important to allow per-configuration files to be specified for the library. This change creates an UNKNOWN type for IMPORTED library targets. The IMPORTED_LOCATION property (and its per-config equivalents) specifies the location of the library. CMake makes no assumptions about the library that cannot be inferred from the file on disk. This will help projects and find-modules import targets found on disk or specified by the user. |
||
|---|---|---|
| .. | ||
| TestSubDir | ||
| scripts | ||
| CMakeLists.txt | ||
| InstallScript1.cmake | ||
| InstallScript2.cmake | ||
| InstallScript3.cmake | ||
| InstallScript4.cmake | ||
| PackageScript.cmake | ||
| PostInstall.cmake | ||
| PreInstall.cmake | ||
| foo.c | ||
| foo.h | ||
| inst.cxx | ||
| inst2.cxx | ||
| lib1.cxx | ||
| lib1.h | ||
| lib2.cxx | ||
| lib2.h | ||
| lib3.cxx | ||
| lib3.h | ||
| lib4.cxx | ||
| lib4.h | ||