Skip to content
  1. Jan 31, 2014
  2. Jan 19, 2014
  3. Jan 13, 2014
    • Chandler Carruth's avatar
      Factor the option and checking of compiler version better. Put the · 83885973
      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
      83885973
    • Chandler Carruth's avatar
      Raise the minimum CMake version to 2.8.8 -- we have a report that the · 5aad86a9
      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
      5aad86a9
    • NAKAMURA Takumi's avatar
      [CMake] Move BUG_REPORT_URL from clang to llvm. · f0a1ab8f
      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
      f0a1ab8f
  4. Jan 06, 2014
  5. Dec 30, 2013
    • NAKAMURA Takumi's avatar
      [CMake][VS][XCode] Restruct the output directory layout more comfortable,... · baa9f533
      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
      baa9f533
  6. Dec 20, 2013
  7. Dec 16, 2013
  8. Nov 26, 2013
  9. Nov 21, 2013
  10. Nov 20, 2013
  11. Nov 13, 2013
  12. Oct 31, 2013
  13. Oct 28, 2013
  14. Oct 17, 2013
    • Hans Wennborg's avatar
      CMake: set stack size for MSVC in just one place · bef50abe
      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
      bef50abe
  15. Oct 04, 2013
  16. Oct 02, 2013
    • Chandler Carruth's avatar
      Remove the very substantial, largely unmaintained legacy PGO · ea564946
      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
      ea564946
  17. Sep 25, 2013
  18. Aug 30, 2013
    • Daniel Dunbar's avatar
      [conf] Add config variable to disable crash related overrides. · eb6c708d
      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
      eb6c708d
    • Reid Kleckner's avatar
      Substitute LLVM's version into the msbuild property file at config time · c974f097
      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
      c974f097
  19. Aug 28, 2013
  20. Aug 26, 2013
  21. Aug 24, 2013
  22. Aug 16, 2013
  23. Aug 15, 2013
    • Michael Gottesman's avatar
      Fixed typo in CMakeLists.txt. · 21c69487
      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
      21c69487
  24. Aug 12, 2013
    • Chandler Carruth's avatar
      Target a minimal terminfo library rather than necessarily a full curses · f11f1e43
      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
      f11f1e43
  25. Aug 07, 2013
    • Chandler Carruth's avatar
      Add support for linking against a curses library when available and · cad7e5e0
      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
      cad7e5e0
  26. Jul 30, 2013
  27. Jul 25, 2013
  28. Jul 17, 2013
    • Duncan Sands's avatar
      Tweak the cmake interaction between CMAKE_BUILD_TYPE and LLVM_ENABLE_ASSERTIONS. · 80f122fe
      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
      80f122fe
  29. Jun 26, 2013
  30. Jun 24, 2013
  31. May 22, 2013
Loading