3 ms·
Is this a common problem? I can't think of any project that does this, and there's a simple solution as well: don't shadow system headers. That's just asking fo
by tedunangst 9y ago
Is this a common problem? I can't think of any project that does this, and there's a simple solution as well: don't shadow system headers. That's just asking for pain, regardless of how well make handles it.
- deleted 9y ago[deleted]
- tomjakubowski 9y agoI don't think this problem is limited to system headers. Something as innocent as #include "foo/bar.h" can be affected by this if you pass -I with at least two unique paths to the compiler.
- tedunangst 9y agook, sure, I revise my answer to don't shadow any header.
- tomjakubowski 9y agoEasier said than done, especially integrating over the lifetime of a years-long project with many ever-changing dependencies :-)