如何在Rcpp的Makevars中调用CMake获取系统库头文件与静态库路径

Since you can't replace Rcpp's build system but need dynamic path resolution from CMake for your P library, here are two reliable methods to pull the header (HF) and static library (SL) paths into your RP/src/Makevars:

Method 1: Direct CMake Command-Line Lookup (Simplest) #

CMake includes built-in command-line utilities for finding paths, which you can call directly from Makevars to fetch the required paths without writing a separate CMake script.

Update your RP/src/Makevars with these lines:

# Use CMake's find_path to locate your P library's header directory (HF)
P_INC := $(shell cmake -E find_path P_INCLUDE_DIR "p_core.h" /usr/local/include /usr/include)

# Use CMake's find_library to locate the static library (SL)
P_LIB := $(shell cmake -E find_library P_STATIC_LIB "libp.a" /usr/local/lib /usr/lib)

# Inject the paths into Rcpp's build flags
PKG_CPPFLAGS += -I$(P_INC)
PKG_LIBS += $(P_LIB)

Notes for Method 1: #

• Replace "p_core.h" with a representative header file from your P library's HF collection.
• Add more paths to the lookup (e.g., /opt/local/include) if your deployment environments install libraries in non-standard locations.
• If your P library installs a PConfig.cmake file (standard for CMake-built packages), simplify further using CMake's built-in package lookup:

  # Fetch paths directly from P's CMake config file (more robust)
  P_INC := $(shell cmake -E find_package P REQUIRED QUIET --variable INCLUDE_DIRS)
  P_LIB := $(shell cmake -E find_package P REQUIRED QUIET --variable LIBRARIES)
  

  This uses the exact paths P registered during installation, avoiding manual path guesswork.

Method 2: CMake Script to Generate a Makefile Fragment (More Flexible) #

For complex setups (e.g., multiple dependencies, custom compile flags), create a small CMake script that generates a Makefile snippet with resolved paths, then include that snippet in your Makevars.

Step 1: Create a CMake script (e.g., RP/cmake_config.cmake) #

# Find P's header directory and static library
find_path(P_INCLUDE_DIR NAMES "p_core.h" PATHS /usr/local/include /usr/include)
find_library(P_STATIC_LIB NAMES "libp.a" PATHS /usr/local/lib /usr/lib)

# Generate a Makefile fragment with the resolved variables
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/p_paths.mk" "
P_INC = ${P_INCLUDE_DIR}
P_LIB = ${P_STATIC_LIB}
")

Step 2: Update RP/src/Makevars to use the generated fragment #

# Define paths to the CMake script and output fragment
CMAKE_SCRIPT := ../cmake_config.cmake
P_PATHS_MK := ../p_paths.mk

# Regenerate the fragment only if the script changes or it doesn't exist
$(P_PATHS_MK): $(CMAKE_SCRIPT)
	cmake -P $(CMAKE_SCRIPT)

# Include the generated paths
include $(P_PATHS_MK)

# Apply paths to Rcpp's build flags
PKG_CPPFLAGS += -I$(P_INC)
PKG_LIBS += $(P_LIB)

Notes for Method 2: #

• This method caches resolved paths, so CMake only runs when the script is modified or the fragment is missing, speeding up subsequent builds.
• You can extend the CMake script to handle additional dependencies (like your NLOPT example) by adding more find_path/find_library calls and including their paths in the generated p_paths.mk.

Key Considerations #

• Deployment Consistency: Since your environments all have CMake and required libraries installed, you don't need fallback logic, but adding default paths ensures compatibility across standard setups.
• Static Linking: Ensure P_LIB points directly to the static library file (e.g., libp.a) rather than just the library directory—Rcpp's PKG_LIBS expects full paths for static linking.
• Debugging: Add debug echoes in Makevars (e.g., $(info P_INC is $(P_INC))) to verify path resolution works across all your deployment environments.

内容的提问来源于stack exchange，提问作者vkubicki