search for: llvm_root

...jllvm Analysis_wrap.c BitReader_wrap.c BitWriter_wrap.c >> Core_wrap.c EnhancedDisassembly_wrap.c ExecutionEngine_wrap.c >> LinkTimeOptimizer_wrap.c lto_wrap.c Target_wrap.c >> Transforms/IPO_wrap.c Transforms/Scalar_wrap.c) >> >> # A convenience variable: >> set(LLVM_ROOT "/usr" CACHE /usr/ "Root of LLVM install.") >> # A bit of a sanity check: >> if( NOT EXISTS ${LLVM_ROOT}/include/llvm ) >> message(FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM >> install") >> endif() >> >> # We inc...

...://llvm.org/releases/3.1/docs/CMake.html#passdev), I copied the files in the llvm/lib/Transforms/Hello to another folder in order to give a try. Then I renamed the folder as Hello2. Then I have changed CMakeLists.txt as following: cmake_minimum_required(VERSION 2.8) # A convenience variable: set(LLVM_ROOT "../llvm_cmake_build" CACHE PATH "Root of LLVM install.") # A bit of a sanity check: if( NOT EXISTS ${LLVM_ROOT}/include/llvm ) message(FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM install") endif() # We incorporate the CMake features provided by LLVM: s...

...vm) > add_library(jllvm Analysis_wrap.c BitReader_wrap.c BitWriter_wrap.c > Core_wrap.c EnhancedDisassembly_wrap.c ExecutionEngine_wrap.c > LinkTimeOptimizer_wrap.c lto_wrap.c Target_wrap.c > Transforms/IPO_wrap.c Transforms/Scalar_wrap.c) > > # A convenience variable: > set(LLVM_ROOT "/usr" CACHE /usr/ "Root of LLVM install.") > # A bit of a sanity check: > if( NOT EXISTS ${LLVM_ROOT}/include/llvm ) > message(FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM > install") > endif() > # We incorporate the CMake features prov...

...ake. > > > And llvm/projects/sample uses autoconf (or ./configure). Is there cmake > > based sample project available? > > I could not find any from official release. Has any of you written sample > > project template that uses cmake? > > Just make a directory under LLVM_ROOT/projects and put your source > there, with a CMakeLists.txt file that contains the right directives > (you can use any of the llvm tools or libraries under LLVM_ROOT/tools or > LLVM_ROOT/lib as an example.) After creating those files, you must > re-invoke cmake for it taking notice of y...

...-07-VarArgs.c:50: error: expected expression before 'DWordS' /Users/build/NightlyBuild/rabbit_main/3rdparty/llvm-2.6-src/projects/ test-suite/SingleSource/UnitTests/2003-05-07-VarArgs.c:50: error: incompatible types in assignment Developer/usr/bin/llvm-g++ -I/Users/build/NightlyBuild/llvm_root/ deploy/llvm-2.6-test/projects/test-suite/SingleSource/Regression/C++ - I/Users/build/NightlyBuild/llvm_root/3rdparty/llvm-2.6-src/projects/ test-suite/SingleSource/Regression/C++ -I/Users/build/NightlyBuild/ llvm_root/deploy/llvm-2.6-test/include -I/Users/build/NightlyBuild/ llvm_root/3rdpart...

...Those files are unrelated to cmake. > And llvm/projects/sample uses autoconf (or ./configure). Is there cmake > based sample project available? > I could not find any from official release. Has any of you written sample > project template that uses cmake? Just make a directory under LLVM_ROOT/projects and put your source there, with a CMakeLists.txt file that contains the right directives (you can use any of the llvm tools or libraries under LLVM_ROOT/tools or LLVM_ROOT/lib as an example.) After creating those files, you must re-invoke cmake for it taking notice of your new project. An...

....c Core_wrap.c EnhancedDisassembly_wrap.c ExecutionEngine_wrap.c LinkTimeOptimizer_wrap.c lto_wrap.c Target_wrap.c Transforms/IPO_wrap.c Transforms/Scalar_wrap.c) install(TARGETS jllvm DESTINATION lib/) add_definitions( -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS ) # A convenience variable: set(LLVM_ROOT "/usr/" CACHE /usr/ "Root of LLVM install.") set(CMAKE_INSTALL_PREFIX "/usr") # A bit of a sanity check: if( NOT EXISTS ${LLVM_ROOT}/include/llvm ) message(FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM install") endif() # We incorporate the CMake...

Hi, I built LLVM on Windows XP through cmake and MinGW make. That was a breeze! Now, I wanted to start a project. It seems like I need Makefile.rules and Makefile.config to start a new project (from http://llvm.org/docs/Projects.html). And llvm/projects/sample uses autoconf (or ./configure). Is there cmake based sample project available? I could not find any from official release. Has any of you

...her options). By the way, I found it annoying to reinstall LLVM, I expected a complete and working LLVM environment with Apple's move to CLANG, but maybe I didn't try that hard. Anyway, this is my lines on CMakeLists.txt, working on linux like a charm: ########### LLVM ########## SET (LLVM_ROOT "" CACHE PATH "Root of LLVM install.") IF (NOT EXISTS ${LLVM_ROOT}/include/llvm) MESSAGE (FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM install") ENDIF () SET (CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} "${LLVM_ROOT}/share/llvm/cmake") INCLUDE (...

...projects/sample uses autoconf (or ./configure). Is there cmake >> > based sample project available? >> > I could not find any from official release. Has any of you written >> sample >> > project template that uses cmake? >> >> Just make a directory under LLVM_ROOT/projects and put your source >> there, with a CMakeLists.txt file that contains the right directives >> (you can use any of the llvm tools or libraries under LLVM_ROOT/tools or >> LLVM_ROOT/lib as an example.) After creating those files, you must >> re-invoke cmake for it ta...

On Fri, Oct 5, 2012 at 3:45 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall > <David.Chisnall at cl.cam.ac.uk> wrote: >> On 5 Oct 2012, at 08:34, Jun Koi wrote: >> >>> any idea on how to fix the problem? >> >> The correct solution is to fix the LLVM build to install the .cmake files in a location that

On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 Oct 2012, at 08:34, Jun Koi wrote: > >> any idea on how to fix the problem? > > The correct solution is to fix the LLVM build to install the .cmake files in a location that CMake knows about. could you please elaborate? > The hacky solution that I've used is just to copy

...irectory > Hello2/Hello.cpp:21: error: ‘llvm’ is not a namespace-name > ... > > Your feedback is very welcome. I think this is the same problem that was reported here a few weeks ago. IIRC LLVM_INCLUDE_DIRS and LLVM_LIBRARY_DIRS are wrong after install. Try with include_directories( ${LLVM_ROOT}/include ) link_directories( ${LLVM_ROOT}/lib )

...>> ./configure; make; make install > > any help on this sample LLVM pass, please? any help, please? i am still stuck on this problem. i fixed CMakeLists.txt in the root directory to be like below: $ cat CMakeLists.txt cmake_minimum_required(VERSION 2.8) # A convenience variable: set(LLVM_ROOT "/usr" CACHE /usr/ "Root of LLVM install.") # A bit of a sanity check: if( NOT EXISTS ${LLVM_ROOT}/include/llvm ) message(FATAL_ERROR "LLVM_ROOT (${LLVM_ROOT}) is not a valid LLVM install") endif() # We incorporate the CMake features provided by LLVM: set(CMAKE_MODUL...

...our patch. I won't be able to look at it in > more detail until this weekend, but perhaps you can address a couple of > concerns: > > 1. I don't understand the need for LLVMToolDirSlash. This seems like a > gratuitous change to me. If LLVM_OBJ_ROOT (with LLVM_SRC_ROOT) and LLVM_ROOT both not set without LLVMToolDirSlash we will have "/gccas$(EXEEXT)", for example. This is not problem for project that not use LLVM tools and libs. But this not permite one useful case: project that use only LLVM tools and LLVM tools directory added to PATH. In this case using LLVMToolD...

...ss is stored in two files: X.cpp and X.h The class X works perfectly in a pass that I already have. However, I need to use that class in some other passes, but I don't want to have a copy of X.cpp and X.h in every pass folder. I've tried to do the following: - put X.h in the folder <llvm_root>/include/lllvm/Analysis - put X.cpp in the folder <llvm_root>/lib/Analysis - go to <llvm_root> and execute "make", to compile everything again, with my new files - change the includes of my passes to replace #include "X.h" by #include "llvm/Analysis/X.h...

...t class is stored in two files: X.cpp and X.h The class X works perfectly in a pass that I already have. However, I need to use that class in some other passes, but I don't want to have a copy of X.cpp and X.h in every pass folder. I've tried to do the following: - put X.h in the folder <llvm_root>/include/lllvm/Analysis - put X.cpp in the folder <llvm_root>/lib/Analysis - go to <llvm_root> and execute "make", to compile everything again, with my new files - change the includes of my passes to replace #include "X.h" by #include "llvm/Analysis/X.h"...

...Zakir via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Is there no one who has already built LLVM for targeting WebAsesembly > with, using Visual Studio 2017 as the generator and toolchain (x64 of > course)? > > My LLVM root folder is C:/llvm, and LLD and Clang are in > llvm_root/tools/lld and llvm_root/tools/clang respectively. If this is as > it should be, then what's the problem? Would someone please help me with > this by also checking the logs I've attached to the first message in this > thread? Thanks in advance. > > In llvm/tools/, I see ther...

Yeah, I don't think that matters. It did set the toolset architecture to x64. You know, I attached those log files for a reason. ________________________________ From: Zachary Turner <zturner at google.com> Sent: Tuesday, November 27, 2018 4:27 AM To: Osman Zakir Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] Have LLD and Clang in their correct locations, but still can't

...oconf (or ./configure). Is there cmake >>> > based sample project available? >>> > I could not find any from official release. Has any of you written >>> sample >>> > project template that uses cmake? >>> >>> Just make a directory under LLVM_ROOT/projects and put your source >>> there, with a CMakeLists.txt file that contains the right directives >>> (you can use any of the llvm tools or libraries under LLVM_ROOT/tools or >>> LLVM_ROOT/lib as an example.) After creating those files, you must >>> re-invoke...