Patched versions of CMake for ReactOS needs
Go to file
Brad King 80c947b397 No /fast targets in try_compile project mode
The try_compile command builds the cmTryCompileExec executable using the
cmTryCompileExec/fast target with Makefile generators in order to save
time since dependencies are not needed.  However, in project mode the
command builds an entire source tree that may have dependencies.
Therefore we can use the /fast target approach only in one-source mode.
2009-08-04 14:37:46 -04:00
Docs BUG: Fix cmake-mode.el indentation cursor motion 2009-02-26 13:28:01 -05:00
Example
Modules Pass Fortran90 test result to try-compile 2009-07-30 13:46:51 -04:00
Source No /fast targets in try_compile project mode 2009-08-04 14:37:46 -04:00
Templates ENH: Install all Modules and Templates 2009-07-24 13:17:41 -04:00
Tests No /fast targets in try_compile project mode 2009-08-04 14:37:46 -04:00
Utilities ENH: 80 is fine, i guess not 2009-06-26 10:00:47 -04:00
.gitattributes
bootstrap ENH: Improve dynamic variable scope implementation 2009-07-22 14:22:45 -04:00
ChangeLog.txt ENH: remove DashboardScripts and CMakeWeb from the change log 2008-03-27 13:30:52 -04:00
cmake_uninstall.cmake.in BUG: Patch from bug#4312 to make uninstall work with DESTDIR. 2007-01-22 10:39:16 -05:00
cmake.1
CMakeCPack.cmake ENH: Overhaul CMake version numbering 2009-03-05 15:17:07 -05:00
CMakeCPackOptions.cmake.in BUG: Add CPACK_NSIS_PACKAGE_NAME to the list of CPack variables that CMake overrides. We use the same value as the CPack-provided default, but do it here such that configuring with an older CMake will still give us this new variable. Necessary so that the CMake release process works with the new variable: CMake is configured with a previous CMake, but packaged with the freshly built CPack. (This fix is necessary because the fix for issue #8682 caused the side effect of having an empty CPACK_NSIS_PACKAGE_NAME for the CMake nightly package.) 2009-07-20 12:08:34 -04:00
CMakeGraphVizOptions.cmake
CMakeLists.txt Fix installation when built by CMake 2.4 2009-07-31 08:27:36 -04:00
CMakeLogo.gif ENH: fancier logo 2007-11-26 13:21:57 -05:00
CompileFlags.cmake ENH: first pass at VS 10, can bootstrap CMake, but many tests still fail 2009-06-25 16:41:57 -04:00
configure
Copyright.txt
CTestConfig.cmake ENH: support old cmake for dashboards 2008-09-09 13:01:46 -04:00
CTestCustom.cmake.in COMP: Mask out shadowed declaration warnings that always follow already masked Utilities/cmtar warnings. 2009-07-10 09:53:50 -04:00
CTestCustom.ctest.in ENH: Create CTestCustom.cmake instead of CTestCustom.ctest. Create the old file to include the new one for compatibility. This should prevent the long delays of CTest traversing the whole tree looking for CTestCustom.ctest files. 2007-08-31 14:51:09 -04:00
DartConfig.cmake ENH: switch to using cdash for submissions 2008-07-21 15:44:36 -04:00
DartLocal.conf.in ENH: remove superior dean i, no longer uses borland 2007-12-03 20:44:43 -05:00
doxygen.config BUG: fix for bug# 3921 INPUT wrong 2006-10-13 11:26:59 -04:00
Readme.txt STYLE: Remove trailing whitespace 2009-05-12 15:06:53 -04:00

This is CMake, the cross-platform, open-source make system.
CMake is free software under a BSD-like license, see Copyright.txt.
For documentation see the Docs/ directory once you have built CMake
or visit http://www.cmake.org.


Building CMake
==============


Supported Platforms
-------------------

MS Windows, Mac OS X, Linux, FreeBSD, Solaris, HP-UX, IRIX, BeOS, QNX

Other UNIX-like operating systems may work too out of the box, if not
it shouldn't be a major problem to port CMake to this platform. Contact the
CMake mailing list in this case: http://www.cmake.org/mailman/listinfo/cmake


If you don't have any previous version of CMake already installed
--------------------------------------------------------------

* UNIX/Mac OSX/MinGW/MSYS/Cygwin:

You need to have a compiler and a make installed.
Run the bootstrap script you find the in the source directory of CMake.
You can use the --help option to see the supported options.
You may want to use the --prefix=<install_prefix> option to specify a custom
installation directory for CMake. You can run the bootstrap script from
within the CMake source directory or any other build directory of your
choice. Once this has finished successfully, run make and make install.
So basically it's the same as you may be used to from autotools-based
projects:

$ ./bootstrap; make; make install


* Other Windows:

You need to download and install a binary release of CMake in order to build
CMake.  You can get these releases from
http://www.cmake.org/HTML/Download.html .  Then proceed with the instructions
below.


You already have a version of CMake installed
---------------------------------------------

You can build CMake as any other project with a CMake-based build system:
run the installed CMake on the sources of this CMake with your preferred
options and generators. Then build it and install it.
For instructions how to do this, see http://www.cmake.org/HTML/RunningCMake.html