开发者

How to create a C #define for a certain target using CMake?

开发者 https://www.devze.com 2023-02-17 11:47 出处:网络
I feel a little stupid right now. After recently converting a few smaller projects to use CMake, I decided to also get rid of a few \"Platfor开发者_JS百科m_Config.h\" files. These files contain a few

I feel a little stupid right now. After recently converting a few smaller projects to use CMake, I decided to also get rid of a few "Platfor开发者_JS百科m_Config.h" files. These files contain a few preprocessing directives like #define USE_NEW_CACHE and control compilation.

How would I 'convert' these defines to be controlled with CMake? Ideally by using these "cache" variables the user can easily edit.


There are two options. You can use the add_definitions method to pass defines as compiler flags: E.g. somewhere in your projects cmakelists.txt:

add_definitions( -DUSE_NEW_CACHE )

CMake will make sure the -D prefix is converted to the right flag for your compiler (/D for msvc and -D for gcc).

Alternatively, check out configure_file. It is more complex, but may be better suited to your original approach with a Platform_Config file.

You can create an input-file, similar to your original Platform_Config.h and add "#cmakedefine" lines to it.

Let's call in Platform_Config.h.in:

// In Platform_Config.h.in
#cmakedefine USE_NEW_CACHE
// end of Platform_Config.h.in

When then running

configure_file( ${CMAKE_SOURCE_DIR}/Platform_Config.h.in ${CMAKE_BINARY_DIR}/common/Platform_Config.h )

it will generate a new Platform_Config file in your build-dir. Those variables in cmake which are also a cmakedefine will be present in the generated file, the other ones will be commented out or undefed.

Of course, you should make sure the actual, generated file is then correctly found when including it in your source files.


option command might provide what you are looking for.
use it with the COMPILE DEFINITIONS property on the target and i think you are done. To set the property on the target, use the command set target properties

option(DEBUGPRINTS "Prints a lot of debug prints")
target(myProgram ...)
if(DEBUGPRINTS)
set_target_properties(myProgram PROPERTIES COMPILE_DEFINITIONS "DEBUGPRINTS=1")
endif()

edit:

The option i wrote in the example shows up as a checkbox in the CMake GUI.


In case you want to set defines per target: Since 2.8.11 you can use target_compile_definitions.

In earlier versions you probably don't want to use set_target_properties as is, since it overwrites any defines you set previously. Call get_target_property first instead, then merge with previous values. See add_target_definitions here.


Use target_compile_options. Do not quote your define or it not be detected as a define. CMake parses off the /define and adds the actual define to the DefineConstants section of the csproj, if there are quotes it will put the entire quoted string in the AdditionalOptions section of the csproj.

An example from one of my projects that uses generator expressions:

target_compile_options( ${LIBRARY_NAME} PRIVATE
    $<${IS_ART_ITERATION_BUILD}:/define:ART_ITERATION_BUILD>
)

An example without generator expressions:

target_compile_options( ${LIBRARY_NAME} PRIVATE
    /define:GRAPHICS_VULKAN
)
0

精彩评论

暂无评论...
验证码 换一张
取 消