search for: componentinfo

...| tr " " "\n" | grep gtest) returns: -lgtest_main -lgtest instead of non-valid: -lLLVMgtest_main -lLLVMgtest It also fixes: $(ld): cannot find -lLLVMgtest $(ld): cannot find -lLLVMgtest_main --- unittests/Makefile.unittest | 2 +- utils/llvm-build/llvmbuild/componentinfo.py | 4 ++-- utils/llvm-build/llvmbuild/main.py | 5 ++++- utils/unittest/UnitTestMain/Makefile | 2 +- utils/unittest/googletest/Makefile | 2 +- 5 files changed, 9 insertions(+), 6 deletions(-) diff --git a/unittests/Makefile.unittest b/unittests/Makefile.uni...

On 1/21/2013 2:01 AM, Óscar Fuentes wrote: > Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > >> I was using the find_package(LLVM llvm/share/llvm/cmake) and >> llvm_map_components_to_libraries(REQ_LLVM_LIBRARIES jit native) to get >> the libraries to link against. This works well for the libLLVM* >> libraries, but how do I implement similar find stuff for

...t; >> AFAIK, there is no such feature for Clang. I noticed that the following files are modified even though I'm compiling outside the source tree (using cmake): > # modified: src/utils/llvm-build/llvmbuild/__init__.pyc > # modified: src/utils/llvm-build/llvmbuild/componentinfo.pyc > # modified: src/utils/llvm-build/llvmbuild/configutil.pyc > # modified: src/utils/llvm-build/llvmbuild/main.pyc > # modified: src/utils/llvm-build/llvmbuild/util.pyc Does anybody know why the sources are being modified? thanks, ashok

...lang. >> >> I noticed that the following files are modified even though I'm compiling >> outside the source tree (using cmake): >> >>> # modified: src/utils/llvm-build/llvmbuild/__init__.pyc >>> # modified: src/utils/llvm-build/llvmbuild/componentinfo.pyc >>> # modified: src/utils/llvm-build/llvmbuild/configutil.pyc >>> # modified: src/utils/llvm-build/llvmbuild/main.pyc >>> # modified: src/utils/llvm-build/llvmbuild/util.pyc >> >> Does anybody know why the sources are being modified...