- Jan 31, 2014
-
-
NAKAMURA Takumi authored
llvm-svn: 200558
-
- Jan 19, 2014
-
-
NAKAMURA Takumi authored
In LLVM build tree, they points corresponding INTDIR. In Clang standalone tree, they points external dir (llvm-config's --bindir and --libdir). llvm-svn: 199595
-
NAKAMURA Takumi authored
llvm-svn: 199594
-
NAKAMURA Takumi authored
llvm-svn: 199593
-
- Jan 13, 2014
-
-
Chandler Carruth authored
option with the others in the top level CMakeLists, and put the check in HandleLLVMOptions. This will also let it be used from the standalone Clang builds. llvm-svn: 199149
-
Chandler Carruth authored
compiler version checking doesn't work on 2.8.7. This feature was documented in 2.8.10, but existed for an unknown amount of time before that. I'm actually happy to revert this and remove the use of the feature if there is anyone with a specific problem updating CMake. Please just let me know. I don't want to re-implement this CMake functionality unless there is a reason, and this is the only real way to find that out. llvm-svn: 199148
-
NAKAMURA Takumi authored
It was too late to set BUG_REPORT_URL after configure_file(config.h). BUG_REPORT_URL in config.h.cmake would be updated at 2nd run of cmake. It caused many recompilations. FYI, configure handles BUG_REPORT_URL in llvm side. llvm-svn: 199076
-
- Jan 06, 2014
-
-
Jean-Daniel Dupas authored
Introduce a cmake LLVM_ENABLE_LIBCXX build parameter to compile using libc++ instead of the system default Summary: This parameter is required to build C++11 projects (like lld or lldb) on OS X as the default STL does not provide c++ classes. CC: llvm-commits, triton Differential Revision: http://llvm-reviews.chandlerc.com/D2381 llvm-svn: 198625
-
- Dec 30, 2013
-
-
NAKAMURA Takumi authored
[CMake][VS][XCode] Restruct the output directory layout more comfortable, ${BINARY_DIR}/${BUILD_MODE}/(bin|lib) We have been seeing nasty directory layout with CMake multiconfig, such as, bin/Release/clang.exe lib/clang/3.x/... lib/Release/clang/3.x/.. (duplicated) Move the layout similar to autoconf's; Release/bin/clang.exe Release/lib/clang/3.x/... Checked on Visual Studio 10. Could you guys please confirm my change on XCode(and other multiconfig builders)? Note: Don't set variables CMAKE_*_OUTPUT_DIRECTORY any more, or a certain builder, for eaxample, msbuild.exe, would be confused. llvm-svn: 198205
-
- Dec 20, 2013
-
-
Artyom Skrobov authored
llvm-svn: 197825
-
Rafael Espindola authored
This matches what the configure build does. Patch by Jan Vesely. Fixes pr14189. llvm-svn: 197743
-
- Dec 16, 2013
-
-
NAKAMURA Takumi authored
[CMake] Introduce LLVM_RUNTIME_OUTPUT_INTDIR and LLVM_LIBRARY_OUTPUT_INTDIR to reduce references to CMAKE_CFG_INTDIR. Each of them forms like; ${CMAKE_BINARY_DIR}/bin/${CMAKE_CFG_INTDIR} ${CMAKE_BINARY_DIR}/lib/${CMAKE_CFG_INTDIR} llvm-svn: 197394
-
NAKAMURA Takumi authored
llvm-svn: 197392
-
- Nov 26, 2013
-
-
Arnaud A. de Grandmaison authored
In some case, it may be required to build LLVM in C++11 mode, as some the subprojects (like lldb) requires it. This mimics the autoconf behaviour. However, given the discussions on the switch to C++11 of the codebase, this behaviour should evolve to default to C++11 with some checks of the compiler capabilities. llvm-svn: 195727
-
- Nov 21, 2013
-
-
Hans Wennborg authored
- Allow overriding PACKAGE_VERSION from the command-line - Use PACKAGE_VERSION to set CPACK_PACKAGE_VERSION (used by the Win installer) - Don't include the version number in the CPack install dir or registry key. Differential revision: http://llvm-reviews.chandlerc.com/D2245 llvm-svn: 195379
-
- Nov 20, 2013
-
-
NAKAMURA Takumi authored
llvm-svn: 195247
-
- Nov 13, 2013
-
-
Hans Wennborg authored
Reid pointed out we already have LLVM_USE_CRT_{buildtype} to set it. llvm-svn: 194604
-
Hans Wennborg authored
for release builds. This is a follow-up to r194589. Aaron pointed out that building libraries with /MT and using them in an application that uses a different run-time library can be a bad idea. Move the option to build with /MT behind a CMake option so it can be turned on selectively, such as when building the toolchain installer. llvm-svn: 194596
-
- Oct 31, 2013
-
-
Rafael Espindola authored
llvm-svn: 193813
-
- Oct 28, 2013
-
-
Bill Wendling authored
llvm-svn: 193541
-
- Oct 17, 2013
-
-
Hans Wennborg authored
After r192904, Reid pointed out he thought we already set the stack size for MSVC. Turns out we did, but it didn't seem to work. This commit sets the stack size in a single place, using CMAKE_EXE_LINKER_FLAGS because that seems to be the way that works best. llvm-svn: 192912
-
- Oct 04, 2013
-
-
Alexey Samsonov authored
Restore LLVM_BUILD_RUNTIME option that was deleted in r191835, but is still used to control building of compiler-rt and libcxx llvm-svn: 191948
-
- Oct 02, 2013
-
-
Chandler Carruth authored
infrastructure. This was essentially work toward PGO based on a design that had several flaws, partially dating from a time when LLVM had a different architecture, and with an effort to modernize it abandoned without being completed. Since then, it has bitrotted for several years further. The result is nearly unusable, and isn't helping any of the modern PGO efforts. Instead, it is getting in the way, adding confusion about PGO in LLVM and distracting everyone with maintenance on essentially dead code. Removing it paves the way for modern efforts around PGO. Among other effects, this removes the last of the runtime libraries from LLVM. Those are being developed in the separate 'compiler-rt' project now, with somewhat different licensing specifically more approriate for runtimes. llvm-svn: 191835
-
- Sep 25, 2013
-
-
Rafael Espindola authored
This makes sure we get the same behavior with all supported cmake versions. Once we support only versions >= 2.8.11 we can experiment with other values or just setting it for some binaries. Patch by Greg Bedwell. llvm-svn: 191372
-
- Aug 30, 2013
-
-
Daniel Dunbar authored
- We do some nasty things w.r.t. installing or overriding signal handlers in order to improve our crash recovery support or interaction with crash reporting software, and those things are not necessarily appropriate when LLVM is being linked into a client application that has its own ideas about how to do things. This gives those clients a way to disable that handling at build time. - Currently, the code this guards is all Apple specific, but other platforms might have the same concerns so I went for a more generic configure name. Someone who is more familiar with library embedding on Windows can handle choosing which of the Windows/Signals.inc behaviors might make sense to go under this flag. - This also fixes the proper autoconf'ing of ENABLE_BACKTRACES. The code expects it to be undefined when disabled, but the autoconf check was just defining it to 0. llvm-svn: 189694
-
Reid Kleckner authored
Requires shuffling the CPack code up before add_subdirectory(tools), but that's where the version settings are anyway. llvm-svn: 189615
-
- Aug 28, 2013
-
-
Hans Wennborg authored
This adds the msbuild integration files to the install, provides batch scripts for (un)installing it in a convenient way, and hooks up the nsis installer to run those scripts. Differential Revision: http://llvm-reviews.chandlerc.com/D1537 llvm-svn: 189434
-
- Aug 26, 2013
-
-
Hans Wennborg authored
It looked misplaced in the main CMakeLists.txt file. llvm-svn: 189230
-
- Aug 24, 2013
-
-
Michael Gottesman authored
I am going to add in a subsequent patch support for generating the llvm manpage. llvm-svn: 189164
-
Hans Wennborg authored
Differential Revision: http://llvm-reviews.chandlerc.com/D1428 llvm-svn: 189155
-
- Aug 16, 2013
-
-
Hans Wennborg authored
This tweaks the CMake rules for building an installation package on Windows: - Sets license file (otherwise nsis shows an ugly default) - Adds LLVM logo - Shows "do you want to add this to the system path" dialog. Differential Revision: http://llvm-reviews.chandlerc.com/D1414 llvm-svn: 188509
-
- Aug 15, 2013
-
-
Michael Gottesman authored
We were marking both LLVMBUILDOUTPUT and LLVMBUILDERRORS as ERROR_VARIABLES when clearly LLVMBUILDOUTPUT should be marked as OUTPUT_VARIABLE. llvm-svn: 188444
-
- Aug 12, 2013
-
-
Chandler Carruth authored
library for color support detection. This still will use a curses library if that is all we have available on the system. This change tries to use a smaller subset of the curses library, specifically the subset that is on some systems split off into a separate library. For example, if you install ncurses configured --with-tinfo, a 'libtinfo' is install that provides just the terminfo querying functionality. That library is now used instead of curses when it is available. This happens to fix a build error on systems with that library because when we tried to link ncurses into the binary, we didn't pull tinfo in as well. =] It should also provide an easy path for supporting the NetBSD libterminfo library, but as I don't have access to a NetBSD system I'm leaving adding that support to those folks. llvm-svn: 188160
-
- Aug 07, 2013
-
-
Chandler Carruth authored
using it to detect whether or not a terminal supports colors. This replaces a particularly egregious hack that merely compared the TERM environment variable to "dumb". That doesn't really translate to a reasonable experience for users that have actually ensured their terminal's capabilities are accurately reflected. This makes testing a terminal for color support somewhat more expensive, but it is called very rarely anyways. The important fast path when the output is being piped somewhere is already in place. The global lock may seem excessive, but the spec for calling into curses is *terrible*. The whole library is terrible, and I spent quite a bit of time looking for a better way of doing this before convincing myself that this was the fundamentally correct way to behave. The damage of the curses library is very narrowly confined, and we continue to use raw escape codes for actually manipulating the colors which is a much sane system than directly using curses here (IMO). If this causes trouble for folks, please let me know. I've tested it on Linux and will watch the bots carefully. I've also worked to account for the variances of curses interfaces that I could finde documentation for, but that may not have been sufficient. llvm-svn: 187874
-
- Jul 30, 2013
-
-
Eric Christopher authored
In limited testing this seems to work. Caveat emptor. llvm-svn: 187452
-
- Jul 25, 2013
-
-
Rafael Espindola authored
Approval in here http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-July/064169.html llvm-svn: 187145
-
- Jul 17, 2013
-
-
Duncan Sands authored
The issue is that CMAKE_BUILD_TYPE=RelWithDebInfo LLVM_ENABLE_ASSERTIONS=ON was not building with assertions enabled. (I was unable to find what in the LLVM source tree was adding -DNDEBUG to the build line in this case, so decided that it must be cmake itself that was adding it - this may depend on the cmake version). The fix treats any mode that is not Debug as being the same as Release for this purpose (previously it was being assumed that cmake would only add -DNDEBUG for Release and not for RelWithDebInfo or MinSizeRel). If other versions of cmake don't add -DNDEBUG for RelWithDebInfo then that's OK: with this change you just get a useless but harmless -UNDEBUG or -DNDEBUG. llvm-svn: 186499
-
- Jun 26, 2013
-
-
Andy Gibbs authored
llvm-svn: 184923
-
- Jun 24, 2013
-
-
Reid Kleckner authored
All of LLVM's Python scripts only support Python 2 for widely understood reasons. Patch by Yonggang Luo. llvm-svn: 184732
-
- May 22, 2013
-
-
Rafael Espindola authored
Should fix the cmake bots that were already building R600. llvm-svn: 182447
-