Bug 75666 - changing the configuration causes problems
Summary: changing the configuration causes problems
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: 3.0.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-20 01:17 UTC by Sven Schmidt
Modified: 2007-11-30 18:30 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 Sven Schmidt 2004-02-20 01:17:08 UTC 
Version:            (using KDE KDE 3.1.4)
Compiler:          gcc 3.3.1 (SuSE 9.0) 
OS:          Linux

kdev 3.0.1, IDEAL, simple c++ project

Trying to do a whole rebuild after changing the configuration, say from "default" to "debug" or "optimized" will cause problems.
A "make" will finish with error code 1 or 2.


Regards, Sven Schmidt
Comment 1 Jens Dagerbo 2004-02-20 01:37:49 UTC 
Yes, this is true. I'm not sure it can be dealt with easily though. The build system at the bottom (in this case) is automake, after all, and there is a clear limit to what it allows us to do.

I guess, one way of doing it would to disallow the choosing of 'default' if the project has been configured once to use something other than 'default', and vice versa. This would clearly be both messy and confusing however.
Comment 2 Amilcar do Carmo Lucas 2004-02-20 09:19:30 UTC 
Teatime I tryed that. Seams there is no easy way of disabling default :(
Comment 3 Bernd Pol 2004-02-20 11:06:13 UTC 
Can't we at least produce a warning popup whenever the user selects default when debug and/or optimize is present?
So at least the unwaring or necomer won't loose work.

Bernd
Comment 4 Amilcar do Carmo Lucas 2005-04-12 10:57:14 UTC 
This is now covered in the FAQ, and a workaround is presented there.
Comment 5 Andreas Pakulat 2007-01-14 23:06:39 UTC 
*** Bug 75665 has been marked as a duplicate of this bug. ***
Comment 6 Andreas Pakulat 2007-11-30 18:30:10 UTC 
This is "fixed" as far as we can fix it. If somebody disagree's I'm happy to re-open and close as wontfix.