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

List:       kdevelop-bugs
Subject:    [Bug 139457] New: It is impossible to manually add files to a project
From:       Claus Wilke <wilke () spamcop ! net>
Date:       2007-01-01 1:34:01
Message-ID: 20070101023359.139457.wilke () spamcop ! net
[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=139457         
           Summary: It is impossible to manually add files to a project of
                    type "Generic C++  Application (Automake based)".
           Product: kdevelop
           Version: 3.3.4
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: wilke spamcop net


Version:           3.3.4 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17-10-generic

In an automake based project, it is impossible to manually add files to the project \
(in contrast to say the custom makefile based projects, where right-clicking on the \
File Tree has the option "add to project").

The reasoning why this option is missing is probably that KDevelop can figure out \
from the Makefiles which files are part of the project and which are not. The problem \
is that this process can fail. In a large real-world project, it is inevitable that \
there will be some pieces that are non-standard. For example, I have a large C++ \
project that also contains some python bindings. The python bindings use the python \
make structure, and KDevelop does not recognize the corresponding C++ files as part \
of the project.

Since it is important to have all source files being recognized by KDevelop as part \
of the project (for code completion, project-wide search/replace, etc.), I consider \
it a bug when I can't manually override KDevelop's incorrect choice of which files to \
include into the project.


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