Consider the following directory structure projectRoot/ projectRoot/projectName.kdev4 projectRoot/build/ projectRoot/build/linux/ projectRoot/build/Makefile projectRoot/src projectRoot/src/source1.cpp projectRoot/src/source2.cpp With Kdevelop <= 4.5 I could configure a Custom Makefile Project to build using the -C option by setting 'Additional make options' in the Projects's Configuration. Additional make options: "-C build/linux" Everything worked find, make ran, and clicking in every error or warning shown in the 'Built Tool View' linked me to the file and line of interest. ../../src/source.cpp:111 ..... But starting with Kdevelop 4.6 this doesn't work anymore, the file path is resolved from project's root instead of the directory where the Makefile is located. Reproducible: Always Steps to Reproduce: 1. Create a project having the Makefile in a directory different than the project. 2. Compile and generate some error 3. Click on the Build Tool View Actual Results: The link points to unexistent (or at least incorrect) file. Expected Results: The link should point to the correct file I'm attaching a sample project that will throw some compilation errors. The workaround in this case is to add the sub-directory containing the Makefile to the buildset, getting ride of the -C option. But this worked before, maybe just digging into commit history could lead us to a solution?
Created attachment 84498 [details] Sample project Sample project as promised. Makefile is in the /linux directory Source file is in the /src directory
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!
Bug persists in 5.3.0.
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!
(In reply to Justin Zobel from comment #4) > 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! Still occurring in KDevelop 5.10 (KDE Neon 5.26)