similar to: [LLVMdev] Building LLVM with CMake

I am using LLVM as back end for my compiler, and until now I have used my own CMake build system for LLVM. But now LLVM has a CMake build system of its own, so when upgrading my LLVM version I decided to move to the 'official' one. It's not an easy transition, the build fails. I already found one bug: in some files the variable CMAKE_SOURCE_DIR is used for the LLVM top-level source

On Sat, Nov 1, 2008 at 12:50 AM, Chris Lattner <clattner at apple.com> wrote: > > On Oct 31, 2008, at 2:04 PM, Óscar Fuentes wrote: >> There is no reason to include the CMake build system on this >> release. It >> is undocumented and immature. >> >> Please remove the cmake/ directory and all files named CMakeLists.txt >> from the LLVM source tree.

[I'm cc-ing the mailing list because there are some topics here of general interest] HyperQuantum <hyperquantum at gmail.com> writes: >> CMAKE_SOURCE_DIR should be the same as LLVM_MAIN_SRC_DIR. If you know an >> scenario where this is not true, please describe it. > > In my case it's not true. I have put LLVM in a subdirectory of my > project

Hi! I'm porting my own projects to CMake (seems very cool) and I want to import LLVM as external libraries. To simplify this CMake supports an export feature that can export an LLVM.cmake file that lists all libraries of LLVM. With this I could simplify the use of LLVM in my own CMake project. For this the following cmake files of LLVM have to be extended (patches are provided at the end of

Hi, I'm trying to build LLVM 5.0.1 with all components on ARM host. I'm not cross-compiling so everything is done natively. I use the following cmake options : cmake -G "Unix Makefiles" .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_C_FLAGS="-march=armv7-a -mcpu=cortex-a9" -DCMAKE_C_COMPILER_TARGET=arm-linux-gnueabi

Óscar Fuentes <ofv at wanadoo.es> writes: > Yep, llvm_map_components_to_libraries gets confused by the existence of > both gtest and gtest_main and enters an infinite loop. A workaround is > to not pass "all" to llvm_map_components_to_libraries but a list of > required components. This patch *seems* to fix the problem (cmake regexps are not thoroughly documented):

Hello Everyone I have just pulled an updated llvm from svn. When I try to use cmake now on llvm I have just started to get errors. Anyone have any ideas? I am using Windows 7 64 and cmake and ninja and mingw. What appears to be the relevant part of the message is below: ... -- Clang version: 3.3 CMake Error: File c:/llvm/tools/clang/include/clang/Basic/Version.inc.indoes not exis CMake Error at

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > >>>> Isn't is possible for cmake just to glob everything in the corresponding >>>> directory? >>>> >>>> >>> Yes, but then the build would not notice a change on the file >>> structure. You'll need to explicitly invoke

Kenneth Boyd <zaimoni at zaimoni.com> writes: >>> Isn't is possible for cmake just to glob everything in the corresponding >>> directory? >>> >> >> Yes, but then the build would not notice a change on the file >> structure. You'll need to explicitly invoke cmake for being sure that >> whatever changes were made by the last svn

Ah, thank you so much. How did you get the list of target_link_libraries() ? Did you use llvm-config? If you did not have access to llvm-config, how would you get list of libraries to link to? Thanks. Sam On Sun, Jun 13, 2010 at 2:44 PM, Nathan Jeffords <blunted2night at gmail.com>wrote: > This isn't meant to be a sample, but I can share with you the cmake files I > use for my

Hi Óscar, Thank you for the reply. I indeed got an impression (may be incorrect) that projects/ directory is intended for users' projects that are not committed to LLVM repository. Otherwise, of course, the patch doesn't make much sense. Anyway, I've added a comment about the need of explicit CMake invocation to projects/CMakeLists.txt. Thanks, Victor -----Original Message-----

Hi All, The proposed patch makes possible to use LLVM's CMake build infrastructure (most importantly add_llvm_library and add_llvm_executable macros) from the project that has llvm in a subdirectory. For example: demo/ llvm/ demo.cpp CMakeLists.txt where CMakeLists.txt is as follows: # ----------------------------- Start of CMakeLists.txt

I built the list by hand though trial and error. I'm not sure if and how llvm-config works with cmake. Its seems now that I got the right dependencies in the right order, there have been no ongoing maintenance issues. On Sun, Jun 13, 2010 at 4:32 PM, sam lee <skynare at gmail.com> wrote: > Ah, thank you so much. > How did you get the list of target_link_libraries() ? > Did you

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

This isn't meant to be a sample, but I can share with you the cmake files I use for my compiler. It builds in both windows user MSVC, and linux using G++, but should work with MinGW. the structure is src/ CMakeLists.txt # root make file front/ CMakeLists.txt # library middle/ CMakeLists.txt # library back/ CMakeLists.txt # library npp/ CMakeLists.txt # executable

"Viktar Zviarovich" <Viktar.Zviarovich at brunel.ac.uk> writes: > The suggested patch enables addition of all subdirectories of > llvm/projects to CMake build. > > It somewhat simplifies the process of creating new projects that use > CMake instead of make, eliminating the need of editing > llvm/CMakeLists.txt and llvm/projects/CMakeLists.txt. This is not

On Tue, Nov 17, 2020 at 10:25 AM Luke Drummond via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all > > I wanted to do a quick build of a clean branch yesterday and noticed > something surprising in the configure log: > > > -- No build type selected, default to Debug > > It appears that llvm's configuration forces Debug builds if the user > does

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

Just trying to understand: Are you suggesting a way to have a “-O0” build without all the debug information? -Min > On Nov 17, 2020, at 10:25 AM, Luke Drummond via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all > > I wanted to do a quick build of a clean branch yesterday and noticed > something surprising in the configure log: > >> -- No build type

I'm curious how much of this is due to not using LLD? Last I checked, using ld.bfd instead of LLD (or gold) was one of my major build time issues, and somehow our default configuration would use ld.bfd. -- Sean Silva On Tue, Nov 17, 2020 at 10:25 AM Luke Drummond via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi all > > I wanted to do a quick build of a clean branch