Valid ways to specify builtin include directories?

Clang Frontend
1

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

2

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

3

Thanks Sean. Do you know if that will override the default resource
directory, or simply add to the search list while also leaving the
default resource directory in effect?

4

Thanks Sean. Do you know if that will override the default resource
directory, or simply add to the search list while also leaving the
default resource directory in effect?

It should override it.

-- Sean Silva