Bug 39797 - specifying make instead of gmake does not create an executable with the name i specify
Summary: specifying make instead of gmake does not create an executable with the name ...
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: kdevelop 2.x (obsolete) (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-25 23:48 UTC by vhytopoulos
Modified: 2003-07-23 19:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description vhytopoulos 2002-03-25 23:39:29 UTC 
(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           2.2.2-2 (using KDE 2.2.2 )
Severity:          normal
Installed from:    RedHat RPMs
Compiler:          form gcc -v:(Red Hat Linux 7.1 2.96-98)
OS:                Linux
OS/Compiler notes: Not Specified

In a previous version of kdevelop (I believe 1.4.2) I was specifying "make" under Options/Kdevelop setup/general/select make-command and a makefile in the same directory that my sources were and kdevelop would execute my makefile creating an executable with the name that I was specifying.  In the current version I have not been successful to repeat this behavior. If I specify the name of executable as "all" things work fine but then the debug option looks for an executable with the same name as the project and it fails.  If I manually rename things work but unless i am doing something wrong I would expect an executable with the name that I specify to be created.

Thank you very much

Vangelis

(Submitted via bugs.kde.org)
Comment 1 Caleb Tennis 2002-10-09 22:03:45 UTC 
This should work in Gideon (3.0).
Comment 2 Amilcar do Carmo Lucas 2003-07-23 19:07:07 UTC 
I'm pretty sure there was never a 2.2.2 release!