search for: cmakecach

Hello, I'm working on a project involving LLVM and keep shifting between the Debug and Release build by assigning different values to CMAKE_BUILD_TYPE in <llvm_build>/CMakeCache.txt and then building it. I wanted to know if this was a safe alternative to re-configuring the build after removing <llvm_build>/CMakeFiles/ and <llvm_build>/CMakeCache.txt. Thanks, Sanjay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lis...

If I've configured a Release build, build it and then go back and re-run cmake with -DCMAKE_BUILD_TYPE=Debug (and nothing else changed), almost nothing gets rebuilt when I try to build. Is this expected? I know I can edit CMakeCache.txt directly and trigger an essentially full rebuild. -David

Hi, I see the following variables in the CMakeCache.txt: SANITIZER_CXX_ABI:STRING=default //STRINGS property for variable: SANITIZER_CXX_ABI SANITIZER_CXX_ABI-STRINGS:INTERNAL=none;default;libcxxabi;libstdc++ Regards, ismail On Tue, Aug 1, 2017 at 7:32 PM, Vedant Kumar <vsk at apple.com> wrote: > >> On Aug 1, 2017, at 7:07 AM, İs...

Now I have -DLLVM_INCLUDE_EXAMPLES:BOOL=OFF but Kaleidoscope is still there and selected for build (-G "Visual Studio 9 2008") -Jochen

...his by unsetting any such variables first. > > > The problem I've had in the past setting *FLAGS on the cmake command > line is that sometimes the configure fails because it uses those > flags in various configuration checking compiles. So typically I > hand edit the resulting CMakeCache.txt if I want to pass specific > options to the build. Note that there are various flavors of e.g. > LINKER_FLAGS that get passed to different types of links though > (SHARED vs EXE etc). I haven't tried setting CFLAGS etc env > variables before kicking off the ninja build to pass...

Can someone tell me the magic CMake changes that I need to make so that the C++ compiler will display warnings and terminate? I broke the build yesterday because I had not seen a warning that then showed up in the build. I have these two options set in CMakeCache.txt: //Enable compiler warnings. LLVM_ENABLE_WARNINGS:BOOL=ON //Fail and stop if a warning is triggered. LLVM_ENABLE_WERROR:BOOL=ON

...uot; -DCMAKE_CXX_FLAGS="/permissive- /D_SILENCE_ALL_CXX17_DEPRECATION_WARNINGS" -DCMAKE_CXX_STANDARD=17 " and when building the target ALL_BUILD.vcxproj I redirected the output to a file. I'm attaching that file to this message. Name of the file is build.log. I'm attaching CMakeCache.txt and CMakeOutput.log for reference. Any help is appreciated. Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191030/254e1d7f/attachment-0001.html> -------------- next part --------...

...t;> >>> Again, I'm working on a fix, but could you also provide your cmake >>> command? Looks like we aren't handling your use case correctly. >>> >>> thanks.. >>> don >>> >> >> % grep -R LLVM_FORCE_ENABLE_DUMP * >> CMakeCache.txt:LLVM_FORCE_ENABLE_DUMP:BOOL=OFF >> CMakeCache.txt.orig:LLVM_FORCE_ENABLE_DUMP:BOOL=OFF >> include/llvm/Config/llvm-config.h:/* Defined in debug builds and release >> builds if LLVM_FORCE_ENABLE_DUMP >> >> is what I see from a cmake options of... >> >>...

Just posted this fix on ninja's github page, but figured I'd share it with a larger audience. Every time I run cmake && ninja in a new build directory, ninja will rerun cmake because the entry for build.ninja in .ninja_log is older than the timestamp on CMakeCache.txt, even if the timestamps on the actual file isn't older. The following patch fixes the problem, i.e., there's no need to add build.ninja to the ninja_log: diff --git a/src/ninja.cc b/src/ninja.cc index a093cd1..810b22d 100644 --- a/src/ninja.cc +++ b/src/ninja.cc @@ -249,8 +249,6 @@ b...

Hi, Trying to compile llvm with the following configuration 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" \

George Karpenkov <ekarpenkov at apple.com> writes: > Should -DCMAKE_CXX_COMPILER be also specified? CMake is smart enough to infer that from C_COMPILER: % grep CMAKE_CXX_COMPILER CMakeCache.txt CMAKE_CXX_COMPILER:FILEPATH=/Users/bogner/llvm-lkgc/bin/clang++ >> On Aug 24, 2017, at 11:29 AM, Justin Bogner <mail at justinbogner.com> wrote: >> >> (kcc, george: sorry for the re-send, the first was from a non-list email >> address) >> >> My co...

...ich is used along with > LLVM_ENABLE_ASSERTIONS to set LLVM_ENABLE_DUMP. > > Again, I'm working on a fix, but could you also provide your cmake > command? Looks like we aren't handling your use case correctly. > > thanks.. > don > % grep -R LLVM_FORCE_ENABLE_DUMP * CMakeCache.txt:LLVM_FORCE_ENABLE_DUMP:BOOL=OFF CMakeCache.txt.orig:LLVM_FORCE_ENABLE_DUMP:BOOL=OFF include/llvm/Config/llvm-config.h:/* Defined in debug builds and release builds if LLVM_FORCE_ENABLE_DUMP is what I see from a cmake options of... -DLLVM_LINK_LLVM_DYLIB:BOOL=ON -DCOMPILER_RT_ENABLE_IOS:BOOL=...

...m open to avoid this by unsetting > any such variables first. > The problem I've had in the past setting *FLAGS on the cmake command line is that sometimes the configure fails because it uses those flags in various configuration checking compiles. So typically I hand edit the resulting CMakeCache.txt if I want to pass specific options to the build. Note that there are various flavors of e.g. LINKER_FLAGS that get passed to different types of links though (SHARED vs EXE etc). I haven't tried setting CFLAGS etc env variables before kicking off the ninja build to pass args. > - Is th...

Hello everyone, I'm trying to compile LLVM and Clang into LLVM IR with debug info. I know that clang++ -g2 -S -emit-llvm <filename> does this, but I'm unfamiliar with CMake. I tried changing CMAKE_CXX_FLAGS in CMakeCache.txt to "clang++ -g2 -S -emit-llvm," "-g2 -S -emit-llvm," and "-emit-llvm," but everything I tried resulted in a failed build, and/or .o files that didn't look like LLVM IR files when I opened them up. Where is the right place to pass these flags in? Thanks, Macke...

>> Now I'm using LLVM_BUILD_EXAMPLES=OFF and I have >> >> //Build LLVM example programs. >> LLVM_BUILD_EXAMPLES:BOOL=OFF >> >> in the cmakecache.txt file but it also does not seem to >> work. >> > > What that means? LLVM_BUILD_EXAMPLES shall create build targets for the > examples but do not build them when you build the ALL_BUILD target. > The targets are present (that's ok) but are selected for build...

Hello LLVM, When building LLVM/Clang (debug build), linking takes too long. I notice that LTO is enabled now and guess that's to blame. Is there a CMAKE config option to disable LTO linking? I can't seem to find anything. Thanks, -steve

On Mon, Oct 3, 2016 at 10:54 PM, Teresa Johnson <tejohnson at google.com> wrote: > > Aha - finally reproduced! The difference is using ld.bfd not > ld.gold. With that I get the same failure (using 3.9 to build 3.9 > sources): Thanks a lot! [...] > I am not sure what the official support story is for LLVMgold.so and > ld.bfd. As mentioned earlier, the LLVM site indicates

> Which combination of cmake/ninja versions are you using (latest are > v3.4.3 and v1.6.0)? > With this combination I could reduce build-time down from approx. 3h down to 01h20m. $ egrep -i 'jobs|ninja' llvm-build/CMakeCache.txt //Program used to build from build.ninja files. CMAKE_MAKE_PROGRAM:FILEPATH=/opt/cmake/bin/ninja //Define the maximum number of concurrent compilation jobs. LLVM_PARALLEL_COMPILE_JOBS:STRING=3 //Define the maximum number of concurrent link jobs. LLVM_PARALLEL_LINK_JOBS:STRING=1 CMAKE_GENERATOR...

...:25 AM, Don Hinton <hintonda at gmail.com> wrote: > Hi Jack: > > Yes, I was just looking at that. Seems like TableGen wasn't done along > with the rest of llvm. I'll work up a complete patch shortly. > > Btw, I'm curious how this happened. Do you have a stale CMakeCache.txt by > any chance? You might check the value for LLVM_ENABLE_DUMP and see if it's > consistent. > > Again, I'll gen up a complete patch shortly -- sorry for delay, had to > walk my dog first... > > thanks... > don > There are no instances of LLVM_ENABLE_DUMP...

Dear All I've made un update to the llvm to the latest. At configuration, I've met some new errors to me, like it needs lldb, lld, dragonegg, llgo and so. However, I've checked them and configuration went on. Now I'm stuck at build stage, specifically at dragonegg. First it could not find gmp.h, I've solved this by installing libgmp-dev. Now, it can't find auto-host.h.