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

List:       kdevelop-bugs
Subject:    [Bug 102706] Cannot add files to/remove files from project correctly if the project is opened by a s
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-04-01 3:21:40
Message-ID: 20050401032140.12267.qmail () ktown ! kde ! org
[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=102706         




------- Additional Comments From gaoj cpsc ucalgary ca  2005-04-01 05:21 -------
These days I found this problem is not so "simple" as not knowing symbolic linked \
path, but seems more complicated (on FreeBSD).

Firstly, for the symbolic linked path, kdevelop actually uses real path except for \
the home directory of a user. I found that if a symbolic linked directory is outside \
of my home directry, e.g. in /tmp, kdevelop will use the actual real path of that \
project directory. But unfortunately, for things inside a user's home directory, \
kdevelop always use $HOME to substitute the leading path in its config file. And in \
my case, $HOME is "/home/user" but it actually is /usr/home/user. This is the reason \
why m_projectDirectory is different from all project files' prefix.

Secondly, even when opening a project is free from the $HOME confusion above, it \
still has problems adding files to the project. Files in the root directory of a \
project are OK. But for a file in some subdirectory in the project directory, no \
matter how deep it is, adding it only got a basename of the file in the \
.kdevelop.filelist file. The prefix relative to the project directory is ripped. I \
don't know how this should happen, because on a Linux system the kdevelop works fine \
without such problems.


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