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

List:       kdevelop-bugs
Subject:    [Bug 110479] headers in noinst /  install
From:       Jens Dagerbo <jens.dagerbo () swipnet ! se>
Date:       2007-01-06 7:55:58
Message-ID: 20070106075558.5986.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=110479         
jens.dagerbo swipnet se changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From jens.dagerbo swipnet se  2007-01-06 08:55 -------
Hmm.. I think this works reasonably well. 

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.

Most of the time, you don't want to list the header file in the Makefile.am, so \
defaulting to "headers in noinst" creates the least bit of work for the user for the \
typical use case. If you want the header to be listed in install (or some other \
target) it is, as you say, just a matter of adding it to that target. The next time \
you load the project, the header will then only appear in the install target, not in \
the noinst target.

Yes, it would be slightly nicer if the header was removed from noinst when you added \
it somewhere else, but this would be inconsistent with other targets and adds further \
complexity to the AM. I simply doubt we want to do this for such a minor gain. \
WONTFIX.


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