<div dir="ltr"><div>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.</div><div><br></div><div>-- Sean Silva</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 20, 2014 at 7:34 PM, Christian Convey <span dir="ltr"><<a href="mailto:christian.convey@gmail.com" target="_blank">christian.convey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi guys,<br>
<br>
This question is related to my previous post, but a little different I think.<br>
<br>
Suppose that I *need* to have a standalone tool's executable be<br>
located somewhere other than the normal directory, and therefore the<br>
relative search paths for builtin include directories won't work.<br>
<br>
Is it okay for me to simply specify those directories to my tool using<br>
"-I ..." directives instead?  If it's okay, are there any gotchas I<br>
need to worry about?<br>
<br>
Thanks,<br>
Christian<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>
</blockquote></div><br></div>