Summary: | allow specifying that subprojects can inherit includes from higher levels | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Jay <joerg> |
Component: | Build tools: Automake | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 4.0.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jay
2003-03-09 11:33:12 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. 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 not a bug, but definitely something that we could implement in the future |