8e8d4b91a8
The only reason this was here was so that Module could have a function called CreateJITModule which created things in a special order. Instead of making this specific to creating JIT modules, I converted this into a template function that can create a module for any type of object file plugin and just forwards arguments through. Since the template is not instantiated in Core, the linker (and header file) dependency moves to the point where it is instantiated, which only happens in Expression. Conceptually, this location also makes more sense for a dependency on ObjectFileJIT. After all, we JIT expressions so it's no surprise that Expression needs to make use of ObjectFileJIT. Differential Revision: https://reviews.llvm.org/D47228 llvm-svn: 333143
40 lines
686 B
CMake
40 lines
686 B
CMake
if(NOT LLDB_BUILT_STANDALONE)
|
|
set(tablegen_deps intrinsics_gen)
|
|
endif()
|
|
|
|
add_lldb_library(lldbExpression
|
|
DiagnosticManager.cpp
|
|
DWARFExpression.cpp
|
|
Expression.cpp
|
|
ExpressionSourceCode.cpp
|
|
ExpressionVariable.cpp
|
|
FunctionCaller.cpp
|
|
IRDynamicChecks.cpp
|
|
IRExecutionUnit.cpp
|
|
IRInterpreter.cpp
|
|
IRMemoryMap.cpp
|
|
LLVMUserExpression.cpp
|
|
Materializer.cpp
|
|
REPL.cpp
|
|
UserExpression.cpp
|
|
UtilityFunction.cpp
|
|
|
|
DEPENDS
|
|
${tablegen_deps}
|
|
|
|
LINK_LIBS
|
|
lldbCore
|
|
lldbHost
|
|
lldbInterpreter
|
|
lldbSymbol
|
|
lldbTarget
|
|
lldbUtility
|
|
lldbPluginExpressionParserClang
|
|
lldbPluginObjectFileJIT
|
|
|
|
LINK_COMPONENTS
|
|
Core
|
|
ExecutionEngine
|
|
Support
|
|
)
|