search for: dcmake_c_flag

...nfiguration on Linux x86-64: cmake -G Ninja -DBUILD_SHARED_LIBS=ON \ -DCMAKE_SHARED_LINKER_FLAGS="-fuse-ld=gold" \ -DCMAKE_EXE_LINKER_FLAGS="-fuse-ld=gold"\ -DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ -DCMAKE_C_FLAGS="-O2 -g" \ -DCMAKE_CXX_FLAGS="-O2 -g" \ -DENABLE_LINKER_BUILD_ID=ON \ -DLLVM_ENABLE_ASSERTIONS=ON \ -DLLVM_ENABLE_PIC=ON \ -DLLVM_BINUTILS_INCDIR=/...

...>> >> Thanks >> Hongbin > > My CMake parameters: > > ${CMake} \ > -DCMAKE_BUILD_TYPE="Release" \ > -DCMAKE_INSTALL_PREFIX:PATH=${InstallDir} \ > -DCMAKE_C_COMPILER=${GCCDir}/bin/gcc \ > -DCMAKE_C_FLAGS="-m64" \ > -DCMAKE_CXX_COMPILER=${GCCDir}/bin/g++ \ > -DCMAKE_CXX_FLAGS="-m64" \ > -DPYTHON_EXECUTABLE=${PythonDir}/bin/python \ > -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON \ > -DLLVM_LIBDIR_SUFFIX=64...

...nja -DBUILD_SHARED_LIBS=ON \ >> -DCMAKE_SHARED_LINKER_FLAGS="-fuse-ld=gold" >> \ >> -DCMAKE_EXE_LINKER_FLAGS="-fuse-ld=gold"\ >> -DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ >> -DCMAKE_C_FLAGS="-O2 -g" \ >> -DCMAKE_CXX_FLAGS="-O2 -g" \ >> -DENABLE_LINKER_BUILD_ID=ON \ >> -DLLVM_ENABLE_ASSERTIONS=ON \ >> -DLLVM_ENABLE_PIC=ON \ >>...

...=clang CXX=clang++ cmake -G Ninja ../../src/llvm >> -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True >> -DLLVM_ENABLE_ASSERTIONS=True >> >> On ARM: >> $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release >> -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_C_FLAGS=-mcpu=cortex-a15 >> -DCMAKE_CXX_FLAGS=-mcpu=cortex-a15 -DLLVM_TARGETS_TO_BUILD=ARM >> -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True >> >> Warning: >> CMake Warning at cmake/modules/HandleLLVMOptions.cmake:117 (message): >> -fPIC is not supported. >&...

...flags... -DBUILD_SHARED_LIBS=ON \ -DCMAKE_BUILD_TYPE="Release" \ -DCMAKE_CXX_COMPILER=$GCC_ROOT/bin/g++ \ -DCMAKE_CXX_FLAGS="$CXXFLAGS" \ -DCMAKE_CXX_LINK_FLAGS="$LDFLAGS" \ -DCMAKE_C_COMPILER=$GCC_ROOT/bin/gcc \ -DCMAKE_C_FLAGS="$CFLAGS" \ -DCMAKE_C_LINK_FLAGS="$LDFLAGS" \ -DCMAKE_INSTALL_PREFIX=$PREFIX_DIR \ -DCMAKE_LIBRARY_PATH=${BASE_DIR}/lib \ -DCMAKE_SKIP_INSTALL_RPATH=OFF \ -DCMAKE_SKIP_RPATH=OFF \ -DCMAKE_SYSTEM_INCLUDE_PATH=$myincpath \ -D...

...building LLVM with Clang via CMake. On x86_64: $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True On ARM: $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_C_FLAGS=-mcpu=cortex-a15 -DCMAKE_CXX_FLAGS=-mcpu=cortex-a15 -DLLVM_TARGETS_TO_BUILD=ARM -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True Warning: CMake Warning at cmake/modules/HandleLLVMOptions.cmake:117 (message): -fPIC is not supported. Call Stack (most recent call first): cmake/modules/Handl...

Hi Eugene, It is strange, I also do a clean build with CMake+make with r301734 and it is ok. Could you provide more details? Thanks Hongbin On Mon, May 1, 2017 at 10:58 AM, Eugene Zelenko via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, Michael! > > On Sun, Apr 30, 2017 at 2:06 PM, Michael Kruse <llvmdev at meinersbur.de> > wrote: > > 2017-04-29 0:49

...ation 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" -- Installing: ship/include/sanitizer/asan_interface.h -- Installing: ship/include/sanitizer/com...

...ore than once! LLVM ERROR: inconsistency in registered CommandLine options llvm is built with: cmake -G "Ninja" \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DCMAKE_BUILD_TYPE=RelWithDebInfo \ -DCMAKE_INSTALL_PREFIX=/usr \ -DLLVM_LIBDIR_SUFFIX=64 \ -DCMAKE_C_FLAGS="-fuse-ld=gold -fPIC" \ -DCMAKE_CXX_FLAGS="-fuse-ld=gold -fPIC" \ -DLLVM_REQUIRES_RTTI=ON \ -DLLVM_ENABLE_TIMESTAMPS=OFF \ -DLLVM_ENABLE_ASSERTIONS=ON \ -DLLVM_ENABLE_PIC=ON \ -DLLVM_BINUTILS_INCDIR=/usr/include \ -DLLVM_TARGETS_TO_BUILD=all \ -D...

...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="-fno-rtti" \ -DCMAKE_CXX_COMPILER=$CXX \ -DCMAKE_C_COMPILER=$CC \ -DCMAKE_BUILD_TYPE=$CMAKE_BUILD_TYPE \ -DCMAKE_INSTALL_PREFIX=$CMAKE_INSTALL_PREFIX \ -DLLVM_TARGETS_TO_BUILD=$LLVM_TARGETS_TO_BUILD \ $SRC

Hi, I am trying to compile LLVM for AARCH (VMA=42), here my cmake command: cmake -G "Ninja" -D SANITIZER_AARCH64_VMA=42 .. But I get the following warning: ------------------------------------------------------------------------------------------ CMake Warning: Manually-specified variables were not used by the project: SANITIZER_AARCH64_VMA

...the build system. I have to turn off a lot of the extra > safety crap that VC2k5 and higher added [snip] > I am sure I am not the only one that does that, so supplying such > instructions for how to add in your own preprocessor definitions would > be great. For C source files: cmake -DCMAKE_C_FLAGS="-DSOME_DEF=value -DSOME_OTHER_DEF=value" path/to/llvm For C++ source files: cmake -DCMAKE_CXX_FLAGS="-DSOME_DEF=value -DSOME_OTHER_DEF=value" path/to/llvm I'll add this to the docs. Please list those defines and I will add an option for enabling them all with a single...

...is shown below: cmake -G Ninja -DBUILD_SHARED_LIBS=ON -DLLVM_PARALLEL_LINK_JOBS=2 -DLLVM_ENABLE_LLD=ON -DLLVM_ENABLE_LIBCXX=OFF -DCMAKE_BUILD_TYPE=Release -DGCC_INSTALL_PREFIX=/pathto/gcc-7.5.0/ -DLIBOMPTARGET_ENABLE_DEBUG=ON -DCMAKE_INSTALL_PREFIX=$HOME/opt/clang/${today} -DCMAKE_C_COMPILER=clang -DCMAKE_C_FLAGS="" -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS="" -DLLVM_ENABLE_PROJECTS="clang;openmp;lld;libcxx;libcxxabi" -DCLANG_OPENMP_NVPTX_DEFAULT_ARCH=sm_60 -DLIBOMPTARGET_NVPTX_COMPUTE_CAPABILITIES=60 -DLLVM_TARGETS_TO_BUILD=all $HOME/projects/llvm-project/llvm ----------...

...rs from CMake. It appears to be trying to pass VC++ flags to Clang. I am using a version of Clang built from trunk. PS D:\llvm\arm_test\compiler-rt-build> cmake -G Ninja -DCMAKE_C_COMPILER=clang.exe -DCMAKE_CXX_COMPILER=clang++.exe -DCM AKE_RC_COMPILER=rc.exe -DCMAKE_CXX_FLAGS="" -DCMAKE_C_FLAGS="" ..\compiler-rt -- The C compiler identification is Clang 3.7.0 clang.exe: error: no such file or directory: '/nologo' clang.exe: error: no such file or directory: '/showIncludes' -- The CXX compiler identification is Clang 3.7.0 clang.exe: error: no such file or direct...

...> My CMake parameters: >>> >>> ${CMake} \ >>> -DCMAKE_BUILD_TYPE="Release" \ >>> -DCMAKE_INSTALL_PREFIX:PATH=${InstallDir} \ >>> -DCMAKE_C_COMPILER=${GCCDir}/bin/gcc \ >>> -DCMAKE_C_FLAGS="-m64" \ >>> -DCMAKE_CXX_COMPILER=${GCCDir}/bin/g++ \ >>> -DCMAKE_CXX_FLAGS="-m64" \ >>> -DPYTHON_EXECUTABLE=${PythonDir}/bin/python \ >>> -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON \ >>&...

...using a version of Clang built from trunk. >>> >>> >>> >>> PS D:\llvm\arm_test\compiler-rt-build> cmake -G Ninja >>> -DCMAKE_C_COMPILER=clang.exe -DCMAKE_CXX_COMPILER=clang++.exe -DCM >>> AKE_RC_COMPILER=rc.exe -DCMAKE_CXX_FLAGS="" -DCMAKE_C_FLAGS="" >>> ..\compiler-rt >>> -- The C compiler identification is Clang 3.7.0 >>> clang.exe: error: no such file or directory: '/nologo' >>> clang.exe: error: no such file or directory: '/showIncludes' >>> -- The CXX compiler ident...

...-DLLVM_TARGETS_TO_BUILD='ARM' \ -DLIBCXX_BUILD_32_BITS:BOOL=ON \ -DLLVM_BUILD_32_BITS:BOOL=ON \ -DLLVM_ENABLE_STATIC:BOOL=ON \ -DLLVM_ENABLE_SHARED:BOOL=OFF \ -DLLVM_DISABLE_PIC:BOOL=OFF \ -D_LIBCPP_HAS_NO_STDOUT:BOOL=ON \ -D_LIBCPP_HAS_NO_STDIN:BOOL=ON \ -DCMAKE_C_FLAGS="$C_AND_CXX_COMMON_FLAGS" \ -DCMAKE_CXX_FLAGS="$C_AND_CXX_COMMON_FLAGS" \ ../llvm Firstly, I encounter the known problem with __atomic_load_8. arm-cortex-m{3,4} most probably doesn't support 64bit atomic read/write, but as long as I don't use it, changing the l...

...cmake.exe \ > -G"MSYS Makefiles" \ > -DCMAKE_MAKE_PROGRAM="/usr/bin/make.exe" \ > -DCMAKE_C_COMPILER="/mingw64/bin/gcc.exe" \ > -DCMAKE_CXX_COMPILER="/mingw64/bin/g++.exe" \ > -DFFI_INCLUDE_DIR="${FFI_INCLUDE_DIR}" \ > -DCMAKE_C_FLAGS="${CFLAGS}" \ > -DCMAKE_CXX_FLAGS="${CXXFLAGS} ${CPPFLAGS}" \ > -DCMAKE_INSTALL_PREFIX=/mingw64 \ > -DCMAKE_BUILD_TYPE=Release \ > -DLLVM_TARGETS_TO_BUILD="ARM;AArch64;CppBackend;X86" \ > -DLLVM_ENABLE_ASSERTIONS=OFF \ > -DLLVM_ENABLE_THR...

...-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" >> -- Installing: ship/include/sanit...

where should the file build_llvm_package.bat be placed and how should the build_llvm_package.bat be called? or is there a another way to do a two stage build of the llvm project on windows starting with using visual studio 2017 community. -------------- next part -------------- An HTML attachment was scrubbed... URL: