<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 19, 2012, at 18:04 , Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com">gribozavr@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thursday, December 20, 2012, Sean Silva wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span></span>Yes, having to hardcode this this is a pain in the ***. Unfortunately,<br>
it is a pretty nasty problem to solve. Probably the most palatable<br>
option currently is to embed the headers inside the clang libraries<br>
(in the binaries) and have it fall back on those if the current<br>
"hardcoded" lookup fails. But that requires messing around with the<br>
build system; nobody has stepped up to do that.</blockquote><div><br></div><div>And there's also a concern that if someone gets an error message referencing stddef.h, they might want to actually open and read it. But that's impossible if the header is embedded in the executable.</div>
</blockquote><br></div><div>Well, we do already have that problem for predefines, but at least people don't expect those to be files. Still, at least there'd be a workaround: "echo '#include <stddef.h>' | clang -E"</div><div><br></div><div>Jordan</div><br></body></html>