[llvm-dev] Include all the things

[David Blaikie via llvm-dev]

On Wed, Dec 9, 2015 at 8:29 AM, Russell Wallace <russell.wallace at gmail.com>
wrote:

> On Wed, Dec 9, 2015 at 3:58 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>> That's really going to hurt your compile time, btw...
>>
>
> Right, though compile time isn't a bottleneck for me; in any case, I've
> seen it said that that clang can do precompiled headers, so I was going to
> try that.
>
>
>> if you're interested in building a tool to help here, a tool that uses
>> Clang to find and suggest headers to include (or to remove, to keep the
>> include set minimal to avoid bloating compile time) would probably be good
>> & I know there are some people working on such a thing. But it is more
>> work, of course. (& may benefit from/need C++ modules support)
>>
>
> Yeah, there is an 'include what you need' tool. I tried it a month or two
> ago, and it didn't quite work, but came impressively close, closer than I
> expected.
>
> The second is probably because you're including a header that's only
>> conditionally usable, when you have the right 3rd party package installed
>> (at least I assume that's the case - Zach?)
>>
>> Did we actually install that header onto a system without the package
>> available? Or are you pointing your build at an LLVM source tree?
>>
>
> I'm on Windows, so package management doesn't apply;
>

Sorry, perhaps a poor use of terms on my part - it still matters in the
sense that LLVM has external library dependencies you may need to have
installed, etc.


> I'm using the 3.7.0 source tarball, so probably closer to the latter than
> the former.
>

OK - yeah, not sure (perhaps Zach can help here, then) - you may need to
install some extra windows debug info development libraries so that header
is available to be included.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151209/29797185/attachment.html>