Bug 70839 - automake manager: remove files from 'Header in noinst' doesn't work ?!
Summary: automake manager: remove files from 'Header in noinst' doesn't work ?!
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: 3.0.0b2
Platform: Compiled Sources Solaris
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-19 14:30 UTC by Daniel Franke
Modified: 2007-01-07 04:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Franke 2003-12-19 14:30:40 UTC 
Version:           3.0.0b2 (using KDE 3.1.4)
Installed from:    compiled sources
Compiler:          gcc version 3.2.2
OS:          SunOS (sun4u) release 5.8

Current CVS (2003/12/19):

When removing files from a target in automake (trash.cpp, trash.h, both still on disk) the classes they implement are instantly removed, as expected, from list in class tool.

Next update of class tool: trash-classes are listed again.
This holds also when closing and reopening the project.

At first I was confused by this behaviour. Then I found that 'trash.h' reappeared in 'Header in noinst' target of automake manager.

Please note:
'trash.h' is NOT listed in noinst_HEADERS target in 'Automake.am' any more - but nevertheless appears in automake manager ?!?
Comment 1 Amilcar do Carmo Lucas 2004-01-06 18:03:05 UTC 
AFAIK this noinst_HEADERS stuff in the AM was introduced for the cppparser.
Just ignore it! It doesn't hurt you.
Comment 2 Daniel Franke 2004-01-06 18:15:44 UTC 
Ok, i don't mind those NOIST headers, nevertheless classes no longer in project litter the class-view. Intended?
Comment 3 Amilcar do Carmo Lucas 2004-01-06 18:29:23 UTC 
No, not intended.
For now the only solution I see is to rename or delete the files using konqueror
Comment 4 Daniel Franke 2005-01-14 13:44:28 UTC 
Still valid in kdevelop-3.1.91, KDE-3.3.91, CVS 050113
Comment 5 Amilcar do Carmo Lucas 2005-01-14 14:35:51 UTC 
Daniel seams to be a very good user. I trush him.
Comment 6 Jens Dagerbo 2007-01-07 04:56:12 UTC 
I think this will have to remain as it is.

The "headers in no-inst" is a pseudo-target that the Automake Manager uses in order to keep track of header files that are not in any other way listed in any Makefile.am file. This is done to have those files also "part of the project" which is needed, among other things, for the language parser to be aware of them. Since they are not listed anywhere, the automake manager simply looks in the directory and assumes that if they are there, they are interesting.

A workaround would either need a metadata file that lists "blacklisted" files only for the purpose of not showing them in the project while letting them remain in the directory.. or a redesign of the whole idea.. Complexity for marginal utility. 

KDevelop4 will probably parse headers straight from the #include statements, so this system shouldn't need to exist there.

IMHO, WONTFIX.

See also bug #110479