summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
* Do not warn for unknown CTest UPDATE_TYPEBrad King2010-02-101-7/+0
| | | | | | | | | | | | | In the CTest module we previously warned if the source directory did not contain known version control directories. The message was: "CTest cannot determine repository type. Please set UPDATE_TYPE to 'cvs' or 'svn'. CTest update will not work." This was confusing when building sources from a tarball. Furthermore, we now support many more version control tools. This feature is now mature enough that the warning causes confusion more than it provides real help. We simply remove it.
* Detect Git repositories for CTest UPDATE_TYPEBrad King2010-02-101-0/+7
| | | | | The CTest module configures the command-line CTest dashboard mode. We teach it to recognize .git directories.
* Simplify CTest.cmake module with ELSEIFBrad King2010-02-101-29/+17
| | | | | We use ELSEIF to simplify the cascading IF blocks for detecting version control tools.
* Fix for bug #10257, NSIS could remove a PATH if it was too longBill Hoffman2010-02-091-0/+9
|
* Moved call to cache CDash version information to cmCTest::initialize. Also ↵Zach Mullen2010-02-081-0/+1
| | | | added a 3 second timeout when requesting the version from the server. Added an option to the CTestConfiguration that will be used to determine whether to query the version information at all. (Behavior for this setting is not yet defined.) Updated CMake's local CDash version setting to 1.6.
* Recognize the Compaq Fortran compilerBrad King2010-02-021-0/+5
| | | | | | | | | | The compiler documents symbols _DF_VERSION_ and _VF_VERSION_ but they do not seem to be available to the preprocessor. Instead we add a vendor query table entry for Compaq. Running "f90 -what" produces Compaq Visual Fortran Optimizing Compiler Version ... This clearly identifies the compiler.
* Add alternate per-vendor compiler id detectionBrad King2010-02-011-0/+40
| | | | | | | At least one Fortran compiler does not provide a preprocessor symbol to identify itself. Instead we try running unknown compilers with version query flags known for each vendor and look for known output. Future commits will add vendor-specific flags/output table entries.
* Fix issue #10155 - default value of CMAKE_OSX_DEPLOYMENT_TARGET should ↵David Cole2010-01-296-31/+40
| | | | always be the empty string. When the value of CMAKE_OSX_DEPLOYMENT_TARGET is the empty string, the -mmacosx-version-min flag should not show up on the compiler command line. The logic for selecting default value of CMAKE_OSX_SYSROOT is orthogonal to and independent of the value of the deployment target. The default value for CMAKE_OSX_SYSROOT is the SDK that corresponds to the current version of Mac OSX on which cmake is running.
* Add -rpath for cuda libraries on Apple. They use @rpath in the library link ↵James Bigler2010-01-281-0/+8
| | | | names.
* Updated the documentation on what kinds of flags you can use when setting ↵James Bigler2010-01-281-3/+6
| | | | target properties.
* Define __CUDACC__ during dependency scanning, since NVCC doesn't.James Bigler2010-01-281-0/+7
|
* -remove unnecessary debug outputAlexander Neundorf2010-01-271-1/+0
| | | | Alex
* FortranCInterface: Fix PathScale detectionBrad King2010-01-222-0/+7
| | | | | | | PathScale Fortran mangles module symbols as "MYSUB.in.MYMODULE" and also requires "mymodule_" when the module is imported. We cannot provide the symbol with ".in." mangling so we should not provide "mymodule_" because it would duplicate the one in the Fortran-provided object file.
* -also put CMAKE_LINKER in the C and CXX compiler information filesAlexander Neundorf2010-01-222-0/+2
| | | | | | This is already done for assembler and is necessary for e.g. Symbian. Alex
* Do not export all symbols from DLLs on CygwinBrad King2010-01-211-2/+3
| | | | | | | | | | In commit "use export all symbols on cygwin" (2003-01-21) we started passing -Wl,--export-all-symbols when linking shared libraries. Now cygwin exports all symbols automatically if no symbols are explicitly exported. When symbols are explicitly exported we want to honor that narrow interface. Therefore this flag should not be passed. Change based on patch from issue #10122.
* Fix CMAKE_DL_LIBS on CygwinBrad King2010-01-211-1/+0
| | | | | | | | The variable should contain the name of a library needed to link the symbol equivalent to dlopen. On Cygwin no special library is needed, and certainly not "gdi32". Change based on patch from issue #10122.
* Add PathScale shared library flags on LinuxBrad King2010-01-214-0/+31
| | | | | | | | We add platform-specific compiler information files Platform/Linux-PathScale-<lang>.cmake to enable -fPIC and -shared flags for shared libraries.
* -make the imported targets feature of FindQt4.cmake fully backwards compatibleAlexander Neundorf2010-01-181-42/+110
| | | | | | | | | | | After discussing with Brad and Clinton: -the namespace for the imported targets is now "Qt4::", tested with Makefiles, Visual Studio and XCode projects -the imported targets are always created -if QT_USE_IMPORTED_TARGETS is set to TRUE (it defaults to FALSE), the QT_QTFOO_LIBRARY variables are set to point to these imported targets, otherwise the old behaviour is used. -on OSX if Qt has been found as framework, disable QT_USE_IMPORTED_TARGETS, since cmake doesn't handle the framework directory as location of the library correctly Alex
* Put quotes arounds strings when doing STREQUAL.Clinton Stimpson2010-01-181-2/+2
|
* some tweaks as suggested by Brad (no functional changes)Alexander Neundorf2010-01-181-16/+4
| | | | | | | | | -set the type of the IMPORTED libraries to UNKNOWN, this way also on Windows only the "LOCATION" property has to be set -the if() around the SET(QT_${basename}_FOUND 1) was useless (always true) -the mapping of the configuration types DEBUG and PROFILE did not belong here Alex
* -create imported library targets for the Qt4 libsAlexander Neundorf2010-01-171-34/+32
| | | | | | | | | | | | | | | | | This commit syncs FindQt4.cmake again with KDEs version. Now for every Qt library an imported target with the name Qt4ImportedTarget__<LIBNAME> is created. This way we can now finally handle the release and debug versions of the Qt libraries correctly. Also, if a Qt-using project A installs a file with exported targets, these targets now depend on the imported Qt targets, e.g. Qt4ImportedTarget__QtCore. The location of QtCore is then resolved at buildtime of project B, which uses the exported targets from project A. Before this patch the full path to the QtCore on the original build machine of project A was stored, so this had to match the directory layout on the build machine for project B. Alex
* Fix bug #10114. Find phonon on some installations.Clinton Stimpson2010-01-131-0/+10
|
* Do not find cyg*.dll on CygwinBrad King2010-01-131-2/+2
| | | | | | | | | | | | | | While Cygwin supports linking directly to .dll files, the behavior is now discouraged. All Cygwin packages now provide import libraries of the form lib*.dll.a and CMake has built the import libraries for years. We believe it is now safe to stop explicitly searching for .dll files because their import libraries will always be available when the corresponding header files are available. Users can always set find_library cache entries to point at a .dll file by hand if they really must use one. Change based on patch from issue #10122.
* Fix KDE3 .la file format on CygwinBrad King2010-01-131-1/+5
| | | | | We teach KDE3Macros.cmake to generate .la files on Cygwin that match those produced by libtool. See issue #10122.
* Search prefix /usr before root prefix /Brad King2010-01-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit "Find locally installed software first" made /usr/local the first prefix searched to be consistent with the Filesystem Hierarchy Standard: http://www.pathname.com/fhs/ The standard also implies that the root prefix "/" should not have any package or development files. The "/bin" and "/lib" directories should have only minimal contents to boot the system. No "/include" ever exists. This commit re-orders the search path prefix list from /usr/local / /usr to /usr/local /usr / to prefer package and development files over low-level system files. See issue #10136. On Cygwin /usr/lib == /lib and /usr/bin == /bin. This change also makes search results report locations as "/usr/..." instead of "/lib/...". See issue #10122.
* Use if(CYGWIN) instead of if(WIN32 AND UNIX)Brad King2010-01-131-2/+2
| | | | | CMake has defined CYGWIN on Cygwin for years, so we no longer need the legacy form of the test. Change based on patch from issue #10122.
* PathScale C/C++/Fortran Compiler InformationBrad King2010-01-134-0/+43
| | | | | | | | | | We add compiler information files Compiler/PathScale-<lang>.cmake to specify PathScale compiler information for C, C++, and Fortran languages. We use a macro in Compiler/PathScale.cmake to consolidate the information common to all languages.
* Recognize the PathScale C/C++/Fortran compilersBrad King2010-01-133-0/+8
|
* Restore -rdynamic in Linux build rulesBrad King2010-01-132-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | The commit "Drop -rdynamic from Linux build rules" removed default use of the flag on Linux. It was expected to be compatible because any project using plugins should set ENABLE_EXPORTS on its executables to export their symbols for use by the plugins in a cross-platform way. However, it is possible to build without ENABLE_EXPORTS and load plugins that do not link to any symbols from the executable explicitly. These plugins may need to see RTTI and other executable symbols needed by the language implementation. Executables using such plugins were broken by the change. If we want to remove the -rdynamic flag in the future we should do so in a compatible way. At that time we should also remove equivalent flags on other platforms (like -bexpall on AIX). We will either need a policy or an explicit API to disable symbol exports on executables. The primary purpose of the above-mentioned commit was to avoid passing the -rdynamic flag to compilers on Linux that do not support it. In this commit we restore the flag but only on GNU and Intel compilers which are known to support it. See issue #9985.
* Create Linux GNU compiler flag consolidation macroBrad King2010-01-134-0/+28
| | | | | This macro will be used for GNU compiler flags that are specific to Linux but not to any language.
* Detect Fortran ABI InformationBrad King2010-01-122-2/+44
| | | | | | | Implement Fortran 32/64-bit ABI detection on some platforms. We need to set CMAKE_SIZEOF_VOID_P correctly in Fortran-only projects so that the find_library() command knows whether to look for 64-bit binaries. We also detect ELF binaries to enable RPATH replacement. See issue #10119.
* Changed warning string to use the WARNING flag.James Bigler2010-01-081-1/+1
|
* Reordered the arguments, so that user generated arguments go last and thus ↵James Bigler2010-01-081-7/+7
| | | | get precedence.
* Disable the --host-compilation flag for CUDA >= 3.0 since it is derecated.James Bigler2010-01-081-1/+5
|
* Fix Issue #9792, remove superfluous output when not searching for ↵Philip Lowman2010-01-051-18/+34
| | | | COMPONENTS, add 1.41 to the search
* Fix issue #10065, "FindGTest.cmake doesn't handle spaces around arguments to ↵Philip Lowman2010-01-051-7/+10
| | | | | | TEST/TEST_F macro". Also improved the documentation.
* Fixes issue #9862 by adding official msvc import library names to FindCURLPhilip Lowman2010-01-051-4/+7
|
* Should get FindGTK2 working with fink on Mac OSXPhilip Lowman2010-01-051-1/+9
|
* make FindRuby work on Windows e.g. with ruby 1.9.1 (version string was ↵Alexander Neundorf2010-01-031-4/+5
| | | | | | constructed wrong) Alex
* Fix issue with SDK not matching initial deployment target chosen by setting ↵David Cole2009-12-231-31/+37
| | | | the MACOSX_DEPLOYMENT_TARGET environment variable. The problem was that we were setting the initial SDK value based on our own internal default value for deplyment target rather than the user's environment variable choice. The solution is to base the default value for the SDK on the deployment target variable after initially caching the deployment target... Every time I'm in this code I think I leave it cleaner, only to be proven otherwise. Let's give this one a whirl. Bleh.
* fix logic of _QT4_ADJUST_LIB_VARS() wrt. release- and debug librariesAlexander Neundorf2009-12-231-13/+15
| | | | | | | | Now the case that both the release- and the debug-version of a library is handled first, because otherwise we always ran into this branch, since the debug-only and the release-only branch also set both variables. Alex
* -handle the REQUIRED and QUIET keywords in FindJNI.cmake, also set JNI_FOUNDAlexander Neundorf2009-12-211-0/+5
| | | | Alex
* Added support for CTest awareness of the CDash version. This will help ↵Zach Mullen2009-12-211-0/+1
| | | | forward compatibility for both tools. Note that this changeset effectively makes the default to disable output compression. Now, to enable output compression, the CDASH_CTEST_VERSION must be explicity set to >= 1.6. Automated detection of the CDash version is the next step.
* sync with KDE: sort the libs alphabeticallyAlexander Neundorf2009-12-201-9/+8
| | | | Alex
* -add support for QtMultimedia and some sync with KDEAlexander Neundorf2009-12-201-6/+11
| | | | | | | -the QtMultimedia module is new since Qt 4.6.0 -sort the doc entries alphabetically Alex
* FindHDF5: Fix Windows compile-line parsingBrad King2009-12-181-6/+6
| | | | | | | We modify the signature of _HDF5_parse_compile_line to pass the command line variable name rather than the command line itself. Otherwise the CMake language MACRO implementation tries to parse the command line as CMake syntax, which does not like backslashes.
* New CheckTypeSize for OS X Universal BinariesBrad King2009-12-174-137/+201
| | | | | | We re-implement this module to support architecture-dependent type sizes. In the mixed-size case we generate C preprocessor code to select the detected type size for each architecture.
* Fix for bug 9960, add support for MSVC10 runtime dlls.Bill Hoffman2009-12-171-0/+69
|
* -better support for Qt4 as frameworksAlexander Neundorf2009-12-162-4/+10
| | | | | | | | | | | before this patch -F<framework> dir had to be added manually in some way when using Qt4 installed as framework and when using FindQt4.cmake directly, i.e. without UseQt4.cmake. With this patch the framework dir is automatically added to QT_INCLUDE_DIR when Qt is installed as a framework. Ok by Clinton, tested already in KDE by Mike Arthur. Alex
* Fix issue #10055 - add documentation for the CPack Mac OSX only Bundle ↵David Cole2009-12-151-0/+21
| | | | | | generator. Thanks to Tim Shead for the patch.
generated by cgit v0.12 at 2024-09-23 10:28:23 (GMT)