I've had the same problem in my Clang-based tools.<div><br></div><div>I think we should either move all platform-specific include code out of Frontend into a separate library or move the Win32 header search code back into Frontend. Right now we have bits of it into different libraries and it's confusing and hard to figure out.</div>
<div><br></div><div>Another option would be move most of it into some configuration files (having hardcoded paths in the source for things like MinGW locations does not make much sense going forward).</div><div><div><br>
</div>
<div>The way I've "solved it" in the meanwhile, was by adding a function to access the Win32 platform headers search code in the driver (see the attached patch).</div><div><br></div><div><div class="gmail_quote">
On Sun, Aug 26, 2012 at 5:08 PM, Larry Olson <span dir="ltr"><<a href="mailto:loarabia@hotmail.com" target="_blank">loarabia@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">I've been maintaining some clang / llvm tutorials that show how to use the basic libraries from clang on github (<a href="https://github.com/loarabia/Clang-tutorial" target="_blank">https://github.com/loarabia/Clang-tutorial</a>). <span style="font-size:12pt">Because of a pull request this week to make the tutorials handle headers on Linux, I noticed that the code has drifted for handling some platforms' headers. </span><div>
<span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">In a nutshell, header handling of platform headers on Win32 and Linux Targets has moved out of InitHeaderSearch and into the Driver. The comments in the file read that the long term goal is to move all header handling out of InitHeaderSearch.</span></div>
<div><span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">My question then is, what is the right way for folks using the basic libraries to setup the full toolchain including headers search. Is that a scenario intended to be supported elsewhere? </span></div>
<div><span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">I can create a component that does basically what the Driver and ToolChain code does together but before I do that, I want to make sure that I am not overlooking the Intended Way (TM).</span></div>
<div><span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">Thanks,</span></div><div><span style="font-size:12pt">Larry</span></div> </div></div>
<br>_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Joćo Matos<br>
</div></div>