| Summary: | kdevelop does not respect EXECUTABLE_OUTPUT_PATH for launch configurations | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Benjamin Schindler <beschindler> |
| Component: | Build tools: CMake | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aleixpol, eugene.shalygin+bugzilla.kde, kitts.mailinglists |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Same for set_target_properties(bla-bla PROPERTIES RUNTIME_OUTPUT_DIRECTORY some_dir) Since newer cmake versions, there are other variables now: - Target properties: LIBRARY_OUTPUT)DIRECTORY, RUNTIME_OUTPUT_DIRECTORY and ARCHIVE_DIRECTORY - Global Variables: CMAKE_LIBRARY_OUTPUT_DIRECTORY, CMAKE_RUNTIME_OUTPUT_DIRECTORY + CMAKE_ARCHIVE_OUTPUT_DIRECTORY The old EXECUTABLE_OUTPUT_PATH are deprecated afaict I thought I fixed that. I'll give it another look. Thanks! Hmm... it seems you are right. At least in the case of CMAKE_RUNTIME_OUTPUT_DIRECTORY, it works here. I cannot test EXECUTABLE_OUTPUT_DIRECTORY or the target_properties. I think support for target_properties is missing as a whole, so this bug should stay open until that is fixed Cheers Benjamin It's not missing as a whole, could you send me a little example that I can use to work on? That would make the solving easier. Git commit ea6db89fbff42a2d6ec1435b0baa7304b6c73c17 by Aleix Pol. Committed on 02/12/2011 at 20:09. Pushed by apol into branch 'master'. Fix integration with custom output paths in CMake. BUG: 232447 M +13 -7 projectmanagers/cmake/cmakemanager.cpp http://commits.kde.org/kdevelop/ea6db89fbff42a2d6ec1435b0baa7304b6c73c17 |
Version: svn (using KDE 4.4.1) OS: Linux Installed from: Gentoo Packages Let me describe my project layout: CMake/VisdomUtils.cmake CMakeLists.txt utils/core/main/CMakeLists.txt - The root CMakeLists first includes VisdomUtils. It sets EXECUTABLE_OUTPUT_PATH to ${BIN_PATH}/bin - It then includes utils/core/main/CMakeLists.txt using subdirectory - utils/core/main/CMakeLists.txt adds an executable using ADD_EXECUTABLE When I go to the launch configuration, I add a new launch configuration: core/main/main When I execute I get this: Could not start program '/home/benjamin/software/visdom/build/core/main/main'. Make sure that the path is specified correctly.