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

List:       kdevelop-bugs
Subject:    [Bug 274712] New: No access to information about projects such as
From:       Wolfgang Bangerth <bangerth () dealii ! org>
Date:       2011-06-01 22:25:34
Message-ID: bug-274712-40295 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=274712

           Summary: No access to information about projects such as
                    include path resolutions
           Product: kdevelop
           Version: 4.2.1
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs@kdevelop.org
        ReportedBy: bangerth@dealii.org


Version:           4.2.1 (using KDE 4.6.0) 
OS:                Linux

Following up on a conversation on the mailing list and between myself and David
Nolden:
.........................................
>> [...] It seems like some of your
>> used headers are not found, which leads to a very reduced navigation-,
>> code-completion, and highlighting functionality. You should make sure
>> that the included headers are found, so that the screenshots will look
>> nicer, and you will get much more functionality regarding navigation,
>> code-completion, etc.
>>
>> To make sure that the headers are found, you can hover or right-click
>> a red-underlined missing header, and then add manual include paths.
>> (Or you can simply add a newline-separated ".kdev_include_paths" file
>> at the top of your project). This, by the way, is something that could
>> use some documentation too. :-)
>
> Ah, interesting.
>
> Before I put this into the documentation somewhere: Is there a dialog
> somewhere where this could be set? While playing, I've occasionally come
> across things like what you describe where you resolve a problem (a missing
> path to include files, or other stuff that's listed in the "Problems" tool
> view) but where there doesn't seem to be an associated dialog where one could
> have done this before the problem even appeared, or where one could undo a
> mistake. In other words, is it true that KDevelop stores information on
> projects that isn't presented in an editable form in a dialog box? If so, why?
>
> Thanks in advance for your help, and I'll be happy to put any answers into the
> manual as usual :-)
>  W.

No, there's no dialog for this, unfortunately. We could put it
somewhere into the project-configuration, but right now, it's simply a
context-sensitive helper to discover the .kdev_include_paths
functionality. Basically though, KDevelop should be able to discover
the correct include-paths automatically in many cases by using
information from the build-system (be it cmake or custom makefiles),
so the user shouldn't be bothered with this until he actually
discovers that it doesn't work.
.................................

Thinking of the complex mess every bigger project's Makefile is, I believe
that there are a good number of cases where it would be worthwhile to
enter this by hand into some dialog box, e.g. the "Project -> Open
configuration" dialog.

The primary reason to request this information, however, is so that one
can set up a project in a predictable way by simply entering all information
that is needed. Right now, if I want to help a colleague set up their project,
all information KDevelop shows in any accessible place may look the same, but
the outcome is different because of past actions (e.g. right clicking with
the mouse) that have been recorded but are not accessible. I find this awkward.

Best & thanks
 W.

Reproducible: Always

-- 
Configure bugmail: https://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]