search for: llvmbuild

...ig --libs | 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/unittest...

Hey all, Quick query on out of tree target support - at present I can drop a folder Foo into <llvm>/lib/Target/Foo and use the CMake option LLVM_EXPERIMENTAL_TARGETS_TO_BUILD to pick up my target. The issue is that I still need to patch the one LLVMBuild.txt file in <llvm>/lib/Target with; |iff --git a/lib/Target/LLVMBuild.txt b/lib/Target/LLVMBuild.txt index 4112046..6e42cbe 100644 --- a/lib/Target/LLVMBuild.txt +++ b/lib/Target/LLVMBuild.txt @@ -16,7 +16,7 @@ ;===------------------------------------------------------------------------==...

...on the link command, resulting in an error of the form: PassManagerBuilder.cpp:(.text+0x499): undefined reference to `registerPollyEarlyAsPossiblePasses Digging a bit in the machinery of the cmake builds, I realized that the order in which the libLLVM*.a are output depends on the contents of the LLVMBuild.txt processed by a script: utils/llvm-build/llvmbuild/main.py that creates a LLVMBuild.cmake file in the build dir specifying the link time dependences on a lib: for example, ./LLVMBuild.cmake:set_property(GLOBAL PROPERTY LLVMBUILD_LIB_DEPS_LLVMipo LLVMAnalysis LLVMCore LLVMInstCombine LLVMObjCARC...

I believe we'd need LLVMBuild.txt even in autoconf build - for bunch of autogenerated stuff, e.g. list of all asmprinters / asmparsers / InitializeAllTargetInfos, etc., since targets are not autoregistered anymore. On Mon, Mar 9, 2015 at 7:20 PM, Eric Christopher <echristo at gmail.com> wrote: > Hi Neil, > > Wei...

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

...how do I implement similar find stuff for clang >>> libraries? >> >> 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 anybo...

...the assembly code generated with llc -march=sparc on the x86 machine does not compile on the sparc machine. Any help would be greatly appreciated. Thank you, Alexandra ************************************************************************************************  make llvm[0]: Constructing LLVMBuild project information. Traceback (most recent call last):   File "/llvm3.1/llvm-3.1/utils/llvm-build/llvm-build", line 3, in ?     import llvmbuild   File "/llvm3.1/llvm-3.1/utils/llvm-build/llvmbuild/__init__.py", line 1, in ?     from main import main   File "/llvm3.1/llvm-...

...> libraries? >>>> >>>> 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-buil...

On Thu, Oct 31, 2013 at 12:17 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Is there a reason to not use the cmake add_dependencies to establish the link > order of the LLVM libs instead of using the LLVMBuild.txt info? Have you tried `target_link_libraries`? The new CMake book has an example showing one static lib depending on another (page 25): `target_link_libraries(foo bar)` where `foo` uses symbols from `bar`. -Greg

...g the resulting xcodeproj. In trying to build the skeleton openrisc backend from https://github.com/asl/llvm-openrisc as described in "building a backend in 24 hours" at http://llvm.org/devmtg/2012-04-12/Slides/Workshops/Anton_Korobeynikov.pdf, I find there are no cmakelists but there are llvmbuild.txt's. Is the llvmbuild somehow used to generate the cmakelists? The presentation and repository are several years old, has the build system changed that much? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-d...

Constructing LLVMBuild project information CMake Error at CMakeLists.txt:299 (message): Unexpected failure executing llvm-build: Traceback (most recent call last): File "C:/OpenSource/llvm/utils/llvm-build/llvm-build", line 3, in <module> import llvmbuild File "C:\OpenSource\llvm\utils\llvm-buil...

The attached patch modifies the CMake/LLVMBuild scripts to build llvm-config on Windows if sed is found on the user's PATH. It also teaches LLVMBuild about MSVC library naming so llvm-config will produce the proper lists of library names. Any comments? Okay to commit? ---------------------------------------------------------------------...

...lem running cmake. Note that I built the trunk release just fine, right now I'm modifying it. *The setup:* My target is called TMS9900 because I'm a masochist, and I'm just trying to make a bare do-nothing skeleton to start with. I have this: lib/Target/TMS9900 - CMakeLists.txt - LLVMBuild.txt - TMS9900TargetMachine.cpp - TMS9900TargetMachine.h - TMS9900.td TMS9900TargetMachine is the barest class I could make. It derives from LLVMTargetMachine, and passes everything through (although it defines the DataLayout). CMakeLists.txt is also pretty small: set(LLVM_TARGET_DEFINITION...

...I ran ./configure with --enable-debug-runtime, then make -j4, before I got the following error: llvm[1]: Building llvm-config script. make[1]: Leaving directory `/home/vk/opt/llvm/tools/llvm-config' make[1]: Entering directory `/home/vk/opt/llvm/tools/llvm-config-2' llvm[1]: Constructing LLVMBuild project information. Traceback (most recent call last): File "/home/vk/opt/llvm/utils/llvm-build/llvm-build", line 3, in <module> import llvmbuild File "/home/vk/opt/llvm/utils/llvm-build/llvmbuild/__init__.py", line 1, in <module> from main import main I...

...cpp PrintSCC.cpp opt.cpp DEPENDS intrinsics_gen ) export_executable_symbols(opt) if(WITH_POLLY AND LINK_POLLY_INTO_TOOLS) target_link_libraries(opt PRIVATE Polly) endif(WITH_POLLY AND LINK_POLLY_INTO_TOOLS) target_link_libraries(opt PUBLIC LLVMExecutionEngine) ``` Modified opt's LLVMBuild.txt: ``` ;===- ./tools/opt/LLVMBuild.txt --------------------------------*- Conf -*--===; ; ; The LLVM Compiler Infrastructure ; ; This file is distributed under the University of Illinois Open Source ; License. See LICENSE.TXT for details. ; ;===-------------------------------...

...t shyam:~$ cat hello.javaclass hello { public static final String str = "Hello Word"; public static void main(String[] args) { System.out.println(str); }}shyam at shyam:~$ llcj --main=hello hello.class -o hellollc: Unknown command line argument '-f'. Try: '/home/shyam/llvmbuild/Release+Debug+Asserts/bin/llc -help'llc: Did you mean '-O'? I edited the vmkit/tools/llcj/llcj.cpp file line number ---- code188 const char* llcArgv[8];189 int i = 0;190 llcArgv[i++] = Prog.c_str();191 llcArgv[i++] = Out.c_str();192 if (shared) llcArgv[i++] = "-reloc...

.../trunk/test/ExecutionEngine/Interpreter/intrinsics.ll FAIL: LLVM :: ExecutionEngine/Interpreter/intrinsics.ll (7635 of 14266) > ******************** TEST 'LLVM :: > ExecutionEngine/Interpreter/intrinsics.ll' FAILED ******************** > Script: > -- > C:/msys64/home/Martell/llvmbuild/./bin/lli.EXE -O0 -force-interpreter < > C:/msys64/home/Martell/llvm/test/ExecutionEngine/Interpreter/intrinsics.ll > -- > Exit Code: 1 > > Command Output (stdout): > -- > Command 0: "C:/msys64/home/Martell/llvmbuild/./bin/lli.EXE" "-O0" > "-force...

The bot has been failing its CMake step for a while now. Probably fallout from renaming Msf to MSF. Can somebody get this straightened out? It's one of the bots that run VS2013 AFAICT which makes it useful to me. Thanks, --paulr

...tion, it still calls an external Python script, namely llvm-build, to manage component dependecies, activation or deactivation of target componenents and generating description for llvm-config. This system is documented in http://llvm.org/docs/CommandGuide/llvm-build.html and https://llvm.org/docs/LLVMBuild.html. Several features of the system are either undocumented, obsolete or redundant with the cmake description (sometimes all at once!). For instance the LLVMBuild.txt under tools/ don't seem relevant anymore. And the –write-make-fragment for Makefile comptibility no longer makes sense. The w...

...t; ..\llvm* /-- Could NOT find LibXml2 (missing: LIBXML2_LIBRARIES LIBXML2_INCLUDE_DIR)// //-- Target triple: x86_64-w64-mingw32// //-- Native target architecture is X86// //-- Threads enabled.// //-- Found PythonInterp: C:/Python33/python.exe (found version "3.3.2")// //-- Constructing LLVMBuild project information// //CMake Error at CMakeLists.txt:299 (message):// // Unexpected failure executing llvm-build: Traceback (most recent call last):// // // File "<project folder>/llvm/utils/llvm-b// //uild/llvm-build", line 3, in <module>// // import llvmbuild// //...