From kdevelop-bugs  Tue Mar 29 01:36:56 2005
From: kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date: Tue, 29 Mar 2005 01:36:56 +0000
To: kdevelop-bugs
Subject: [Bug 102706] New: Cannot add files to/remove files from project correctly if the project is opened b
Message-Id: <20050329033654.102706.gaoj () cpsc ! ucalgary ! ca>
X-MARC-Message: https://marc.info/?l=kdevelop-bugs&m=118306935706869

------- 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         
           Summary: Cannot add files to/remove files from project correctly
                    if the project is opened by a symbolic-linked path
           Product: kdevelop
           Version: unspecified
          Platform: FreeBSD Ports
        OS/Version: FreeBSD
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: gaoj cpsc ucalgary ca


Version:           kdevelop-3.2 (using KDE KDE 3.4.0)
Installed from:    FreeBSD Ports
Compiler:          gcc version 3.4.2 [FreeBSD] 20040728 
OS:                FreeBSD

If a project is opened by a symbolic-linked path, the add file to/remove file from project functionality will not work correctly.

Example:

/home is a symbolic link to /usr/home (this is likely be the case on FreeBSDs). And a project is in /usr/home/user/foobar/ , with the project file /usr/home/user/foobar/foobar.kdevelop .

If you use kdevelop to open /home/user/foobar/foobar.kdevelop , you will open the project. But whenever you try to add a file to the project, or remove a file from the project by the File Tree, you will find nothing will happen. And actually, in the case of adding a file, a line with the absolute path name of the file is put into foobar.kdevelop.filelist  (/usr/home/user/foobar/somefile.c). But the supposed behaviour is to put a file path name relative to the project directory.

I have tried to add some output in customprojectpart.cpp, and found that in the above case, m_projectDirectory is the symbolic-linked path: /home/user/foobar, while the project files populated in the project all have absolute path like: /usr/home/user/foobar/....

I also tried, if open the project by /usr/home/user/foobar/foobar.kdevelop, everything works fine.

So in kdevelop, while opening a project, it should try to resolve an absolute path for the project, instead of using what is given. (Or it can figure out the equivalence of a symbolic-linked and non-symbolic-linked path.)

Note: This is somewhat similar to bug 98852 but actually not the same.