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

List:       kdevelop-bugs
Subject:    [Bug 143389] Custom Project: Do NOT overwrite relative path to
From:       Martin Gebert <murphy.gebert () gmx ! de>
Date:       2008-09-30 12:56:55
Message-ID: 20080930125655.BD3FB130AF () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=143389





--- Comment #18 from Martin Gebert <murphy gebert gmx de>  2008-09-30 14:56:53 ---
Hi Andreas,

> KDevelop doesn't set the "current working directory" since I think 3.5.0 anymore itself

I just checked with 3.5.2; it shows the same behaviour as 3.5.3, so there's
indeed no change. Must have been some 3.4 version since setting a GDB config
script with relative path has worked.

Another thought just occurred to me: When setting a main application or working
dir with an absolute path (under Runtime options) within one of the build
configuration dirs (e. g. "debug"), the path to it wouldn't be changed when I
change the build configuration, would it? However this is necessary to run an
app that isn't the default subproject to automake, AFAIK. So setting these
paths as relative (as I did all the time with this current project) is the only
way I know to avoid being forced to change them every time I want to run my app
from another build config...


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]