search for: prop_tgt

Hi dear list, I tried to build llvm+clang on an OpenSuse BuildServer for ARM. The build was carried out with CMake 2.8.11. In the installation step I got the following error: > [26815s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/llvm-3.4.99-336.1.arm/usr/lib/libLLVMSupport.so > [26815s] CMake Error at lib/Support/cmake_install.cmake:45 (FILE): > [26815s] file RPATH_CHANGE could

...with no special environment by using RPATH/RUNPATH. > Then at installation time it has a builtin ELF editor that replaces > the build-tree RPATH with one for the install tree as specified by > the INSTALL_RPATH target property: > > http://www.cmake.org/cmake/help/v2.8.12/cmake.html#prop_tgt:INSTALL_RPATH > > When the desired install-tree RPATH is longer than the build tree > one then CMake adds bogus content to the end of the RPATH value for > the build tree to reserve space. > > I'm not familiar with the tools for the platform in question, but > some linker...

A couple of llvm sub-projects have been failing to build for me for a while (compiler-rt asan and util/unittests, at least). It turns out to be due to the fact that some paths on my system include spaces and other special characters, but the the build.ninja file was not generated with correctly quoted strings. Specifically I'm on OS X and the command is setting -isysroot to a location inside

LLVM currently has CMake code to try to detect the various options needed to compile with C++11 support that has been around since prior to the CMake version bump. One of the nicer features that came with the newer required CMake version is that very thing. Rather than try to discern this yourself CMake has the CXX_STANDARD and CXX_STANDARD_REQUIRED target properties. If set appropriately on a

...target property was a very early CMake feature > and is treated as a raw string to put on the command line. That > is why it needs manual escaping. > > CMake 2.8.12 added the COMPILE_OPTIONS property and supporting command: > > http://www.cmake.org/cmake/help/v2.8.12/cmake.html#prop_tgt:COMPILE_OPTIONS > http://www.cmake.org/cmake/help/v2.8.12/cmake.html#command:target_compile_options > > The property holds a ;-list of options to be passed to the compiler. > CMake handles conversion to a command-line string with all needed > escaping. > > -Brad >

I have just committed support to llvm-ar for creating thin archives. The idea of thin archives is that they contain just the symbol table and the path to find the original .o files. By locally making thin archives the default I was able to build llvm+lld+clang with them. The total size of the .a files goes from 181,658,164 to 7,116,900 bytes. Is there any way to do that with cmake without having

> On Dec 4, 2018, at 10:59 AM, George Burgess IV <george.burgess.iv at gmail.com> wrote: > > > I think people are too eager to use `auto` because it is easy to write but it makes the types substantially harder for the reader to understand > > I'm probably the Nth person to ask this, but what keeps us from promoting the use of a clang-tidy-powered tool that basically