search for: libllvmtoolssupport

I was thinking of moving the files into a Tools subdirectory of Support, and having a new library generated from that. Does that mesh with what you’d like to see? I’ve gotten wrapped into a nasty internal bug hunt, so I probably won’t have patches until next week. I will also probably need to ask Eric for help with the autoconf side of things because my familiarity with autoconf ends at “run

...his wasn’t so small. These patches aren’t done yet, but since they’re pretty big I thought I’d send them out for preliminary feedback about whether or not this is the right approach. The patches contain the following changes: > > * Patches to LLVM & Clang CMake build systems to add a new libLLVMToolsSupport > * New SignalHandlers.h/.cpp/.inc files for PrintStackTraceOnErrorSignal > * Updated all llvm tools to pull in the new library and use the new header > > Still missing: > > * Windows side of the SignalHandlers patches > * Autoconf/Make side of the build system patches > *...

Here is my limited perspective on this topic: 1. I would like to see some of the code in LLVM's ADT and Support libraries available for reuse in other projects. This also has some potential for being useful to Clang -- one could imagine a world where Clang directly linked the ADT & Support libraries, but used the compiler itself via a clear dynamic-library vended API (which would be