search for: llvm_plugin_ext

Displaying 7 results from an estimated 7 matches for "llvm_plugin_ext".

2014 Feb 13
2
[LLVMdev] [llvm] r201072 - [CMake] Introduce llvm_add_library().
...Feb 12, 2014, at 5:29 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Juergen, > > Thanks to let me know. I guess r200762 (and r200763) might affect. > > Although I won't check this on darwin box, I suspect the line in > HandleLLVMOptions.cmake; > > set(LLVM_PLUGIN_EXT ${CMAKE_SHARED_MODULE_SUFFIX}) > > Does it have expected value? > > 2014-02-13 10:11 GMT+09:00 Juergen Ributzka <juergen at apple.com>: >> Hi Takumi, >> >> I am not sure if it this change, but recently we started to build >> LLVMHello.so and BugpointPass...
2014 Feb 13
2
[LLVMdev] [llvm] r201072 - [CMake] Introduce llvm_add_library().
...apper macro also invoke target_link_libraries looks >> odd to someone familiar with cmake. >> >> I don't fully know what this wrapper is needed for, but I looked at it a >> bit. >> >> if(ARG_MODULE) >> set_property(TARGET ${name} PROPERTY SUFFIX ${LLVM_PLUGIN_EXT}) >> endif() >> >> if(ARG_SHARED) >> if (MSVC) >> set_target_properties(${name} >> PROPERTIES >> IMPORT_SUFFIX ".imp") >> endif () >> endif() >> >> >> CMake provides CMAKE_SHARED_MODULE_...
2014 Feb 10
2
[LLVMdev] [llvm] r201072 - [CMake] Introduce llvm_add_library().
...instead of add_library, the cmake command. Making that wrapper macro also invoke target_link_libraries looks odd to someone familiar with cmake. I don't fully know what this wrapper is needed for, but I looked at it a bit. if(ARG_MODULE) set_property(TARGET ${name} PROPERTY SUFFIX ${LLVM_PLUGIN_EXT}) endif() if(ARG_SHARED) if (MSVC) set_target_properties(${name} PROPERTIES IMPORT_SUFFIX ".imp") endif () endif() CMake provides CMAKE_SHARED_MODULE_SUFFIX and CMAKE_IMPORT_LIBRARY_SUFFIX. Can you set those at directory scope instead of setting the...
2017 Nov 25
2
PSA: debuginfo-tests workflow changing slightly
...ot;@CMAKE_BINARY_DIR@" + +config.llvm_src_root = "@LLVM_SOURCE_DIR@" +config.llvm_obj_root = "@LLVM_BINARY_DIR@" +config.llvm_tools_dir = "@LLVM_TOOLS_DIR@" +config.llvm_libs_dir = "@LLVM_LIBS_DIR@" +config.llvm_shlib_dir = "@SHLIBDIR@" +config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@" +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") +config.host_triple = "@LLVM_...
2017 Dec 06
3
PSA: debuginfo-tests workflow changing slightly
...c_root = "@LLVM_SOURCE_DIR@" >> +config.llvm_obj_root = "@LLVM_BINARY_DIR@" >> +config.llvm_tools_dir = "@LLVM_TOOLS_DIR@" >> +config.llvm_libs_dir = "@LLVM_LIBS_DIR@" >> +config.llvm_shlib_dir = "@SHLIBDIR@" >> +config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@" >> +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" >> +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" >> +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") >&gt...
2017 Dec 06
2
PSA: debuginfo-tests workflow changing slightly
...> +config.llvm_src_root = "@LLVM_SOURCE_DIR@" > +config.llvm_obj_root = "@LLVM_BINARY_DIR@" > +config.llvm_tools_dir = "@LLVM_TOOLS_DIR@" > +config.llvm_libs_dir = "@LLVM_LIBS_DIR@" > +config.llvm_shlib_dir = "@SHLIBDIR@" > +config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@" > +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" > +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" > +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") > +config.host_t...
2017 Nov 22
2
PSA: debuginfo-tests workflow changing slightly
I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure