为什么 CMake 设计为在安装时删除运行时路径

Why is CMake designed so that it removes runtime path when installing(为什么 CMake 设计为在安装时删除运行时路径)

本文介绍了为什么 CMake 设计为在安装时删除运行时路径的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我自己构建了我的共享库(例如我使用了一个计算斐波那契数的库),并希望在我的另一个由 CMake

I built my shared library(I use a lib calculating the fibonacci number for example) myself and want to use it in my another c++ project built by CMake

假设共享库和头文件位于 /path/to/my/lib,共享库 libfib.so 位于 /path/to/my/lib/lib 和标题 fib.h/path/to/my/lib/include 和我自己的项目位于 >/path/to/my/project

Let's say the shared library and headers located in /path/to/my/lib, the shared library libfib.so is in /path/to/my/lib/lib and the header fib.h is in /path/to/my/lib/include and my own project located in /path/to/my/project

这是我原来的CMakeLists.txt:

cmake_minimum_required(VERSION 3.2)
project(learn-lib)
set(CMAKE_CXX_FLAGS "-std=c++11 ${CMAKE_CXX_FLAGS}")
set(FIB_INCLUDE "${FIB_PREFIX}/include")
set(FIB_LIB "${FIB_PREFIX}/lib")
set(EXE mybin)
include_directories(${FIB_INCLUDE})
link_directories(${FIB_LIB})
add_executable(${EXE} main.cpp)
target_link_libraries(${EXE} fib)
install(TARGETS ${EXE} RUNTIME DESTINATION bin)

我使用这个脚本来构建和安装我的项目:

And I use this script to build and install my project:

mkdir -p build_dir
cd build_dir
cmake -DFIB_PREFIX=/path/to/my/lib 
      -DCMAKE_INSTALL_PREFIX=/path/to/my/project 
      ..
make
make install
cd ..

现在,在运行安装脚本后,我得到了两个可执行文件,一个在 build_dir 中,一个在安装位置 path/to/my/project/bin 中,当在 build_dir 中运行程序,一切正常,但是在运行已安装的程序时,我得到:

Now, after running the install script, I got two executables, one in build_dir, one in the install location path/to/my/project/bin, when running the program in build_dir, everything is fine, but when running the installed program, I get:

./bin/mybin:加载共享库时出错:libfib.so:无法打开共享对象文件:没有这样的文件或目录

./bin/mybin: error while loading shared libraries: libfib.so: cannot open shared object file: No such file or directory

在 google 和 stackoverflow 上进行一些搜索后,我知道 CMake 似乎删除了构建时与可执行文件相关联的运行时搜索路径.我现在知道两种解决方法:

After some searching on google and stackoverflow, I knew it seems that CMake removed the runtime search path that is tied to the executable when building. I now know two ways to get it around:

  1. libfib.so所在的库路径添加到环境变量LD_LIBRARY_PATH
  2. set_target_properties(${EXE} PROPERTIES INSTALL_RPATH_USE_LINK_PATH TRUE) 添加到我的 CMakeLists.txt
  1. Add the library path where libfib.so locates to the environment variable LD_LIBRARY_PATH
  2. Add set_target_properties(${EXE} PROPERTIES INSTALL_RPATH_USE_LINK_PATH TRUE) into my CMakeLists.txt

所以,我的问题是:

  1. 为什么 CMake 是这样设计的?安装时,为什么要从可执行文件中删除运行时路径,而不是将构建的可执行文件复制到安装目标或保留已安装程序的链接路径的任何内容?
  2. 哪种方法是消除此问题的最佳做法(或是否有最佳做法)?设置环境或将 set_target_properties(...) 添加到 CMakeLists.txt 中?
  1. Why is CMake designed so? When installing, why would it remove runtime path from executables instead of just copying the built executables to the install destination or whatever keeping the link path for the installed program?
  2. Which way is the best practice(or is there a best practice) to eliminate this problem? To set the environment or to add set_target_properties(...) into CMakeLists.txt ?

推荐答案

您可能需要查看 CMake 的 RPATH 处理设置

这句话似乎与您的困境特别相关:

This quote in particular seems relevant to your predicament:

默认情况下,如果您不更改任何 RPATH 相关设置,CMake 会将具有完整 RPATH 的可执行文件和共享库链接到构建树中所有使用的库.安装时,会清除这些目标的 RPATH,以便安装时使用空的 RPATH.

By default if you don't change any RPATH related settings, CMake will link the executables and shared libraries with full RPATH to all used libraries in the build tree. When installing, it will clear the RPATH of these targets so they are installed with an empty RPATH.

您可以使用 CMAKE_INSTALL_RPATH 变量设置为已安装二进制文件设置的 RPATH,例如:

You can set the RPATH that is set for installed binaries using the CMAKE_INSTALL_RPATH variable, for example:

SET(CMAKE_INSTALL_RPATH "${CMAKE_INSTALL_PREFIX}/lib")

并且您还可以在安装过程中禁用 RPATH 剥离:

and you can also disable the RPATH stripping during installation:

SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE)

这篇关于为什么 CMake 设计为在安装时删除运行时路径的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本文标题为:为什么 CMake 设计为在安装时删除运行时路径

基础教程推荐