search for: cmake_current_binary_dir

...blem is? > > - Daniel > > On Wed, Aug 5, 2009 at 8:04 AM, 罗勇刚(Yonggang Luo)<luoyonggang at gmail.com> > wrote: >> It's because of lib/Target/*/TargetInfo/CMakeLists.txt (* is Alpha, >> ARM and so on); >> the current line is include_directories( >> ${CMAKE_CURRENT_BINARY_DIR}/.. ${CMAKE_CURRENT_SOURCE_DIR}/.. ) >> and so msvc can't find out those directory properly. >> but once I changed it to >> include_directories( ${CMAKE_CURRENT_BINARY_DIR}/../ >> ${CMAKE_CURRENT_SOURCE_DIR}/../ ) >> It's working. >> But I am worry about...

...transforms") +feature_summary(WHAT ALL) + +configure_file(config.h.cmake config.h) + +set(speex_PUBLIC_HEADERS + include/speex/speex.h + include/speex/speex_bits.h + include/speex/speex_callbacks.h + include/speex/speex_header.h + include/speex/speex_stereo.h + include/speex/speex_types.h + ${CMAKE_CURRENT_BINARY_DIR}/include/speex/speex_config_types.h) + +set(speex_SOURCES + libspeex/cb_search.c + libspeex/exc_10_32_table.c + libspeex/exc_8_128_table.c + libspeex/filters.c + libspeex/gain_table.c + libspeex/hexc_table.c + libspeex/high_lsp_tables.c + libspeex/lsp.c + libspeex/ltp.c + libspeex/speex.c + libspee...

...d <garious at gmail.com> >> wrote: >> >> >> >> Alexey, Evgeniy, >> >> >> >> I propose the following steps to unify multi-arch support in >> compiler-rt: >> >> >> >> 1) The compiler-rt test suite adds "-L${CMAKE_CURRENT_BINARY_DIR}/lib" >> >> to its 'clang' variables. This way we can test the sanitizers without >> >> installing any libs to the just-built-clang install directory. >> > >> > >> > This is possible, but please keep in mind that: >> > 1) we...

...fective. > install(DIRECTORY include/ > DESTINATION include > # FILES_MATCHING > PATTERN "*.def" > PATTERN "*.h" > PATTERN "*.td" > PATTERN "*.inc" > PATTERN ".svn" EXCLUDE > ) > > install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/include/ > DESTINATION include > # FILES_MATCHING > PATTERN "*.def" > PATTERN "*.h" > PATTERN "*.gen" > PATTERN "*.inc" > # Exclude include/llvm/CMakeFiles/intrinsics_gen.dir, matched by "*.def" > PATTERN &quo...

...2014 at 2:50 AM, Greg Fitzgerald <garious at gmail.com> > wrote: > >> > >> Alexey, Evgeniy, > >> > >> I propose the following steps to unify multi-arch support in > compiler-rt: > >> > >> 1) The compiler-rt test suite adds "-L${CMAKE_CURRENT_BINARY_DIR}/lib" > >> to its 'clang' variables. This way we can test the sanitizers without > >> installing any libs to the just-built-clang install directory. > > > > > > This is possible, but please keep in mind that: > > 1) we would still want to use...

So you're referring to llvm_test_prepare? There aren't many examples of that being used. I tried adding a call to it in my test directory's CMakeLists.txt like so: llvm_test_prepare(WORKDIR ${CMAKE_CURRENT_BINARY_DIR} export MY_VAR=42 ) In the hopes that something would happen, even an error, but it had no effect. Nothing at http://llvm.org/docs/lnt/tests.html explains how to use these cmake macros, so I'm looking at test-suite/External/SPEC/CINT2000/175.vpr/CMakeLists.txt for an example. The tests tha...

...TARGET_LINK_FLAGS} > - -lstdc++ -lm ${CMAKE_THREAD_LIBS_INIT} > - ${CMAKE_DL_LIBS_INIT} -lrt) > + LINK_FLAGS ${TARGET_LINK_FLAGS} ${XRAY_UNITTEST_LINK_FLAGS} -lstdc++) > set_target_properties(XRayUnitTests > PROPERTIES RUNTIME_OUTPUT_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}) > endforeach() > @@ -66,11 +69,19 @@ endmacro() > > if(COMPILER_RT_CAN_EXECUTE_TESTS) > foreach(arch ${XRAY_SUPPORTED_ARCH}) > - add_xray_lib("RTXRay.test.${arch}" > - $<TARGET_OBJECTS:RTXray.${arch}> > - $<TARGET_OBJECTS:RTXrayFDR.${...

Hi Greg, On Wed, Apr 2, 2014 at 2:50 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Alexey, Evgeniy, > > I propose the following steps to unify multi-arch support in compiler-rt: > > 1) The compiler-rt test suite adds "-L${CMAKE_CURRENT_BINARY_DIR}/lib" > to its 'clang' variables. This way we can test the sanitizers without > installing any libs to the just-built-clang install directory. > This is possible, but please keep in mind that: 1) we would still want to use compiler-rt test-suite in a standalone mode, to test...

...gt;> >>>> >> Alexey, Evgeniy, >>>> >> >>>> >> I propose the following steps to unify multi-arch support in >>>> >> compiler-rt: >>>> >> >>>> >> 1) The compiler-rt test suite adds "-L${CMAKE_CURRENT_BINARY_DIR}/lib" >>>> >> to its 'clang' variables. This way we can test the sanitizers without >>>> >> installing any libs to the just-built-clang install directory. >>>> > >>>> > >>>> > This is possible, but please...

...>> - -lstdc++ -lm ${CMAKE_THREAD_LIBS_INIT} >> - ${CMAKE_DL_LIBS_INIT} -lrt) >> + LINK_FLAGS ${TARGET_LINK_FLAGS} ${XRAY_UNITTEST_LINK_FLAGS} -lstdc++) >> set_target_properties(XRayUnitTests >> PROPERTIES RUNTIME_OUTPUT_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}) >> endforeach() >> @@ -66,11 +69,19 @@ endmacro() >> >> if(COMPILER_RT_CAN_EXECUTE_TESTS) >> foreach(arch ${XRAY_SUPPORTED_ARCH}) >> - add_xray_lib("RTXRay.test.${arch}" >> - $<TARGET_OBJECTS:RTXray.${arch}> >> - $&...

...${LLVM_LINK_COMPONENTS} + ) + endif() + endif() + if(CMAKE_VERSION VERSION_LESS 2.8.12) # Link libs w/o keywords, assuming PUBLIC. target_link_libraries(${name} @@ -885,11 +891,18 @@ add_llvm_executable(${test_name} IGNORE_EXTERNALIZE_DEBUGINFO ${ARGN}) set(outdir ${CMAKE_CURRENT_BINARY_DIR}/${CMAKE_CFG_INTDIR}) set_output_directory(${test_name} BINARY_DIR ${outdir} LIBRARY_DIR ${outdir}) + if (LLVM_LINK_LLVM_DYLIB) + target_link_libraries(${test_name} + gtest + gtest_main + ) + else() target_link_libraries(${test_name} - gtest - gtest_main - LLVMSup...

It does sound like Android is better suited for "honest" cross-compilation, rather than "build compiler-rt for all targets we can find" model. I'm still not convinced that we must require the "ninja install" step. Could we just "ninja clang" and then build the second stage against the first stage build directory? Will this "find_package" thing

...;> >> >>>> >> I propose the following steps to unify multi-arch support in >> >>>> >> compiler-rt: >> >>>> >> >> >>>> >> 1) The compiler-rt test suite adds >> >>>> >> "-L${CMAKE_CURRENT_BINARY_DIR}/lib" >> >>>> >> to its 'clang' variables. This way we can test the sanitizers >> >>>> >> without >> >>>> >> installing any libs to the just-built-clang install directory. >> >>>> > >> &...

...========================== --- tools/lld/test/CMakeLists.txt +++ tools/lld/test/CMakeLists.txt @@ -17,11 +17,11 @@ if ( NOT LLD_BUILT_STANDALONE ) set(LLD_TEST_DEPS lld-core lld-test.deps - FileCheck not + FileCheck not llvm-nm ) set(LLD_TEST_PARAMS lld_site_config=${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg )

...st/CMakeLists.txt b/test/CMakeLists.txt > index c433ebe..24ccab0 100644 > --- a/test/CMakeLists.txt > +++ b/test/CMakeLists.txt > @@ -11,7 +11,7 @@ set(POLLY_TEST_DIRECTORIES > > set(POLLY_SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/..") > set(POLLY_BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/..") > -set(LLVM_SHLIBEXT "${CMAKE_SHARED_LIBRARY_SUFFIX}") > +set(LLVM_SHLIBEXT "${CMAKE_SHARED_MODULE_SUFFIX}") > > if (NOT DEFINED LLVM_MAIN_SRC_DIR) > # We are building polly out of tree, adjust the settings. > -- > 1.7.9.5 >

...s.txt --- llvm-project-10.0.1rc1/lld/CMakeLists.txt 2020-05-19 21:16:37.000000000 +0200 +++ llvm-project/lld/CMakeLists.txt 2020-05-20 18:40:07.817924825 +0200 @@ -120,16 +120,23 @@ set(LLD_SOURCE_DIR ${CMAKE_CURRENT_SOURC set(LLD_INCLUDE_DIR ${LLD_SOURCE_DIR}/include ) set(LLD_BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}) -# Compute the LLD version from the LLVM version. -string(REGEX MATCH "[0-9]+\\.[0-9]+(\\.[0-9]+)?" LLD_VERSION - ${PACKAGE_VERSION}) +# If LLD_VERSION_* is specified, use it, if not use LLVM_VERSION_*. +if(NOT DEFINED LLD_VERSION_MAJOR) + set(LLD_VERSION_MAJOR ${LLVM_VERSION_MAJOR})...

...nclude/ >> DESTINATION include >> # FILES_MATCHING >> PATTERN "*.def" >> PATTERN "*.h" >> PATTERN "*.td" >> PATTERN "*.inc" >> PATTERN ".svn" EXCLUDE >> ) >> >> install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/include/ >> DESTINATION include >> # FILES_MATCHING >> PATTERN "*.def" >> PATTERN "*.h" >> PATTERN "*.gen" >> PATTERN "*.inc" >> # Exclude include/llvm/CMakeFiles/intrinsics_gen.dir, matched by "*.def&quo...

Does the LNT test-suite provide a way to have an environment variable set when executing a test? I can set it outside of LNT (i.e. have it in my environment when LNT is launched) and that works fine, but there does not appear to be a way to set it as part of a test's configuration. There are some lit.local.cfg files scattered throughout the test-suite repository, but messing with os.environ

...,26 @@ +# Debug Info tests. These tests invoke clang to generate programs with +# various types of debug info, and then run those programs under a debugger +# such as GDB or LLDB to verify the results. + +set(DEBUGINFO_TESTS_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}) +set(DEBUGINFO_TESTS_BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}) + +set(DEBUGINFO_TEST_DEPS + clang + FileCheck + count + not + ) + +configure_lit_site_cfg( + ${CMAKE_CURRENT_SOURCE_DIR}/lit.site.cfg.py.in + ${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg.py + MAIN_CONFIG + ${CMAKE_CURRENT_SOURCE_DIR}/lit.cfg.py + ) + +add_lit_testsuite(check-debuginfo &quo...

...ke clang to generate programs with >> +# various types of debug info, and then run those programs under a debugger >> +# such as GDB or LLDB to verify the results. >> + >> +set(DEBUGINFO_TESTS_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}) >> +set(DEBUGINFO_TESTS_BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}) >> + >> +set(DEBUGINFO_TEST_DEPS >> + clang >> + FileCheck >> + count >> + not >> + ) >> + >> +configure_lit_site_cfg( >> + ${CMAKE_CURRENT_SOURCE_DIR}/lit.site.cfg.py.in <http://lit.site.cfg.py.in/> >> + ${CMAKE_CURRE...