similar to: check_include_file not respecting CMAKE_PREFIX_PATH

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

My build process: $ cd llvm/ $ mkdir build $ cd build $ cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/local -DCMAKE_PREFIX_PATH=$HOME/local -DCMAKE_BUILD_TYPE=Release -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD="WebAssembly;AVR;RISCV" -DLLVM_ENABLE_LIBXML2=OFF $ make install $ cd clang/ $ mkdir build $ cd build $ cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/local -DCMAKE_PREFIX_PATH=$HOME/local

I am trying to build Clang/LLVM with -DLLVM_BUILD_LLVM_DYLIB=ON and -DLLVM_LINK_LLVM_DYLIB=ON to reduce the size of toolchain. I am getting LINK error 1181 about `lib\LLVM.lib` not found. After investigating, `lib\LLVM.lib` is supposed to be produced along with `bin\LLVM.dll`. `bin\LLVM.dll` is indeed produced, but it does not contain any exported symbols (10KB only) because LLVM does not use

I ran CMake on the command line with this command: " cmake .. -DCMAKE_INSTALL_PREFIX=../install_x64 -T host=x64 -G "Visual Studio 15 2017 Win64" -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly " And I have LLD and Clang where they should be. But I still couldn't generate project files. The path to the build and installation directories don't have spaces at all this

I'm using CMake version 3.12.3 on Windows 10 Home. I checked out LLVM, Clang, Clang extra tools, Compiler-RT, LLD, LibOMP, LIBCXX, and LIBCXXABI with SVN and am now trying to generate project files. But LLD, among some other things, wasn't found (even though put all of those in the documented directories inside the LLVM source tree). And a lot of the tests failed. I'm attaching the

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

@Jonathan Goodwin: Do I have to use a flag to tell it where the LLVM include files are? And would it be easier to do that in the CMake GUI? Please tell me how you had it find the include files if that may help me. ________________________________ From: Jonathan Goodwin <jondgoodwin at gmail.com> Sent: Wednesday, November 28, 2018 6:24 AM To: zturner at google.com Cc: Osman Zakir; llvm-dev

I think most people are using ninja to do the build. You can still use the Visual Studio generator for the IDE experience while doing build from ninja. I know there are a couple of people who build from inside of Visual Studio, but it's a pretty small number, and I don't think they are targeting WebAssembly. On Tue, Nov 27, 2018 at 12:46 PM Osman Zakir via llvm-dev < llvm-dev at

On Thu, Mar 20, 2014 at 10:12 PM, Greg Fitzgerald <garious at gmail.com> wrote: > > ExternalProject_Add(compiler-rt ...) > > So that was quite the experiment. Looking at > clang/runtime/CMakeLists.txt, I'm not seeing a lot of bang for buck > here, and it looks like this file is prone to bit rot. Could you please elaborate on this? In fact, I don't plan to give

Hello. Excuse me. Why CMakeLists.txt from llvm-3.9.1.src does not contain WebAssembly target? So, it is like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ X86 XCore ) but not like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ Webassembly X86

Hi Greg, On Fri, Mar 21, 2014 at 11:18 PM, Greg Fitzgerald <garious at gmail.com> wrote: > Hi Alexey, > > CMAKE_PREFIX_PATH is a convenient mechanism for exposing prebuilt > install directories to a CMake build. It contains a colon-separated > list of paths. Each path points to a directory that contains > directory names that are meaningful to CMake, including

On Tue, Apr 25, 2017 at 02:35:26PM +0300, Pavel Butsykin wrote: > The patch changes the order of the steps to search for fixed/supermin > appliance in accordance with documentation: > > "If the fixed appliance is found, libguestfs skips supermin entirely > and just runs qemu with the kernel, initrd and root disk from the > fixed appliance." Does anyone rely on the

On 06/25/2012 12:50 AM, Mihai Basa wrote: > Hello all, > > Is there a reason why the library location code in cindex py does not > use find_library() to locate libclang, like in the attached patch? > > Without it there were problems locating a versioned libclang.so.1 file > on Debian, for example. Hi Mihai, as this is a clang related question, I move your mail to the clang

What is the purpose of supporting this "copy directories around" sort of build strategy anyway? At the end of the day, the way these packages get installed is via system package managers is independently, each project finding its dependencies with the standard prefix path. When I compile from source it's always like this: $ cd llvm-6.0.0rc2.src/ $ mkdir build $ cd build $ cmake ..

On Wed, Feb 26, 2014 at 9:58 PM, Brad King <brad.king at kitware.com> wrote: > On 02/26/2014 12:43 PM, Alexey Samsonov wrote: > > Do you think it makes sense to land my ExternalProject_Add patch > > so that others can experiment with it? I can add quit with a > > fatal_error/warning if the build tree rules are generated with Ninja. > > Since it is conditional on

I have what I hope is a simple question regarding a security practice I''ve been using in my first Rails app. I want to know if it''s worthwhile or if the extra typing isn''t worth it. I have 3 models that are related to each other. class User < AR:Base has_one :library end class Library < AR:Base belongs_to :user has_many :items end class Item < AR:Base

Fixing llvm-dev at llvm.org to llvm-dev at lists.llvm.org On Tue, Nov 17, 2020 at 11:27 AM Thomas Lively <tlively at google.com> wrote: > Thanks for your work on this, Paulo! > > Here's some more detail about how function pointers work today in the > WebAssembly backend and how they differ from the `funcref` Paulo is > working on. > > Today in the WebAssembly

To get into more detail, I'm trying to update WebAssembly's `call` instruction. `call` is currently constrained to return one or zero arguments, so in TableGen we have a separate call Instruction for each possible return type. But I need to update calls to return arbitrarily many values of any combination of WebAssembly types, so even if we imposed some reasonable artificial limit like 8

Hello all, Is there a reason why the library location code in cindex py does not use find_library() to locate libclang, like in the attached patch? Without it there were problems locating a versioned libclang.so.1 file on Debian, for example. Cheers, Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL:

> > If you want to do a minimal build of libvirt you can run meson with > --auto-features=disabled which will disable most of the features and you > can explicitly enable only the things that you want to use (this is what > most distributions are doing when building packages). I just noticed > that there are some build options where this doesn't work so I'll post >