search for: edit_cach

...% if gnuwin32 is dedicated to tests. Use LLVM_LIT_TOOLS_DIR instead then. (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) - cmake and python are needed on %PATH%, as long as they are not invoked explicitly. cmake-generated Makefiles know where they are. eg. "make edit_cache", "make check" - If the target of this would be for newbies, you may mention "cmake-gui", too. FYI, I am usually use cmake-gui.exe, because I am n00b. - (Building the Sources), In my experience, make.exe -jN tends to be choked. I don't know where is -jN-stable gnu...

...'m getting a build error on one project and don't want it to hold up >> the build of everything else. > > In your LLVM build directory run > > $ cmake -DLLVM_BUILD_EXAMPLES=OFF /path/to/llvm/source > > (note if you are using the makefile build you can run ``make > edit_cache`` to do the above). > > If you are still having problems you could also set > LLVM_INCLUDE_EXAMPLES to OFF. > > If you use ccmake or cmake gui these options are easily visibile, > you'll see a whole bunch of other useful options. I'm wondering about things like clang, ll...

I'm learning the cmake build. Is there a way to disable the build of a subdirectory in llvm/projects? I'm getting a build error on one project and don't want it to hold up the build of everything else. Thanks! -David

...n build > in the first place. I'm sure most people who do a lot of cmake know these > settings by the back of their hand, but if you're like me and totally > clueless when it comes to cmake, it's downright confusing. ccmake will help you. After generating makefiles, "make edit_cache" will show you options. ...Takumi

...ests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make check" > > - If the target of this would be for newbies, you may mention "cmake-gui", > too. > FYI, I am usually use cmake-gui.exe, because I am n00b. > > - (Building the Sources), In my experience, make.exe -jN tends to be > choked. I don'...

...ests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make check" > > - If the target of this would be for newbies, you may mention "cmake-gui", > too. > FYI, I am usually use cmake-gui.exe, because I am n00b. > > - (Building the Sources), In my experience, make.exe -jN tends to be > choked. I don'...

...ests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make check" > > - If the target of this would be for newbies, you may mention "cmake-gui", > too. > FYI, I am usually use cmake-gui.exe, because I am n00b. > > - (Building the Sources), In my experience, make.exe -jN tends to be > choked. I don'...

...TOOLS_DIR instead then. >> (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) >> >> - cmake and python are needed on %PATH%, as long as they are not >> invoked explicitly. >> cmake-generated Makefiles know where they are. >> eg. "make edit_cache", "make check" >> >> - If the target of this would be for newbies, you may mention >> "cmake-gui", too. >> FYI, I am usually use cmake-gui.exe, because I am n00b. >> >> - (Building the Sources), In my experience, make.exe -jN tends to b...

On 6/21/2012 1:21 PM, Douglas Gregor wrote: > > On Jun 20, 2012, at 5:13 PM, Nick Lewycky <nlewycky at google.com > <mailto:nlewycky at google.com>> wrote: > >> Is there anybody who is certain that our autoconf dependency needs to >> stay around? Are there developers stuck on systems that don't have a >> recent enough cmake in their most recent

...TOOLS_DIR instead then. >> (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) >> >> - cmake and python are needed on %PATH%, as long as they are not >> invoked explicitly. >> cmake-generated Makefiles know where they are. >> eg. "make edit_cache", "make check" >> >> - If the target of this would be for newbies, you may mention >> "cmake-gui", too. >> FYI, I am usually use cmake-gui.exe, because I am n00b. >> >> - (Building the Sources), In my experience, make.exe -jN tends to b...

Is there an equivalent "make check-all VERBOSE=1" in the CMake build? I'm looking to see the full list of unit tests and the result of each. Thanks, Greg

For those interested in the actual file, it is now attached. ---------- Forwarded message ---------- From: Mikael Lyngvig <mikael at lyngvig.org> Date: 2012/6/16 Subject: RFC: "Building with MinGW on Windows" (DOC, NEW) To: LLVMdev Mailing List <llvmdev at cs.uiuc.edu> Here's the first part of my Windows set up documentation. This one only covers the process of

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

Here's the first part of my Windows set up documentation. This one only covers the process of setting up a normal box for building LLVM and Clang. A later document, which will follow in a few days, will cover how to set up a buildbot slave. As usual: I'm not a psychic, so if you have opinions regarding or suggestions on this document, please feel free to share them with me (on this

...ests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make check" > > - If the target of this would be for newbies, you may mention "cmake-gui", > too. > FYI, I am usually use cmake-gui.exe, because I am n00b. > > - (Building the Sources), In my experience, make.exe -jN tends to be > choked. I don'...