tree fac871d27b0c23ad3c45b4d9a521785a4f88f8e4
parent 898ba64d2463bb70a2e21bf86c69dbc44ec9cd5f
author Chad Versace <chad@kiwitree.net> 1649941452 -0700
committer GitHub <noreply@github.com> 1649941452 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiWBvMCRBK7hj4Ov3rIwAAABMIADUnBHF3849mhRfTKrnkEwM3
 BIR59qOCWp8qp1X5kV7XEmniO5uDhccg9oDKGHkCLrkXpS4OYnZIIpeDiNbCIQIZ
 +2lSa10bt9fqHmtIYQIwWnbI8xALQkFGZleuQ3rUbkr4L19B7USxrMc0Edao3KLs
 CrjAy1CQX+eYCAhT5cyFyMITu2cRHyNStaotSvTsu3jAhotwII6SKWtB8ZDsK3ur
 KC/t1p9C68Ol7VqUjI3gK3W0V5uvo/5qJk5k2AvcRNPspm+94r+ewPWj+6/t497x
 pezqEdfwgKNr4hj/6dDbZ9PO1an/2qgIKGkj+B5gisEtRaWpArY8BOoOXQJK6Zk=
 =yAB+
 -----END PGP SIGNATURE-----
 

Fix CMake for librt (#4773)

In the installed file
/usr/lib64/cmake/SPIRV-Tools/SPIRV-ToolsTarget.cmake, occurences of
librt in the INTERFACE_LINK_LIBRARIES property are incorrect.  The
property contains the absolute path to librt. In most situations, this
produces no problem. But when building in a sysroot, which is commonly
done when cross-compiling, the absolute path breaks dependent projects.

For example, when building spirv-tools using the Chrome OS SDK, and
targeting the board 'volteer', where the build sysroot is
'/build/volteer', the file includes this line
    INTERFACE_LINK_LIBRARIES "/build/volteer/usr/lib64/librt.so"
when it should instead say
    INTERFACE_LINK_LIBRARIES "rt"

The CMake documentation agrees [1]:
    Note that it is not advisable to populate the
    INTERFACE_LINK_LIBRARIES of a target with absolute paths to
    dependencies. That would hard-code into installed packages the
    library file paths for dependencies as found on the machine the
    package was made on.

[1] https://cmake.org/cmake/help/latest/prop_tgt/INTERFACE_LINK_LIBRARIES.html