search for: enable_crash_overrides

There is no real technical requirement for this. Currently we work around the signal handlers by building with ENABLE_CRASH_OVERRIDES=NO, and carrying along the command line parsing code and ToolOutputFile isn’t really a big drain. This seemed to me like the cleanest way to accomplish a goal of mine. The goal I have is to be able to build an LLVM dylib and llc/opt/etc from the same CMake invocation where the dylib does not have...

...mbedded uses like LLVM in the JavaScript JIT. One example of this type of functionality is the signal handlers. I'd like to propose migrating content that is specifically designed for tools into a new ToolsSupport library. My initial candidates for the new library would be; anything guarded by ENABLE_CRASH_OVERRIDES, and any functionality specific to tools (i.e. ToolOutputFile and eventually command line parsing— once it can be factored out). The primary goal of this is to make it easy for uses of LLVM that aren't command line tools to not include functionality that isn't required for that use case....

...only with the tools and not an external supported library at all. > > -Juergen > > On Oct 20, 2014, at 1:02 PM, Chris Bieneman <beanz at apple.com> wrote: > > There is no real technical requirement for this. Currently we work around > the signal handlers by building with ENABLE_CRASH_OVERRIDES=NO, and > carrying along the command line parsing code and ToolOutputFile isn’t > really a big drain. > > This seemed to me like the cleanest way to accomplish a goal of mine. The > goal I have is to be able to build an LLVM dylib and llc/opt/etc from the > same CMake invocation w...

...ported library at all. > > -Juergen > >> On Oct 20, 2014, at 1:02 PM, Chris Bieneman <beanz at apple.com <mailto:beanz at apple.com>> wrote: >> >> There is no real technical requirement for this. Currently we work around the signal handlers by building with ENABLE_CRASH_OVERRIDES=NO, and carrying along the command line parsing code and ToolOutputFile isn’t really a big drain. >> >> This seemed to me like the cleanest way to accomplish a goal of mine. The goal I have is to be able to build an LLVM dylib and llc/opt/etc from the same CMake invocation where the dy...

...; -Juergen >>> >>>> On Oct 20, 2014, at 1:02 PM, Chris Bieneman <beanz at apple.com <mailto:beanz at apple.com>> wrote: >>>> >>>> There is no real technical requirement for this. Currently we work around the signal handlers by building with ENABLE_CRASH_OVERRIDES=NO, and carrying along the command line parsing code and ToolOutputFile isn’t really a big drain. >>>> >>>> This seemed to me like the cleanest way to accomplish a goal of mine. The goal I have is to be able to build an LLVM dylib and llc/opt/etc from the same CMake invocat...