From 02da99353aa31fb31f2f3a036992c5c203d483b2 Mon Sep 17 00:00:00 2001 From: "Roscoe A. Bartlett" Date: Wed, 29 Mar 2023 10:41:41 -0600 Subject: [PATCH] Remove unused legacy RELATIVE_PATH code (#63, #560) Turns out this code was not even being used anymore after the previous refactorings. This removes a very long comment as well that is just not needed. --- ...ribitsInternalPackageWriteConfigFile.cmake | 20 ------------------- 1 file changed, 20 deletions(-) diff --git a/tribits/core/package_arch/TribitsInternalPackageWriteConfigFile.cmake b/tribits/core/package_arch/TribitsInternalPackageWriteConfigFile.cmake index 9d6691402..914825ffa 100644 --- a/tribits/core/package_arch/TribitsInternalPackageWriteConfigFile.cmake +++ b/tribits/core/package_arch/TribitsInternalPackageWriteConfigFile.cmake @@ -289,26 +289,6 @@ function(tribits_generate_package_config_file_for_install_tree packageName) set(EXPORT_FILE_VAR_PREFIX ${packageName}) endif() - # Set the include and library directories relative to the location - # at which the ${PROJECT_NAME}Config.cmake file is going to be - # installed. Note the variable reference below is escaped so it - # won't be replaced until a client project attempts to locate - # directories using the installed config file. This is to deal with - # installers that allow relocation of the install tree at *install* - # time. - # The export files are typically installed in - # //cmake//. - # The relative path to the installation dir is hence k*(../) + ../../, where - # k is the number of components in . Extract those here. - # This doesn't work if ${${PROJECT_NAME}_INSTALL_LIB_DIR} contains "./" or - # "../" components, but really, it never did. All of this should actually be - # handled by CMake's configure_package_config_file(). - string(REPLACE "/" ";" PATH_LIST ${${PROJECT_NAME}_INSTALL_LIB_DIR}) - set(RELATIVE_PATH "../..") - foreach(PATH ${PATH_LIST}) - set(RELATIVE_PATH "${RELATIVE_PATH}/..") - endforeach() - # Custom code in configuration file. set(PACKAGE_CONFIG_CODE "")