[cfe-dev] Clang and QNX

Douglas Gregor dgregor at apple.com
Tue Jan 3 09:08:48 PST 2012

On Jan 3, 2012, at 8:58 AM, Schmiedlin, Joshua wrote:

> Thanks Doug.  I will try both methods when I have a chance… If I modify InitHeaderSearch is it worthwhile to provide the patch back to Clang?

Yes, although looking at it more closely… it looks like you'll need some changes both in LLVM (to support the QNX OS in its Triple type) and in Clang.

	- Doug

> -          Josh
> From: Douglas Gregor [mailto:dgregor at apple.com] 
> Sent: Tuesday, January 03, 2012 11:57 AM
> To: Schmiedlin, Joshua
> Cc: cfe-dev at cs.uiuc.edu
> Subject: Re: [cfe-dev] Clang and QNX
> On Jan 2, 2012, at 5:49 AM, Schmiedlin, Joshua wrote:
> Hello,
> I would like to build clang on Windows so that It knows where my QNX standard headers are.  I don’t intend to create usable binaries, but ultimately I would like to be able to use clang to run static analysis on my code base.  I planned on using cmake to create the visual studio projects or mingw make files.  What if anything would I need to modify in order for Clang to know where all the QNX stuff lives?
> The simplest way is to simply use Clang's command-line options to turn off all of the normal system header includes (-nostdinc) and then add -isystem <path> and -I <path> options that point to your QNX standard headers.
> Now, if you don't want to do that, you can modify lib/Frontend/InitHeaderSearch.cpp to teach Clang about QNX system header paths. 
>             - Doug
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20120103/eec537bd/attachment.html>

More information about the cfe-dev mailing list