search for: dcmake_prefix_path

...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 .. -DCMAKE_INSTALL_PREFIX=$HOME/local -DCMAKE_PREFIX_PATH=$HOME/local -DCMAKE_BUILD_TYPE=Release $ make install $ cd cfe-6.0.0rc2.src/ $ mkdir build $ cd build $ cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/local -DCMAKE_PREFIX_PATH=$HOME/local -DCMAKE_BUILD_TYPE=Release $ make install $ cd lld-6.0.0rc2.src/ $ mkdir build $ cd build $ cmake .. -DCMAKE_INSTALL_...

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 -DCMAKE_BUILD_TYPE=Release $ mak...

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

...ect is not added to the install directory and the test suites are not built. Is this a build configuration you'd consider using? $ cmake -G Ninja .. \ -DCMAKE_INSTALL_PREFIX=ship \ -DCMAKE_C_COMPILER=arm-linux-androideabi-gcc \ -DCMAKE_CXX_COMPILER=arm-linux-androideabi-g++ \ -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship \ -DANDROID=1 \ -DCMAKE_SYSTEM_NAME=Linux \ -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm \ -DCMAKE_CXX_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm ... $ ninja install ... [68/68] -- Install configuration: "Release"...

...end up with a top-level > build that performs the following: > > mkdir -p llvm/out && cd llvm/out > cmake .. -DCMAKE_INSTALL_PREFIX=ship > ninja check-all install > cd - > > mkdir -p compiler-rt/out && cd compiler-rt/out > cmake .. -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship > -DCMAKE_INSTALL_PREFIX=ship > ninja check-all install > cd - > > mkdir -p clang/out && cd clang/out > cmake .. > -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship:`pwd`/../../compiler-rt/out/ship > -DCMAKE_INSTALL_PREFIX=ship...

On 15 Feb 2018, at 15:45, Siegmar Gross via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > today I've tried to build llvm-6.0.0rc2 using Cmake on my "SUSE Linux > Enterprise Server 12.3 (x86_64)" with the following commands (gcc-6.4.0 > is necessary for CUDA-9.0). > > > wget http://prereleases.llvm.org/6.0.0/rc2/llvm-6.0.0rc2.src.tar.xz > wget

...are not built. Is >> this a build configuration you'd consider using? >> >> $ cmake -G Ninja .. \ >> -DCMAKE_INSTALL_PREFIX=ship \ >> -DCMAKE_C_COMPILER=arm-linux-androideabi-gcc \ >> -DCMAKE_CXX_COMPILER=arm-linux-androideabi-g++ \ >> -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship \ >> -DANDROID=1 \ >> -DCMAKE_SYSTEM_NAME=Linux \ >> -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm \ >> -DCMAKE_CXX_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm >> ... >> $ ninja install &gt...

...;> > >> mkdir -p llvm/out && cd llvm/out > >> cmake .. -DCMAKE_INSTALL_PREFIX=ship > >> ninja check-all install > >> cd - > >> > >> mkdir -p compiler-rt/out && cd compiler-rt/out > >> cmake .. -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship > >> -DCMAKE_INSTALL_PREFIX=ship > >> ninja check-all install > >> cd - > >> > >> mkdir -p clang/out && cd clang/out > >> cmake .. > >> > -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship...

Hi, today I've tried to build llvm-6.0.0rc2 using Cmake on my "SUSE Linux Enterprise Server 12.3 (x86_64)" with the following commands (gcc-6.4.0 is necessary for CUDA-9.0). wget http://prereleases.llvm.org/6.0.0/rc2/llvm-6.0.0rc2.src.tar.xz wget http://prereleases.llvm.org/6.0.0/rc2/cfe-6.0.0rc2.src.tar.xz wget

...ration you'd consider using? >>>> >>>> $ cmake -G Ninja .. \ >>>> -DCMAKE_INSTALL_PREFIX=ship \ >>>> -DCMAKE_C_COMPILER=arm-linux-androideabi-gcc \ >>>> -DCMAKE_CXX_COMPILER=arm-linux-androideabi-g++ \ >>>> -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship \ >>>> -DANDROID=1 \ >>>> -DCMAKE_SYSTEM_NAME=Linux \ >>>> -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm \ >>>> -DCMAKE_CXX_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm >>&...

$ file /home/andy/misc/bootstrap/out/native/include/zlib.h /home/andy/misc/bootstrap/out/native/include/zlib.h: C source, ASCII text $ cmake /home/andy/misc/bootstrap/llvm-6.0.0.src -DCMAKE_PREFIX_PATH=/home/andy/misc/bootstrap/out/native -DCMAKE_INSTALL_PREFIX=/home/andy/misc/bootstrap/out/native -DCMAKE_BUILD_TYPE=Release -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly; \ -- Looking for zlib.h - not found I propose to use find_path and find_library instead of check_include_file. Shall I s...

...> >> >>>> $ cmake -G Ninja .. \ >> >>>> -DCMAKE_INSTALL_PREFIX=ship \ >> >>>> -DCMAKE_C_COMPILER=arm-linux-androideabi-gcc \ >> >>>> -DCMAKE_CXX_COMPILER=arm-linux-androideabi-g++ \ >> >>>> -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship \ >> >>>> -DANDROID=1 \ >> >>>> -DCMAKE_SYSTEM_NAME=Linux \ >> >>>> -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm >> >>>> \ >> >>>> >> >>&g...

I've been building clang on linux for a couple of years now, contributing to the testing on Ubuntu, but this one has me stumped: fatal error: 'asm/socket.h' file not found #include <asm/socket.h> [1556/4006] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.i386.dir/sanitizer_platform_limits_posix.cc.o FAILED:

...ke -G Ninja .. \ > >>> >>>> -DCMAKE_INSTALL_PREFIX=ship \ > >>> >>>> -DCMAKE_C_COMPILER=arm-linux-androideabi-gcc \ > >>> >>>> -DCMAKE_CXX_COMPILER=arm-linux-androideabi-g++ \ > >>> >>>> -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship \ > >>> >>>> -DANDROID=1 \ > >>> >>>> -DCMAKE_SYSTEM_NAME=Linux \ > >>> >>>> > -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm > >>> >>>> \ > &gt...

Just to follow-up, I'm now encountering this as well. I'm doing this on Linux. It seems that when linking with the most-recently built clang, the unit tests are taking a while to complete. It's notably not using more than 1 thread, and if using `lld` I would have expected the linker to still be running in parallel. I'm doing this on a debug build, so that might help narrow it

...50 branch of git, sha1: f1d5723be3f9456a6b16cdf687847ac2918846de Using gcc 7.2.0 from homebrew. $ CC=/usr/local/opt/gcc/bin/x86_64-apple-darwin16.7.0-gcc-7 CXX=/usr/local/opt/gcc/bin/x86_64-apple-darwin16.7.0-g++-7 cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/Users/andy/local/llvm5 -DCMAKE_PREFIX_PATH=/Users/andy/local/llvm5 $ make VERBOSE=1 [ 92%] Linking CXX executable ../../bin/bugpoint cd /Users/andy/Downloads/llvm-project/llvm/build/tools/bugpoint && /usr/local/Cellar/cmake/3.7.2/bin/cmake -E cmake_link_script CMakeFiles/bugpoint.dir/link.txt --verbose=1 /usr/local/opt/gcc/bin/x86_6...

...gt;> >>>> -DCMAKE_INSTALL_PREFIX=ship \ > >> >>> >>>> -DCMAKE_C_COMPILER=arm-linux-androideabi-gcc \ > >> >>> >>>> -DCMAKE_CXX_COMPILER=arm-linux-androideabi-g++ \ > >> >>> >>>> -DCMAKE_PREFIX_PATH=`pwd`/../../llvm/out/ship \ > >> >>> >>>> -DANDROID=1 \ > >> >>> >>>> -DCMAKE_SYSTEM_NAME=Linux \ > >> >>> >>>> > >> >>> >>>> > -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/plat...

I saw this change come in yesterday: commit 572ad839e2f66eaa82ffc71b1061eb3d06a4d126 Author: Saleem Abdulrasool <compnerd at compnerd.org> Date: Thu Jun 15 20:39:58 2017 +0000 COFF: add support for lib mode usage When link is invoked with `/def:` and no input files, it behaves as if `lib.exe` was invoked. Emulate this behaviour, generating the import library from the