llvm-project/llvm/tools/lli/ChildTarget/CMakeLists.txt

set(LLVM_LINK_COMPONENTS
  OrcJIT
  RuntimeDyld
  Support
  )

add_llvm_utility(lli-child-target
  ChildTarget.cpp
)
[LLI] Replace the LLI remote-JIT support with the new ORC remote-JIT components. The new ORC remote-JITing support provides a superset of the old code's functionality, so we can replace the old stuff. As a bonus, a couple of previously XFAILed tests have started passing. llvm-svn: 257343 2016-01-12 00:35:55 +08:00			`set(LLVM_LINK_COMPONENTS`
			`OrcJIT`
lli-child-target: Introduce a new dependency on RuntimeDyld. llvm-svn: 257410 2016-01-12 07:12:30 +08:00			`RuntimeDyld`
[LLI] Replace the LLI remote-JIT support with the new ORC remote-JIT components. The new ORC remote-JITing support provides a superset of the old code's functionality, so we can replace the old stuff. As a bonus, a couple of previously XFAILed tests have started passing. llvm-svn: 257343 2016-01-12 00:35:55 +08:00			`Support`
			`)`
Refactor lli-child-target to remove duplicated code Eliminate the copies LLVM's System mmap and cache invalidation code. These were slowly drifting away from the original version, and moreover the copied code was a dead end in terms of portability. We now statically link to Support but in practice with stripping this adds next to no weight to the resultant binary. Also avoid installing lli-child-target to the user's $PATH. It's not meant to be run directly. llvm-svn: 199881 2014-01-23 19:04:42 +08:00
[cmake] Change lli-child-target to use add_llvm_utility instead of add_llvm_executable. We are currently using add_llvm_utility for executable targets that: 1. Are built by default. 2. Used for testing. 3. Are not installed by default. Originally, lli-child-target used add_llvm_tool instead of add_llvm_executable directly. This was changed so that lli-child-target would not be installed. This was good since this is only used for testing and should never be installed for users. This also had the unfortunate side effect that one can never turn off the building of lli-child-target by default, a regression for projects that by default do not want to compile any LLVM tools beyond tablegen/llvm-config. This patch changes lli-child-target to use add_llvm_utility. This makes sense since: 1. lli-child-target matches the semantics of executables created with add_llvm_utility. 2. We fix the regression since now one can use the flag LLVM_BUILD_UTILS to eliminate default compilation. llvm-svn: 275008 2016-07-10 10:43:50 +08:00			`add_llvm_utility(lli-child-target`
Adding out-of-process execution support to lli. At this time only Unix-based systems are supported. Windows has stubs and should re-route to the simulated mode. Thanks to Sriram Murali for contributions to this patch. llvm-svn: 191843 2013-10-03 01:12:36 +08:00			`ChildTarget.cpp`
Refactor lli-child-target to remove duplicated code Eliminate the copies LLVM's System mmap and cache invalidation code. These were slowly drifting away from the original version, and moreover the copied code was a dead end in terms of portability. We now statically link to Support but in practice with stripping this adds next to no weight to the resultant binary. Also avoid installing lli-child-target to the user's $PATH. It's not meant to be run directly. llvm-svn: 199881 2014-01-23 19:04:42 +08:00			`)`
[CMake] Put lli-child-target into the Folder "Misc". llvm-svn: 200297 2014-01-28 17:43:41 +08:00