Bug 71675

Summary: "No makefile in this directory" detection is too conservative.
Product: [Applications] kdevelop Reporter: Kuba Ober <kuba>
Component: Build tools: AutomakeAssignee: kdevelop-bugs-null
Severity: wishlist CC: kbugger, mattr
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Kuba Ober 2004-01-02 14:30:06 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.2.2 
OS:          Linux

The "There's no makefile in this directory" popup invoked from Project/Build isn't too intelligent if the make command has the file argument set, say as in make -f Makefile.linux

The "missing makefile" detection should look for "-f" argument to make and either take the name of the file from make's command line as specified in the Project/Build dialog.

The check should either be removed, or fixed.

Workaround: touch Makefile in correct directory, but that's really a long shot :)
Comment 1 Kuba Ober 2004-01-02 14:31:31 UTC
This bug is related to bug 71594 which is invalid per se as the arguments to the make command *can* be set.
Comment 2 Jon Smirl 2004-01-04 01:29:30 UTC
It might be simpler to add a field to Project Options/Build Option/Make for the name of the makefile. Then the missing makefile logic could be left alone and just modified to use the name given in the dialog. This would avoid the need for parsing the command line.

The project I am working on uses 'make -f Makefile.linux' this makefile then uses a script to dynamically build 'Makefile'. The project is crossplatform so there are scripts for various platforms.
Comment 3 Jens Dagerbo 2007-01-05 18:52:24 UTC
*** Bug 135197 has been marked as a duplicate of this bug. ***
Comment 4 Andreas Pakulat 2008-07-05 20:58:48 UTC
this is actually a wish not a bug.