Bug 457790

Summary: Need non-root Makefile for importing new project
Product: [Applications] kdevelop Reporter: Aaron Williams <aaronw>
Component: Session supportAssignee: kdevelop-bugs-null
Status: REPORTED ---    
Severity: normal CC: igorkuo
Priority: NOR    
Version First Reported In: 5.8.220403   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Aaron Williams 2022-08-12 08:56:43 UTC
SUMMARY
I have a code base where the Makefile is not in the root project directory, or for that matter named Makefile.
It would be useful if I could manually assign the project root directory to be separate from where the base Makefile is located.

While there appears to be an option to change this, it does not seem to work. Every time I want to select a file, it starts at the Makefile location which does not include the tree.  In addition, it cannot pick up the actual file locations.
The only way I have found to get around this is to create a symbolic link named Makefile in the project root directory to the actual Makefile, which breaks things since the Makefile assumes it's in a different location.

STEPS TO REPRODUCE
1.  Import a new project where the base Makefile is not in the project root directory
2. Attempt to work with the project.
3. 

OBSERVED RESULT
The project is not imported because the Makefile is not in the project root. None of the .cpp/.h files are picked up.

EXPECTED RESULT
I expect to be able to override where the root folder is when importing from a Makefile.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Igor Kushnir 2022-08-13 12:18:32 UTC
I remember creating a separate dummy project without a build system as a workaround for this issue.