Bug 55735 - allow specifying that subprojects can inherit includes from higher levels
Summary: allow specifying that subprojects can inherit includes from higher levels
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: 4.0.0
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-09 11:33 UTC by Jay
Modified: 2009-01-24 01:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jay 2003-03-09 11:33:12 UTC
Version:           Gideon CVS (using KDE KDE 3.1)
Installed from:    Gentoo Packages

In automake projects, when I set internal or external includes for the topproject, no subproject inherits the includes. Instead, I have to set them for each subproject individually.
Comment 1 Jens Dagerbo 2003-10-28 00:02:52 UTC
Is this a bug? 

Is it unthinkable that two sets of include flags are mutually exclusive? If that isn't the case, I don't see how "inheriting" include flags from the top project can be done safely.
Comment 2 Jay 2003-10-28 00:38:17 UTC
Subject: Re:  autoproject: extra include dirs not inherited by subprojects

If it's intended, it's a usability bug maybe. My project makes use of 
auxiliary libraries which I don't have installed in the usual /usr/include 
path PLUS the project consists of a lot of subdirectories which all need 
these includefiles. For sure it can be possible that a topfolder needs 
includes the subfolders don't, but then I think there is a need to make 
inheritance optional ( like you can optionally assign new filepermissions in 
subdirectories, too, in konqueror ).

Regards,
J
Comment 3 Matt Rogers 2005-10-20 02:41:01 UTC
not a bug, but definitely something that we could implement in the future