CMAKE_CFG_INTDIR.rst 1.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. CMAKE_CFG_INTDIR
  2. ----------------
  3. Build-time reference to per-configuration output subdirectory.
  4. For native build systems supporting multiple configurations in the
  5. build tree (such as :ref:`Visual Studio Generators` and :generator:`Xcode`),
  6. the value is a reference to a build-time variable specifying the name
  7. of the per-configuration output subdirectory. On :ref:`Makefile Generators`
  8. this evaluates to `.` because there is only one configuration in a build tree.
  9. Example values:
  10. ::
  11. $(ConfigurationName) = Visual Studio 8, 9
  12. $(Configuration) = Visual Studio 10
  13. $(CONFIGURATION) = Xcode
  14. . = Make-based tools
  15. Since these values are evaluated by the native build system, this
  16. variable is suitable only for use in command lines that will be
  17. evaluated at build time. Example of intended usage:
  18. ::
  19. add_executable(mytool mytool.c)
  20. add_custom_command(
  21. OUTPUT out.txt
  22. COMMAND ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool
  23. ${CMAKE_CURRENT_SOURCE_DIR}/in.txt out.txt
  24. DEPENDS mytool in.txt
  25. )
  26. add_custom_target(drive ALL DEPENDS out.txt)
  27. Note that ``CMAKE_CFG_INTDIR`` is no longer necessary for this purpose but
  28. has been left for compatibility with existing projects. Instead
  29. :command:`add_custom_command` recognizes executable target names in its
  30. ``COMMAND`` option, so
  31. ``${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}/mytool`` can be replaced
  32. by just ``mytool``.
  33. This variable is read-only. Setting it is undefined behavior. In
  34. multi-configuration build systems the value of this variable is passed
  35. as the value of preprocessor symbol ``CMAKE_INTDIR`` to the compilation
  36. of all source files.