Home/ Questions/Q 741023
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T08:35:04+00:00

We are moving from hand-managed Visual Studio projects to cross platform cmake. We used

  • 0

We are moving from hand-managed Visual Studio projects to cross platform cmake.

We used to open a solutions file, select a project as “Startup Target” and push Ctrl+F5 or F5 debug or run.

Now cmake has this install concept. It requires me to run the install target. But the install project doesn’t have any executables set so it can not be used to start with debugging.

If I set my executable project as a startup target, then install will not run, so I can not debug.

I am sure there is a better way of doing this.

Any ideas ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should only need to run the INSTALL target if you want to distribute your application. If you select a project that builds an executable (so it has a ADD_EXECUTABLE statement in the CMakeLists.txt file) it should run with F5 or Ctrl+F5.

    It could be that you executable requires shared libraries which are build in a seperate directory. You can force all executables and libraries to be build in the same directory with the following CMake commands in your main CMakeLists.txt file.

       SET(LIBRARY_OUTPUT_PATH ${CMAKE_BINARY_DIR}/Bin/${CMAKE_BUILD_TYPE} CACHE PATH "Library output path")
   SET(EXECUTABLE_OUTPUT_PATH ${CMAKE_BINARY_DIR}/Bin/${CMAKE_BUILD_TYPE} CACHE PATH "Executable output path")

    If you want more control over the command that should be run when debugging have a look at this question: How to Set Path Environment Variable using CMake and Visual Studio to Run Test

    • 0