summaryrefslogtreecommitdiffstats
path: root/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'import-KWIML'David Cole2011-11-151-0/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | 5be0e92 Merge branch 'upstream-kwiml' into import-KWIML a8f6159 KWIML: Create test output dir for Xcode 33fff24 KWIML: No INT_SCN*8 on Intel for Windows bcc06d4 KWIML: No INT_SCN*8 on SunPro compiler 6d12ab3 KWIML: Suppress printf/scanf format warnings in test 553acec KWIML: Avoid redefining _CRT_SECURE_NO_DEPRECATE in test.h 93cebca Configure KWIML inside CMake as cmIML b2975ad Merge branch 'upstream-kwiml' into import-KWIML 831bade KWIML: The Kitware Information Macro Library
| * Configure KWIML inside CMake as cmIMLBrad King2011-06-271-0/+6
| |
* | Begin post-2.8.6 developmentDavid Cole2011-10-041-2/+2
| |
* | CMake 2.8.6v2.8.6David Cole2011-10-041-1/+1
| |
* | CMake 2.8.6-rc4David Cole2011-09-221-1/+1
| |
* | Merge branch 'release'David Cole2011-09-221-3/+3
|\ \
| * | CMake 2.8.6-rc3David Cole2011-09-091-1/+1
| | |
| * | CMake 2.8.6-rc2David Cole2011-09-021-1/+1
| | |
| * | CMake 2.8.6-rc1David Cole2011-08-261-3/+3
| | |
* | | CMake: Reference test targets only when BUILD_TESTING is ONDavid Cole2011-09-141-6/+10
|/ / | | | | | | | | | | | | You cannot set a property on a target that's not there, and these targets are not there when BUILD_TESTING is OFF. Thanks to Sankhesh Jhaveri for the bug report.
* | Begin post-2.8.5 developmentDavid Cole2011-07-081-2/+2
| |
* | CMake 2.8.5v2.8.5David Cole2011-07-081-1/+1
| |
* | CMake 2.8.5-rc3David Cole2011-06-211-1/+1
| |
* | CMake 2.8.5-rc2David Cole2011-06-151-1/+1
| |
* | CMake 2.8.5-rc1David Cole2011-05-251-3/+3
|/
* COMP: Fix build against non-standard outside libarchiveBrad King2011-03-311-0/+1
| | | | Use the include directories reported by find_package(LibArchive).
* Remove unused CMAKE_BACKWARDS_COMPATIBILITY markBrad King2011-03-011-2/+0
| | | | | CMake itself has no calls to cmake_minimum_required with VERSION < 2.6 so this cache variable does not appear at all.
* Require at least CMake 2.6.3 to build current CMakeBrad King2011-02-241-15/+2
| | | | Remove some cruft left for supporting builds with CMake 2.4.
* Begin post-2.8.4 developmentDavid Cole2011-02-151-2/+2
|
* CMake 2.8.4v2.8.4David Cole2011-02-151-1/+1
|
* CMake 2.8.4-rc2David Cole2011-01-311-1/+1
|
* Merge branch 'release'David Cole2011-01-311-3/+3
|\
| * CMake 2.8.4-rc1David Cole2011-01-121-3/+3
| |
* | bootstrap: Granular system library selection (#11431)Brad King2011-01-101-28/+39
|/ | | | | | | | | | This adds the ability for packagers to specify that some libraries should use system versions and others should use the CMake versions. This allows a bit of flexibility and means Homebrew (an OSX package manager) no longer has to continue to patch the CMake build process. Inspired-by: Mike McQuaid <mike@mikemcquaid.com>
* Cygwin: Do not define 'WIN32' (#10122)Brad King2010-12-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | One of Cygwin's goals is to build projects using the POSIX API with no Windows awareness. Many CMake-built projects have been written to test for UNIX and WIN32 but not CYGWIN. The preferred behavior under Cygwin in such projects is to take the UNIX path but not the WIN32 path. Unfortunately this change is BACKWARDS INCOMPATIBLE for Cygwin-aware CMake projects! Some projects that previously built under Cygwin and are Cygwin-aware when they test for WIN32 may now behave differently. Eventually these projects will need to be updated, but to help users build them in the meantime we print a warning about the change in behavior. Furthermore, one may set CMAKE_LEGACY_CYGWIN_WIN32 to request old behavior during the transition. Normally we avoid backwards incompatible changes, but we make an exception in this case for a few reasons: (1) This behavior is preferred by Cygwin's design goals. (2) A warning provides a clear path forward for everyone who may see incompatible behavior, and CMAKE_LEGACY_CYGWIN_WIN32 provides a compatibility option. The warning and compatibility option both disappear when the minimum required version of CMake in a project is sufficiently new, so this issue will simply go away over time as projects are updated to account for the change. (3) The fixes required to update projects are fairly insignificant. Furthermore, the Cygwin distribution has no releases itself so project versions that predate said fixes tend to be difficult to build anyway. (4) This change enables many CMake-built projects that did not previously build under Cygwin to work out-of-the-box. From bug #10122: "I have built over 120 different source packages with (my patched) CMake, including most of KDE4, and have found that NOT defining WIN32 on Cygwin is much more accurate." -- Yaakov Selkowitz A fully compatible change would require patches on top of these project releases for Cygwin even though they otherwise need not be aware of it. (5) Yaakov has been maintaining a fork of CMake with this change for the Cygwin Ports distribution. It works well in practice. By accepting the change in upstream CMake we avoid confusion between the versions. CMake itself builds without WIN32 defined on Cygwin. Simply disable CMAKE_LEGACY_CYGWIN_WIN32 explicitly in our own CMakeLists.txt file.
* Begin post-2.8.3 developmentDavid Cole2010-11-031-2/+2
|
* CMake 2.8.3v2.8.3David Cole2010-11-031-1/+1
|
* CMake 2.8.3-rc4David Cole2010-10-291-1/+1
|
* CMake 2.8.3-rc3David Cole2010-10-201-1/+1
|
* CMake 2.8.3-rc2Brad King2010-10-061-1/+1
|
* Merge branch 'release'Brad King2010-10-061-3/+3
|\
| * CMake 2.8.3-rc1Brad King2010-09-151-3/+3
| |
* | Merge topic 'vs-project-groups'Brad King2010-10-051-7/+25
|\ \ | |/ |/| | | | | fd3249e New USE_FOLDERS property OFF by default. (#3796)
| * New USE_FOLDERS property OFF by default. (#3796)David Cole2010-10-021-7/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Visual Studio Express editions do not support solution folders, so default behavior should be as if USE_FOLDERS global property is OFF. Also, allow folder names to be the same as target names: internally, use a prefix to distinguish folder GUIDs from target GUIDs. Add a target and folder with the same name in the ExternalProject test to exercise this code. For CMake itself, provide a new option CMAKE_USE_FOLDERS that defaults to ON so that Visual Studio users get a nicely organized CMake project. Express edition users will have to turn off the CMAKE_USE_FOLDERS option in order to build CMake in the VS Express IDE.
* | Merge topic 'vs-project-groups'Brad King2010-09-081-1/+34
|\ \ | |/ | | | | | | e6ac0aa Add FOLDER target property, for IDEs (#3796)
| * Add FOLDER target property, for IDEs (#3796)David Cole2010-09-031-1/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This work was started from a patch by Thomas Schiffer. Thanks, Thomas! See the newly added documentation of the FOLDER target property for details. Also added global properties, USE_FOLDERS and PREDEFINED_TARGETS_FOLDER. See new docs here, too. By default, the FOLDER target property is used to organize targets into folders in IDEs that have support for such organization. This commit adds "solution folder" support to the Visual Studio generators. Currently works with versions 7 through 10. Also, use the new FOLDER property in the ExternalProject test and in the CMake project itself.
* | Add option CMAKE_USE_SYSTEM_LIBARCHIVE (#10923)Brad King2010-07-291-5/+20
| | | | | | | | | | Finish the implementation of the option from the skeleton left by the initial addition of libarchive.
* | Merge topic 'use-system-bzip2'Brad King2010-07-201-1/+4
|\ \ | | | | | | | | | | | | 6a24bdf Optionally use system bzip2 library (#10932)
| * | Optionally use system bzip2 library (#10932)Brad King2010-07-131-1/+4
| | | | | | | | | | | | | | | | | | | | | Add option CMAKE_USE_SYSTEM_BZIP2 and enable it automatically when CMAKE_USE_SYSTEM_LIBRARIES is on. While we're at it, remove XMLRPC from the list of system library options because we no longer provide it in source.
* | | Merge topic 'disable_gcc33_onfree_bsd'Brad King2010-07-131-1/+15
|\ \ \ | |/ / |/| | | | | | | | | | | 3ef273c Poison GCC 3.3 on OpenBSD a bit later 696a0af Disable gcc 33 on OpenBSD because it crashes CPack by default.
| * | Poison GCC 3.3 on OpenBSD a bit laterBrad King2010-07-061-16/+15
| | | | | | | | | | | | | | | | | | | | | Move lines from commit 696a0af (Disable gcc 33 on OpenBSD because it crashes CPack by default, 2010-06-25) further down in CMakeLists.txt so that CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS applies. This fixes the code for building with CMake 2.4.
| * | Disable gcc 33 on OpenBSD because it crashes CPack by default.Bill Hoffman2010-06-251-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | Make sure no one tries to use gcc 33 based tools to build CMake. This is because a cpack test failed with a crash. The crash seems to be caused by the stack checking code on by default in OpenBSD. The crash is in some stl code. The problem is fixed with newer gcc compilers on OpenBSD.
* | | Begin post-2.8.2 developmentBrad King2010-06-281-2/+2
| | |
* | | CMake 2.8.2v2.8.2Brad King2010-06-281-1/+1
| |/ |/|
* | CMake 2.8.2-rc4Brad King2010-06-241-1/+1
| |
* | CMake 2.8.2-rc3Brad King2010-06-221-1/+1
| |
* | CMake 2.8.2-rc2Brad King2010-06-151-1/+1
| |
* | Merge branch 'release'Brad King2010-06-151-3/+3
|\ \ | |/ |/|
| * CMake 2.8.2-rc1Brad King2010-06-111-3/+3
| |
* | Merge branch 'make_libarchive_use_cmzlib'Brad King2010-06-151-0/+1
|\ \
generated by cgit v0.12 at 2024-11-15 06:47:14 (GMT)