cmake

问题 As a part of my build process I'm building the webserver lighttpd. The following CMakeLists.txt is working: include(ExternalProject) ExternalProject_Add( lighttpd URL ${PROJECT_SOURCE_DIR}/ext/lighttpd.tar.gz CMAKE_ARGS -DCMAKE_INSTALL_PREFIX=${EXTERNAL_OUTPUT_PATH}/lighttpd ) ExternalProject_Add_Step( lighttpd copy2bin COMMAND ${CMAKE_COMMAND} -E copy_directory ${EXTERNAL_OUTPUT_PATH}/lighttpd/sbin ${EXECUTABLE_OUTPUT_PATH} COMMAND ${CMAKE_COMMAND} -E copy_directory ${EXTERNAL_OUTPUT_PATH}

问题 As a part of my build process I'm building the webserver lighttpd. The following CMakeLists.txt is working: include(ExternalProject) ExternalProject_Add( lighttpd URL ${PROJECT_SOURCE_DIR}/ext/lighttpd.tar.gz CMAKE_ARGS -DCMAKE_INSTALL_PREFIX=${EXTERNAL_OUTPUT_PATH}/lighttpd ) ExternalProject_Add_Step( lighttpd copy2bin COMMAND ${CMAKE_COMMAND} -E copy_directory ${EXTERNAL_OUTPUT_PATH}/lighttpd/sbin ${EXECUTABLE_OUTPUT_PATH} COMMAND ${CMAKE_COMMAND} -E copy_directory ${EXTERNAL_OUTPUT_PATH}

问题 I would like to change CMAKE_C_COMPILER and CMAKE_CXX_COMPILER in an inner sub_directory being compiled as part of a bigger project. changing from GNU to intel compiler. however, outside of this directory nothing has to chagne. is that possible? Thanks 回答1: Instead of using add_subdirectory consider making the subdirectory a self-contained CMake project, which can be configured and built independently of the bigger project. You can then add the subdirectory to your bigger project as an

问题 I like to automate the cross compiling for several projects on a Windows build server. I have some problems with the arm cross compiler. Setting it up seems a bit difficult. The cmake compiler check fails with a linking error(see below). My experimental project looks like: main.cpp - a test programm CMakeLists.txt - the cmake build script cmake/STM32F2xx.cmake - the special settings for the ARM STM32F2xx-series I am using 3 Packages: cmake-3.8.0-win64-x64.msi -cmake for windows mingw-w64

问题 In Short: Is there any preferred naming convention for cmake library targets - in particular when using namespaces? Note: Unless there is really an objective reason for it, I'm not asking about personal preferences, but whether there is either an "official" (e.g. recommended by kitware) or established (which might deviate) convention. Details: Lets say I have a library/framework foo which has the individual components bar and baz . So far, my naming convention looks like this: add_library(foo

问题 In Short: Is there any preferred naming convention for cmake library targets - in particular when using namespaces? Note: Unless there is really an objective reason for it, I'm not asking about personal preferences, but whether there is either an "official" (e.g. recommended by kitware) or established (which might deviate) convention. Details: Lets say I have a library/framework foo which has the individual components bar and baz . So far, my naming convention looks like this: add_library(foo

问题 In Short: Is there any preferred naming convention for cmake library targets - in particular when using namespaces? Note: Unless there is really an objective reason for it, I'm not asking about personal preferences, but whether there is either an "official" (e.g. recommended by kitware) or established (which might deviate) convention. Details: Lets say I have a library/framework foo which has the individual components bar and baz . So far, my naming convention looks like this: add_library(foo

问题 I have the following CMakeLists.txt cmake_minimum_required(VERSION 3.12) project( project_360_visual ) find_package( OpenCV REQUIRED ) set(SOURCE_FILES ${CMAKE_SOURCE_DIR}/src/project_360_visual.cpp ${CMAKE_SOURCE_DIR}/src/projection.cpp) set(INCLUDE_FILES ${CMAKE_SOURCE_DIR}/include/project_360_visual.h ${CMAKE_SOURCE_DIR}/include/projection.h) LINK_DIRECTORIES(c:/opencv/build/bin/Release) add_library(opencv_tracking430 SHARED IMPORTED GLOBAL) set_target_properties(opencv_tracking430

问题 I'm trying to compile this code, but when running cmake .. in the build folder I get the messages: -- Looking for Fortran sgemm -- Looking for Fortran sgemm - not found -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE -- Looking for Fortran dgemm -- Looking for Fortran dgemm - found -- Found BLAS: /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System

问题 I was trying to use yaml-cpp in my project. It took me half an hour to correctly link the library by experimenting with the following names. After I finally stumbled across them in this file, I settled for this: find_package(yaml-cpp REQUIRED) include_directories(${YAML_INCLUDE_DIRS}) target_link_libraries(${YAML_CPP_LIBRARIES}) It works, but the way I was searching for those seems brainless. How is it remotely possible to figure out the correct name of the include variables? It could be YAML