[cfe-dev] Valid ways to specify builtin include directories?

[Sean Silva]

Manually specifying -resource-dir should work if you know where the builtin
includes live, even though they happen to not be at their regular location
relative to the executable.

-- Sean Silva

On Thu, Nov 20, 2014 at 7:34 PM, Christian Convey <
christian.convey at gmail.com> wrote:

> Hi guys,
>
> This question is related to my previous post, but a little different I
> think.
>
> Suppose that I *need* to have a standalone tool's executable be
> located somewhere other than the normal directory, and therefore the
> relative search paths for builtin include directories won't work.
>
> Is it okay for me to simply specify those directories to my tool using
> "-I ..." directives instead?  If it's okay, are there any gotchas I
> need to worry about?
>
> Thanks,
> Christian
> _______________________________________________
> 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/20141120/f2755353/attachment.html>