<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 2, 2011, at 4:28 PM, Eric Christopher wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 2, 2011, at 4:01 PM, Douglas Gregor wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On Feb 2, 2011, at 2:29 PM, Óscar Fuentes wrote:<br><br><blockquote type="cite">Douglas Gregor <<a href="mailto:dgregor@apple.com">dgregor@apple.com</a>> writes:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">We'd like to be able to consider LLVM as a stable library that Clang<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">depends on. This would allow us to build against an installed LLVM<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(rather than embedding our own full copy of LLVM in Clang), test Clang<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and LLVM more independently,<br></blockquote></blockquote><blockquote type="cite">[snip]<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">There are some configuration options (C_INCLUDE_DIRS,<br></blockquote><blockquote type="cite">CLANG_RESOURCE_DIR) which are stored on LLVM's config.h file.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The Right Thing is to create a config.h file for Clang, which is a task<br></blockquote><blockquote type="cite">a bit more obtrusive than I used to. It would consist on passing<br></blockquote><blockquote type="cite">-DHAVE_CLANG_CONFIG_H on the command line and adding<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">#ifdef HAVE_CLANG_CONFIG_H<br></blockquote><blockquote type="cite"># include "clang/Config/config.h"<br></blockquote><blockquote type="cite">#endif<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">where necessary. This allows the autoconf build to remain unaffected.<br></blockquote><br><br>This sounds like the right approach.<br></div></blockquote></div><br><div>Why not just have clang's config.h just be entirely separate from llvm? While</div><div>you may be duplicating a few things in a new configure.ac for clang it wouldn't</div><div>be a whole lot and then you could just (effectively) ./configure clang as</div><div>well and it'll just look for llvm on the system, otherwise just do a recursive</div><div>configure?</div></div></blockquote><div><br></div><div>You know, now that you mention it.... yeah, that would probably be better. Thanks, Eric!</div><br><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><br></body></html>