Summary: | "Build directory" not saved | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Sylvain Joyeux <doudou> |
Component: | Build tools: Automake | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Sylvain Joyeux
2003-06-13 17:34:00 UTC
You are not suposed to blank that directory! You should NOT mix your configurations! If you have two configurations outputing .o files to the project root, ALL HELL BREAKS LOOSE! Your debug files will be mixed with the optimized ones and so on! That is why that field sould never be blank and all your build directories _have_ _to_ _be_ different directories. Please close this bug if you understood or agree with me. If not, comment my opinon. Subject: Re: "Build directory" not saved In this case, I definitely think it should be better to explain that when we create new configurations. The first time I did it, I was unable to use the new configurations because the default one was already built. It's very annoying. Thank you. -- Sylvain Joyeux Subject: kdevelop/parts/autoproject CVS commit by aclu: Warn the user to not mess build directories. Fix: http://bugs.kde.org/show_bug.cgi?id=59730 CCMAIL: 59730-done@bugs.kde.org M +1 -1 configureoptionswidgetbase.ui 1.13 --- kdevelop/parts/autoproject/configureoptionswidgetbase.ui #1.12:1.13 @@ -177,5 +177,5 @@ </property> <property name="text"> - <string>&Build directory:</string> + <string>&Build directory (must be different for every different Configuration):</string> </property> <property name="buddy" stdset="0"> |