search for: ccmake

On 21 Jun 2012, at 09:45, Konstantin Tokarev wrote: > Use ccmake and don't suffer anymore! Now there's a construct that I never expected to see anyone utter seriously... David

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

...sn't completely mature yet (the "TODO" sections in the page you mention above reinforce that impression). I remember at least one other build error in the past, related to building a non-X86 backend. With current svn I get: %> mkdir llvm-svn-build %> cd llvm-svn-build/ %> ccmake ../llvm-svn # Basically only tweak the install prefix in ccmake, configure, generate %> make ... [ 2%] Built target LLVMSupport [ 3%] Built target LLVMSystem Linking CXX executable ../../bin/tblgen ../../lib/libLLVMSystem.a(Mutex.cpp.o): In function `llvm::sys::Mutex::tryacquire()': Mutex....

..._TARGETS_TO_BUILD doesn't tell you *which* targets you can 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

...ctory 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, lldb, etc. that are checked out in llvm's projects directory. Is there a way to skip building one of them? The lldb build is failing due to an...

...ng to try it out. I dont know >>  enough about CMake but I tried to go through the cmake build files. >> >>  Thanks, >>  ashok > > I managed to use: > > CC=clang CXX=clang++ CXXFLAGS="-stdlib=libc++ -I <libcxxdir..." cmake... Why so complicated? Use ccmake and don't suffer anymore! -- Regards, Konstantin

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

...o make a backward-compatible binary? If not, is there a sane way to build something that needs gcc 4.8+/boost 1.5.3+/cmake 2.8 on Centos6? I found the devtoolset-2 software collection with a usable gcc, but no boost. And cmake 2.8 installs as cmake28 whereas the project expects the normal cmake/ccmake names. -- Les Mikesell lesmikesell at gmail.com

...ce Debug builds tend to be very slow. > > - Install Clang + LLVM somewhere that isn't where you do your normal LLVM/Clang development. > > - Configure with the environment variables CC=/path/to/clang CXX=/path/to/clang++, which works with either autoconf configure or CMake cmake/ccmake. > > - Build LLVM and Clang as normal. > > - Report your experiences to help us improve Clang! > > - Doug -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin http://exactcode.com | http://t2-project.org | http://rene.rebe.de

...RGETS_TO_BUILD doesn't tell you *which* targets you can 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. Well, you can use ccmake to navigate back and forth through available options, their descriptions and values -- Regards, Konstantin

Chuck Robey <chuckr at telenix.org> writes: >> Doesn't CMake support the BSD toolchain? > > OK, I checked the llvm-2.5 Makefiles. They have constructs in them > which cannot be used in any BSD Makefile (such as the form of > conditionals: ifndef is a GNU Makeism), and won't run on any BSD Make. > I know BSD Make and GNU Make well enough, but I doon't know

Hi llvm-dev, Are we still able to run llvm test-suite without LNT? Also, is there any example of configuring test-suite to run against 3rd party backend rather than llc? Thanks Hongbin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160810/2adbad76/attachment.html>

...s tend to be very slow. >> >>  - Install Clang + LLVM somewhere that isn't where you do your normal LLVM/Clang development. >> >>  - Configure with the environment variables CC=/path/to/clang CXX=/path/to/clang++, which works with either autoconf configure or CMake cmake/ccmake. >> >>  - Build LLVM and Clang as normal. >> >>  - Report your experiences to help us improve Clang! >> >>       - Doug > > -- >  René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin >  http://exactcode.com | http://t2-project.org | http://rene.r...

...Release build, since Debug builds tend to be very slow. - Install Clang + LLVM somewhere that isn't where you do your normal LLVM/Clang development. - Configure with the environment variables CC=/path/to/clang CXX=/path/to/clang++, which works with either autoconf configure or CMake cmake/ccmake. - Build LLVM and Clang as normal. - Report your experiences to help us improve Clang! - Doug

On 6/20/2012 11:55 PM, Ashok Nalkund wrote: > On 6/20/2012 11:00 PM, "C. Bergström" wrote: >> On 06/21/12 12:47 PM, Chandler Carruth wrote: >>> On Wed, 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

Nice, very well done on the CMake build. This command worked perfectly: cmake -G "Visual Studio 8 2005" -DCMAKE_CXX_FLAGS="-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE -D_SECURE_SCL=0 -D_SCL_SECURE_NO_DEPRECATE -D_HAS_ITERATOR_DEBUGGING=0" ..\trunk > ..\build_log.txt And for the actual build, went very well. The INSTALL was much project was better then I was

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

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

Try as I might I can't seem to get LLVM to bulid using clang/clang++. No matter what I do it insists on using /usr/bin/cc and /usr/bin/c++ which are gcc. Am I missing something obvious? I vaguely remember some document describing a stage1 compiler built by your old toolchain and a stage2 compiler but I can't find the steps to do that any more. $ CC=/usr/local/bin/clang

...ings like configuration checks that are slow caching the result makes incremental re-configuration much faster. We should use cached values sparingly and only where they provide benefit. Additionally, every cached CMake variable is a configuration point. Variables not marked `INTERNAL` show up in `ccmake` and `cmake-gui`, and variables not `mark_as_advanced` show up to all users. We should use the `INTERNAL` and `mark_as_advanced` options wherever appropriate to limit our supported configuration interface. #### Making Sense of Runtime Builds Right now, there are three different ways to build compi...