search for: cmake_install_prefix

...39; can not be used when making a shared object; recompile with -fPIC ../../lib/libLLVMX86CodeGen.a: could not read symbols: Bad value collect2: error: ld returned 1 exit status I am not sure how to proceed from here.. Thanks, Frank SRC=$HOME/svn/llvm-3.8 CMAKE_BUILD_TYPE="Debug" CMAKE_INSTALL_PREFIX="$HOME/toolchain/install/llvm-3.8" LLVM_TARGETS_TO_BUILD="X86" CXX="/dist/gcc-4.8.2/bin/g++" CC="/dist/gcc-4.8.2/bin/gcc" #-DBUILD_SHARED_LIBS="ON" \ cmake -G "Unix Makefiles" \ -DCMAKE_CXX_FLAGS="-fno-rtti" \ -DCMAKE_C_FLAGS...

I just checkout release_38 branches of llvm, clang and polly and built it on and x86 Ubuntu with cmake: CMAKE_BUILD_TYPE="Debug" CMAKE_INSTALL_PREFIX="$HOME/toolchain/install/llvm-3.8" LLVM_TARGETS_TO_BUILD="X86" cmake -G "Unix Makefiles" \ -DBUILD_SHARED_LIBS="ON" \ -DCMAKE_BUILD_TYPE=$CMAKE_BUILD_TYPE \ -DCMAKE_INSTALL_PREFIX=$CMAKE_INSTALL_PREFIX \ -DLLVM_TARGETS_TO_BUILD=$LLVM_TARGETS_TO_BUILD \ $SRC...

...kay, the documentation has come a long way since 3.0 although it still needs a bit of polish. > I wouldn't say that much "important functionality is plain lacking", > it probably just isn't documented that well. See the following. > Installation prefix is set using the CMAKE_INSTALL_PREFIX cache > variable. You can set it at configure time, > > $ cmake -DCMAKE_INSTALL_PREFIX=$HOME/root/usr/local /path/to/llvm/src Correct, but I cannot set it as a default in a configuration file so I need to specify it for every single package that I compile every time I configure it. I th...

...rs and libraries. Cmake version is 2.8.12.2 cmake -G "Visual Studio 12" -D LLVM_TARGETS_TO_BUILD:STRING=%TARG% -D TARGET_TRIPLE:STRING=%TRIPLE% -D LLVM_DEFAULT_TARGET_TRIPLE:STRING=%TRIPLE% -D LLVM_TARGET_ARCH:STRING=%TRIPLE% -D LLVM_ENABLE_PIC:BOOL=ON -D LLVM_ENABLE_ASSERTIONS:BOOL=ON -D CMAKE_INSTALL_PREFIX=%win_top_install_dir% -D CMAKE_BUILD_TYPE=%BLDMODE% -DLLVM_APPEND_VC_REV:BOOL=ON -D LLVM_VENDOR_NAME:STRING=%NAME% -D LLVM_VENDOR_VERSION:STRING=%VER% %win_top_src_dir%/llvm As far as I know, cmake tries to compile a simple file with "#include <zlib.h>" with MSbuild.exe which invo...

I am an actual end user of LLVM who builds it from source and not a developer of it so I think I have an important perspective that is not represented here. Also I am pretty sure the llvmdev mailing is heavily biased and might not reach actual end users of LLVM. I use the Autotools build system for a number of reasons. If compromises or reasonable workarounds could be found I would be okay with

...> 2) The "clang/runtime" build calls ExternalProject once for each arch > it needs of compiler-rt. So once to create x86_64 libs and once for > i386 libs. > > 3) The compiler-rt build drops the ${arch} suffix from its libs, and > the "clang/runtime" build uses CMAKE_INSTALL_PREFIX to control where > the compiler-rt libs go. > > "CMAKE_INSTALL_PREFIX=${CMAKE_CURRENT_BINARY_DIR}/lib/clang/${CLANG_VERSION}/x86_64-linux" > > 4) Remove multi-arch support from the compiler-rt build. Instead, > declare compiler-rt as an "any-arch" build, conf...

Hello All, I wanted to convert .html file into .pdf. is there any rails plugin ?? Thanks, Sandip R~ -- Ruby on Rails Developer http://sandip.sosblog.com http://funonrails.wordpress.com www.joshsoftware.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

...that llvm is installed complicates things. >> >> >> >> Sorry for the confusion. By "llvm install directory", I don't mean to >> >> install llvm to the root directory. I'm referring to the intermediary >> >> directory pointed to by CMAKE_INSTALL_PREFIX. When you run "ninja >> >> install", the build populates this directory with only the libs, >> >> headers, docs, and executables that the LLVM build intends customers >> >> to use directly. In the case of compiler-rt, we need LLVM's >> >&...

...-jN-stable gnu make on mingw. (Lemme know if you knew better version of make!) - Why don't you mention "make {check|clang-test|check-all}", despite of introducing gnuwin32? - You forgot to mention a few important cmake variables. - CMAKE_BUILD_TYPE=Release (for most purpose) - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed onto C:\PROGRA~1\?) - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from llvm source tree - PYTHON_EXECUTABLE, if %PATH% does not contain python. - Consider to...

...alls ExternalProject once for each arch > >> it needs of compiler-rt. So once to create x86_64 libs and once for > >> i386 libs. > >> > >> 3) The compiler-rt build drops the ${arch} suffix from its libs, and > >> the "clang/runtime" build uses CMAKE_INSTALL_PREFIX to control where > >> the compiler-rt libs go. > >> > >> > "CMAKE_INSTALL_PREFIX=${CMAKE_CURRENT_BINARY_DIR}/lib/clang/${CLANG_VERSION}/x86_64-linux" > >> > >> > >> 4) Remove multi-arch support from the compiler-rt build. Instead,...

...to install and use clang and the required headers and libraries, without having to build from scratch. The install path for a given user would be, e.g., /home/USERNAME/build/common/ So for example, clang would be installed to /home/USERNAME/build/common/bin. When I did my initial build, I set -DCMAKE_INSTALL_PREFIX to the "common" path above, but the Makefiles and cmake_makefiles that were generated have a full path (/home/dlobron/build/common), which of course is not portable to other users if they were to do a "make install". Is it possible to set DCMAKE_INSTALL_PREFIX (or another varia...

...lly. > > As I understand it, clang expects to find the compiler-rt libraries > relative to the resource directory, which you can find out the > location of with clang --print-resource-dir . By default it is > lib/clang/9.0.0 assuming you are building from master. I think that > -DCMAKE_INSTALL_PREFIX=/usr has broken that assumption. I think that > you would either need to take out the CMAKE_INSTALL_PREFIX or change > the location of the resource directory, which I think that you can > alter at build time. > You're right, I've just checked both packages in Alpine and Arch a...

...once for each arch >> >> it needs of compiler-rt. So once to create x86_64 libs and once for >> >> i386 libs. >> >> >> >> 3) The compiler-rt build drops the ${arch} suffix from its libs, and >> >> the "clang/runtime" build uses CMAKE_INSTALL_PREFIX to control where >> >> the compiler-rt libs go. >> >> >> >> >> "CMAKE_INSTALL_PREFIX=${CMAKE_CURRENT_BINARY_DIR}/lib/clang/${CLANG_VERSION}/x86_64-linux" >> >> >> >> >> >> 4) Remove multi-arch support from the c...

...>> andrey > Andrey, > There is one issue with the proposed patch at > http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20150511/129075.html > with regard to finding the installed libiomp5.dylib for linkage. If > the cmake build of llvm/clang/opemmp uses > -DCMAKE_INSTALL_PREFIX=/sw/opt/llvm-3.7, the -fopenmp option fails to > find the libiomp5.dylib installed in /sw/opt/llvm-3.7/lib for > linkage... > > % clang-3.7 -fopenmp -o omp_getEnvInfo omp_getEnvInfo.c -v > clang version 3.7.0 (trunk) > Target: x86_64-apple-darwin14.4.0 > Thread model: posix &gt...

On 02/03/2016 11:06 AM, Tobias Grosser wrote: > On 02/03/2016 04:46 PM, Frank Winter via llvm-dev wrote: >> >> >> On 02/03/2016 10:41 AM, Tobias Grosser wrote: >>> On 02/03/2016 04:37 PM, Frank Winter wrote: >>>> Hi Tobias, >>>> >>>> I tried to invoke other passes and none of them are available, e.g.: >>>>

On Wed, Aug 27, 2014 at 4:29 PM, Mueller-Roemer, Johannes Sebastian <Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote: > prefix = CMAKE_INSTALL_PREFIX > enabled-shared = BUILD_SHARED_LIBS > targets = LLVM_TARGETS_TO_BUILD (defaults to all, or use a semicolon separated list) > disable-assertions = LLVM_ENABLE_ASSERTIONS (obviously inverted ;) > > I don't believe the others have direct equivalents, however debug/optimized is chos...

...able, > eg, when installed under /lib/llvm I just later need to move the > installation tree to /lusr/local/lib/llvm without re-run cmake and the > time-boring build/install process, and this is especially convinient on > Windows. LLVM_INSTALL_PREFIX is supposed to contain the value of CMAKE_INSTALL_PREFIX when you configured LLVM. Using it for setting other variables is just a convenience. > Use CMAKE_CURRENT_LIST_DIR while not the absolute predefined > LLVM_INSTALL_PREFIX is just to give the freedom to this, if just installed and > not moved, this will work identical to the value original...

...t; know if you knew better version of make!) > > - Why don't you mention "make {check|clang-test|check-all}", despite > of introducing gnuwin32? > > - You forgot to mention a few important cmake variables. > > - CMAKE_BUILD_TYPE=Release (for most purpose) > - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed > onto C:\PROGRA~1\?) > - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. > - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from > llvm source tree > - PYTHON_EXECUTABLE, if %PATH% does not contain p...

...;> it needs of compiler-rt. So once to create x86_64 libs and once for >>>> >> i386 libs. >>>> >> >>>> >> 3) The compiler-rt build drops the ${arch} suffix from its libs, and >>>> >> the "clang/runtime" build uses CMAKE_INSTALL_PREFIX to control where >>>> >> the compiler-rt libs go. >>>> >> >>>> >> >>>> >> "CMAKE_INSTALL_PREFIX=${CMAKE_CURRENT_BINARY_DIR}/lib/clang/${CLANG_VERSION}/x86_64-linux" >>>> >> >>>> >>...

...t; know if you knew better version of make!) > > - Why don't you mention "make {check|clang-test|check-all}", despite > of introducing gnuwin32? > > - You forgot to mention a few important cmake variables. > > - CMAKE_BUILD_TYPE=Release (for most purpose) > - CMAKE_INSTALL_PREFIX (Who would be happy if clang were installed > onto C:\PROGRA~1\?) > - LLVM_LIT_TOOLS_DIR, to use gnuwin32 dedicated to testing llvm and clang. > - LLVM_EXTERNAL_CLANG_SOURCE_DIR, to check out clang outside from > llvm source tree > - PYTHON_EXECUTABLE, if %PATH% does not contain p...