similar to: [LLVMdev] Fixing LLVM's CMake interface before LLVM3.5 release

>> I am happy to start writing a patch for the documentation > > Thanks. Please Cc me for review. Will do. >> # LLVM_BUILD_* values available only from LLVM build tree. > > Those were created to simplify building Clang locally against a > LLVM build tree. Clang needs the LLVM source and build trees too, > so this gives it that information. No information is

> Run it through its phases and report any bugs you find! [ 1495s] CMake Warning (dev) at projects/dragonegg/CMakeLists.txt:34 (get_target_property): [ 1495s] Policy CMP0026 is not set: Disallow use of the LOCATION target property. [ 1495s] Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy [ 1495s] command to set the policy and suppress this warning. [

Hi all, Recently I have implemented a transformation pass based on LLVM3.5 and its function is to duplicate the function's argument list in a bytecode file and replace all use of original function with modified function. In LLVM3.5, the pass can work properly. However, when I tried to transplant the pass to LLVM3.9, the error "Argument value does not match function argument type!"

Hi again, I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and did a slight rewrite of my CMakeLists.txt file for building the C code. Problem is, cmake no longer finishes at all. I receive the following output, and then it just runs forever (while still responding to a CTRL-C): > eli at

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

Eli Gottlieb <eligottlieb at gmail.com> writes: > I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To > do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and > did a slight rewrite of my CMakeLists.txt file for building the C > code. > > Problem is, cmake no longer finishes at all. I receive the > following output, and then

Greetings, I have a simple C++ EDSL working using the JIT execution engine. When I upgraded to LLVM 3.2 (effortless upgrade, awesome stuff!) I thought I would try taking the MCJIT for a spin after having read that the JIT is considered to be "legacy". So the changes I made to my code were: + #include <llvm/ExecutionEngine/MCJIT.h> - #include <llvm/ExecutionEngine/JIT.h> +

On 1/19/2013 2:39 AM, Óscar Fuentes wrote: > Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > >> We want to compile LLVM/Clang and use the resulting >> headers/libraries in our project. But we compile it during out build >> process. I can build LLVM/Clang by adding it to our cmakelists.txt but >> when our code tries to use one of the headers >>

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 clang > libraries? AFAIK, there is no such feature for Clang.

On 1/21/2013 10:25 AM, Ashok Nalkund wrote: > 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

On 01/17/2016 02:53 PM, Dan Liew wrote: > @Brad: CC'ing you because I know you use > ``llvm_map_components_to_libnames()`` so you will likely have > something to say about it breaking. I'm using it in CastXML but that could easily be adapted to something different if needed. The larger concern is that that API is the documented way to use LLVM in an application with CMake so

This is just standard behavior of the Python interpreter. The files are just a cache (it is not the sources being modified) and also won't be written if the source tree is made read only, and shouldn't cause a problem in practice. - Daniel On Jan 22, 2013, at 0:02, Duncan Sands <baldrick at free.fr> wrote: > I would have expected the .pyc files to go in the objects directory.

[Please CC the mailing list] Eli Gottlieb <eligottlieb at gmail.com> writes: > OK, I'm just going to paste in my CMakeLists.txt file. Like I said, > I'm building an LLVM install myself by untarring llvm, mkdir build in > the root dir of the source, cd build/, cmake .., make. > >> cmake_minimum_required (VERSION 2.6) >> project (libjllvm) >>

Ashok Nalkund <ashoknn at qti.qualcomm.com> writes: > We want to compile LLVM/Clang and use the resulting > headers/libraries in our project. But we compile it during out build > process. I can build LLVM/Clang by adding it to our cmakelists.txt but > when our code tries to use one of the headers > (clang/CodeGen/ModuleBuilder.h), its not found as it doesnt exist. If > I

Hi All, We want to compile LLVM/Clang and use the resulting headers/libraries in our project. But we compile it during out build process. I can build LLVM/Clang by adding it to our cmakelists.txt but when our code tries to use one of the headers (clang/CodeGen/ModuleBuilder.h), its not found as it doesnt exist. If I do a 'make install' in the llvm directory, then the file is

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

Currently, cmake policies are manually maintained by each project. This is done via a set of `cmake_policy()` commands following the initial `cmake_minimum_required()` command at the top of each CMakeLists.txt project file. Somewhat surprisingly, these sets are local to each project and independent of each other -- even for in-tree builds containing multiple sub-projects. This is because cmake

Hello; I am working on porting a tool written for LLVM3.5 to LLVM10. There used to be a call instruction with the signature static CallInst * Create (Value *F, Value *Actual, const Twine &NameStr="", Instruction *InsertBefore=0) Can anyone please explain what it supposed to do? What was F and Actual? Thank you so much. -- Dr. Arnamoy Bhattacharyya R&D Compiler Engineer

Dear all, I am trying to move a project from Linux to OSX, with bad results at my first attempt. First, I am using LLVM 3.2, the latest version, compiled from sources (configured with just the install prefix, vanilla for other 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