search for: required_librari

...the accidental linkage of libLLVMSupport with libLLVM and libgtest for the unittests was really tricky as two different mechanisms to pass LLVMSupport are in play. The underlying problem was that the python based llvm-build tool was forcing a dependency on LLVMSupport for libgtest according to the required_libraries entry for the gtest library in utils/unittest/LLVMBuild.txt. Since the llvm-build tool has no access to the cmake defines, I had to solve this problem by adding a new --enable-llvm-link-llvm-dylib option in utils/llvm-build/llvmbuild/main.py to allow the LLVM_LINK_LLVM_DYLIB build to prune '...

..._DEFINITIONS TMS9900.td) add_llvm_library(TMS9900CodeGen TMS9900TargetMachine.cpp ) LLVMBuild.txt is as minimal as I could guess at: [common] subdirectories = [component_0] type = TargetGroup name = TMS9900 parent = Target [component_1] type = Library name = TMS9900CodeGen parent = TMS9900 required_libraries = Analysis AsmPrinter CodeGen Core MC Scalar SelectionDAG Support Target TransformUtils add_to_library_groups = TMS9900 And finally, TMS9900.td contains: include "llvm/Target/Target.td" def TMS9900 : Target { } I also updated lib/Target/LLVMBuild.txt's [common] subdirectories to...

Hello everyone! Could somebody, advice me what's wrong with my AsmPrinter? I've created ColdFireAsmPrinter.cpp file, and added initialization: extern "C" void LLVMInitializeColdFireAsmPrinter() { RegisterAsmPrinter<ColdFireAsmPrinter> X(TheColdFireTarget); } But, unfortunately, after build AsmPrinters.def doesn't contain LLVM_ASM_PRINTER(ColdFire). Maybe I've

> 1. I've configured llvm with my target. And after, I added AsmPrinter. Do I > need re-configure LLVM, or only re-make? re-configure, as I mentioned > 2. required_libraries list contains AsmPrinter or you mean something else? has_asmprinter = 1 in TargetGroup -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...d description file for the components in this subdirectory. ; ; For more information on the LLVMBuild system, please see: ; ; http://llvm.org/docs/LLVMBuild.html ; ;===------------------------------------------------------------------------===; [component_0] type = Tool name = opt parent = Tools required_libraries = AsmParser BitReader BitWriter CodeGen IRReader IPO Instrumentation Scalar ObjCARC Passes ExecutionEngine Interpreter MCJIT Native NativeCodeGen all-targets ``` On top of that I also added these lines to the beginning of main function in opt.cpp to force linking ExecutionEngine...

...so Dan Liew. > Hans, My current, and hopefully final, revision of the proposed patch is simplified and reworked to solve the problem entirely from cmake without touching the the llvm-build python scripts. Basically, the new fix for avoiding the Support library dependency set from the 'required_libraries = Support' in llvm/utils/unittest/LLVMBuild.txt is not read it for LLVM_LINK_LLVM_DYLIB. The new patch modifies llvm_add_library() in cmake/modules/AddLLVM.cmake to manually set the LLVMBUILD_LIB_DEPS_gtest property to LLVM when LLVM_LINK_LLVM_DYLIB is set and the library name is gtest rathe...

Hey: I spent sometime debugging this, it seems like editing ``llvm/tools/opt.cpp`` and move ``cl::ParseCommandLineOptions(argc, argv, "llvm .bc -> .bc modular optimizer and analysis printer\n");`` to the beginning of main() solved it for me. I'm not sure if this is a bug on LLVM side Zhang ------------------ Original ------------------ From: "Viktor Was BSc via

...gt; ;===------------------------------------------------------------------------===; > > -[common] > -subdirectories = Interpreter MCJIT RuntimeDyld IntelJITEvents OProfileJIT Orc > - > [component_0] > -type = Library > -name = ExecutionEngine > -parent = Libraries > -required_libraries = Core MC Object RuntimeDyld Support Target > +type = OptionalLibrary > +name = PerfJITEvents > +parent = ExecutionEngine > +required_libraries = CodeGen Core DebugInfoDWARF Support Object ExecutionEngine > diff --git a/lib/ExecutionEngine/PerfJITEvents/PerfJITEventListener.cpp b/l...

...f the component. name = VMCore # The name of the component to logically group this in. This is just for # organization purposes. parent = Libraries # The names of the library components that are also required when linking # with this library. More on this later. required_libraries = Support The exact structure of the format is TBD (and easy to change), currently the format is INI style but I may decide to change to JSON once all the pieces are in place. The LLVM web pages will have clear documentation on what these files should look like, what is required,...

Having something like this available in tree would definitely be useful. For simplicity, why don't we start with support for the second style? This is the long term useful one and would be a good starting point for getting the code in tree. Can you give a pointer to the patch so that I can assess the rough complexity? If it's simple enough, I'd be happy to help get it reviewed

Hi, On 2016-12-29 13:17:50 -0800, Philip Reames wrote: > Having something like this available in tree would definitely be > useful. Cool. > For simplicity, why don't we start with support for the second style? This > is the long term useful one and would be a good starting point for getting > the code in tree. Works for me. > Can you give a pointer to the patch so that

...gt; # The name of the component to logically group this in. This is just > for > # organization purposes. > parent = Libraries > > # The names of the library components that are also required when > linking > # with this library. More on this later. > required_libraries = Support > > The exact structure of the format is TBD (and easy to change), currently > the > format is INI style but I may decide to change to JSON once all the > pieces > are in place. > > The LLVM web pages will have clear documentation on what these files >...

...name of the component. name = VMCore # The name of the component to logically group this in. This is just for # organization purposes. parent = Libraries # The names of the library components that are also required when linking # with this library. More on this later. required_libraries = Support The exact structure of the format is TBD (and easy to change), currently the format is INI style but I may decide to change to JSON once all the pieces are in place. The LLVM web pages will have clear documentation on what these files should look like, what is required, what...

...e > > # The name of the component to logically group this in. This is just for > # organization purposes. > parent = Libraries > > # The names of the library components that are also required when linking > # with this library. More on this later. > required_libraries = Support > > The exact structure of the format is TBD (and easy to change), currently the > format is INI style but I may decide to change to JSON once all the pieces > are in place. > > The LLVM web pages will have clear documentation on what these files should >...

...; # The name of the component to logically group this in. This is just for > # organization purposes. > parent = Libraries > > # The names of the library components that are also required when linking > # with this library. More on this later. > required_libraries = Support > > The exact structure of the format is TBD (and easy to change), currently the > format is INI style but I may decide to change to JSON once all the pieces > are in place. > > The LLVM web pages will have clear documentation on what these files should...

Patch for review. On Mon, Aug 21, 2017 at 11:45 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> wrote: > Ping. > > Still working on preparing code for review. Will have a patch for review > ready in the coming days. > > PL > > On Tue, Aug 15, 2017 at 12:06 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> > wrote: > >> Hi, >> >> >>

...components in this subdirectory. +; +; For more information on the LLVMBuild system, please see: +; +; http://llvm.org/docs/LLVMBuild.html +; +;===------------------------------------------------------------------------===; + +[component_0] +type = Library +name = CustomCallback +parent = $ROOT +required_libraries = Core Support Target Index: CustomCallback/Makefile =================================================================== --- CustomCallback/Makefile (revision 0) +++ CustomCallback/Makefile (working copy) @@ -0,0 +1,13 @@ +##===- lib/ExecutionEngine/CustomCallback/Makefile ----------------------...