[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-29 13:12:22
Message-ID: 20080929131222.4EB5E12F8D () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #14 from Martin Gebert <murphy gebert gmx de>  2008-09-29 15:12:18 ---
> taking relative paths led to a myriad of problems for users.

That's what I figured from the discussion above :-( I would have suggested that
resolving the paths would be handled the following way, but I presume you've
already thought of that:

1. When getting a path, either entered manually, from a config file or from the
file/dir dialog, always make it a realpath (absolute, canonical; compare man 3
realpath).
2. Realpaths located within the project dir will be stored as relative paths
("relative to project file").
3. All others will be stored as absolute paths.

> the gdb-configurations weren't changed and should still allow to put just a "name" \
> of the executable there

That's probably not the problem I described above; just putting "<arch>-gdb" as
GDB executable is allright when it is found in $PATH. However the config script
for GDB (the one containing "target remote <IP>..." which is executed by GDB on
startup) is searched from within the working dir of GDB, which has become $HOME
with 3.5.3, while I was able to define a relative path "../../remoteGdb.conf",
starting from the main app working dir (containing my app executable) and
finding the file in the project dir, in previous versions. I just tried,
providing the relative path starting at $HOME works allright, but doesn't solve
my issue...


-- 
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]