Bug 334943 - wrong working directory for CMake target
Summary: wrong working directory for CMake target
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.6.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-17 13:06 UTC by Barade
Modified: 2023-02-07 03:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barade 2014-05-17 13:06:40 UTC
I've created a Unit Test with the Boost Unit Testing Framework. The test is specified in CMakeLists.txt:
add_executable(rectanglestest rectanglestest.cpp ../implementation.cpp)
target_link_libraries(rectanglestest ${OpenCV_LIBS} ${Boost_LIBRARIES})
add_test(RectanglesTest rectanglestest)
configure_file(test.xcf test.xcf COPYONLY)
configure_file(test.png test.png COPYONLY)

when I add the executable "rectanglestest" under "Configure Launches ..." and do not specify the working directory it seems to run in the wrong working directory since it does not find the file "test.png". On the other hand when I run the Unit Test "RectanglesTest" using the Unit Test list in KDevelop it works properly. 

A executable launch called "CTest" is added automatically which uses the executable "rectanglestest" as well but not the test "RectanglesTest" which is wrong I think. The launch "CTest" does not find the file as well so the working dir seems to be wrong here, too.

Reproducible: Always
Comment 1 Andrew Crouthamel 2018-11-11 04:21:28 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:31:48 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-08 22:45:14 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-23 05:05:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-02-07 03:55:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!