[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 99361] New: cleaned customproject not rebuild before execution
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-02-14 14:16:47
Message-ID: 20050214151645.99361.daniel.franke () imbs ! uni-luebeck ! de
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=99361         
           Summary: cleaned customproject not rebuild before execution
           Product: kdevelop
           Version: 3.1.92
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: daniel.franke imbs uni-luebeck de


Version:           3.1.92 (using KDE KDE 3.3.92)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3 
OS:                Linux

Generic C++ Application (Custom Makefiles):

I don't have dependency tracking in my Makefiles, so if I change any header, I've to \
recompile anything that includes them.

 * change header
 * Build -> Build Project
   (assume no effect without dependency tracking)
 * Build -> Clean Project
   (no more changes in sources)
 * Build -> Execute Program

Assumed behaviour: the executeable should be built, then run
Actual behaviour:  kdevelop attempts to execute the (non-existant) binary

If there are changes after the 'clean' and before the 'run', then the binary is \
rebuilt before execution.

Conclusion: kdevelop should check whether the binary it will try to execute is \
available (and not, e.g. cleaned away), if not, it should be built.


[prev in list] [next in list] [prev in thread] [next in thread]