mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 11:13:28 +01:00
b6537e49a5
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
45 lines
665 B
CMake
45 lines
665 B
CMake
if ( LLVM_INCLUDE_UTILS )
|
|
add_subdirectory(ChildTarget)
|
|
endif()
|
|
|
|
set(LLVM_LINK_COMPONENTS
|
|
CodeGen
|
|
Core
|
|
ExecutionEngine
|
|
IRReader
|
|
Instrumentation
|
|
Interpreter
|
|
MC
|
|
MCJIT
|
|
Object
|
|
OrcJIT
|
|
RuntimeDyld
|
|
SelectionDAG
|
|
Support
|
|
Target
|
|
TransformUtils
|
|
native
|
|
)
|
|
|
|
if( LLVM_USE_OPROFILE )
|
|
set(LLVM_LINK_COMPONENTS
|
|
${LLVM_LINK_COMPONENTS}
|
|
OProfileJIT
|
|
)
|
|
endif( LLVM_USE_OPROFILE )
|
|
|
|
if( LLVM_USE_INTEL_JITEVENTS )
|
|
set(LLVM_LINK_COMPONENTS
|
|
${LLVM_LINK_COMPONENTS}
|
|
DebugInfoDWARF
|
|
IntelJITEvents
|
|
Object
|
|
)
|
|
endif( LLVM_USE_INTEL_JITEVENTS )
|
|
|
|
add_llvm_tool(lli
|
|
lli.cpp
|
|
OrcLazyJIT.cpp
|
|
)
|
|
export_executable_symbols(lli)
|