summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
* Include relative path in generated qrc and uic files. Fixes #10413.Clinton Stimpson2010-03-171-2/+2
|
* Change to use FindX11.cmake. Should fix #9929.Clinton Stimpson2010-03-172-54/+26
|
* Add support for libXi.Clinton Stimpson2010-03-171-0/+10
|
* ENH: Hook in GetPrerequisites to override item typeMichael Wild2010-03-171-0/+11
| | | | | | The hook is called gp_resolved_file_type_override. Signed-off-by: Michael Wild <themiwi@users.sourceforge.net>
* ENH: Clarify a doc string. Fixes #10358.Clinton Stimpson2010-03-171-1/+3
|
* ENH: Modify how OpenGL is searched for, that is, use FindOpenGL.cmake.Clinton Stimpson2010-03-171-17/+5
|
* Support multiple arguments in CC,CXX,FC valuesBrad King2010-03-151-0/+1
| | | | | | | | | Teach compiler identification to support values such as export CC='gcc -g -O2' by separating the arguments on spaces. We already do this for the values of CFLAGS, CXXFLAGS, and FFLAGS.
* Add a new registry key to check for the location of MPICH2.David Partyka2010-03-111-0/+1
|
* BUG #9419: Added wxWidgets_EXCLUDE_COMMON_LIBRARIES option.Miguel A. Figueroa-Villanueva2010-03-071-2/+10
| | | | | | | | | | This allows the user not to link to the common libraries, which are regularly required. The user must specify all libraries that he does want to link in the find_package line (png tiff jpeg zlib regex expat). --HG-- extra : rebase_source : df29f96c957600629a34a1c5fafb8b3d6f274e22
* Fix Qt with OpenGL on the Mac.Bill Hoffman2010-03-101-1/+15
|
* Add .git .bzr and .hg to the list of default CPack ignore directories.Bill Hoffman2010-03-081-1/+1
|
* If tests failed on the last run, have them run first next timeZach Mullen2010-03-011-1/+0
|
* Configurable path to CTest cost data fileZach Mullen2010-03-011-0/+4
| | | | Allow the user to set the CMake variable CTEST_COST_DATA_FILE, which will be used to store the cost data from test runs. If not set, defaults to the original location in the build tree Testing/Temporary dir.
* Suppress GNU flag -fPIC on WindowsBrad King2010-02-191-0/+2
| | | | | | | | Commit "Modernize GNU compiler info on Windows" (2009-12-02) reorganized GNU flags on Windows but let -fPIC slip through for compilation of objects in shared libraries. While this flag is valid on most GNU compiler platforms we need to suppress it in Windows-GNU.cmake just as we already do in CYGWIN-GNU.cmake.
* Add support for QtDeclartive module.Clinton Stimpson2010-02-182-3/+12
|
* A few small changed from Pat Marion (in VTK CVS too)Marcus Hanwell2010-02-171-2/+2
|
* Applied patch from Pat Marion - modules header macro.Marcus Hanwell2010-02-171-6/+12
| | | | | | This modifies the behavior of PYTHON_WRITE_MODULES_HEADER, should be backwards compatible. Also marked a couple of the variables generated by adding Python modules as advanced.
* Do not force frameworks on Mac OS X - never worked well.Marcus Hanwell2010-02-171-16/+0
|
* FortranCInterface: Fix PathScale detection againBrad King2010-02-161-0/+6
| | | | | | | | | | | PathScale Fortran mangles module symbols as "MY_SUB.in.MY_MODULE" and also requires "my_module_" when the module is imported. We cannot provide the symbol with ".in." mangling so we should not provide "my_module_" because it would duplicate the one in the Fortran-provided object file. Commit "FortranCInterface: Fix PathScale detection" (2010-01-22) already made the same fix for the non-underscore module case.
* Make a common function that prints the status during the checks for working ↵David Cole2010-02-124-9/+36
| | | | compilers. Call it from all of the CMakeTesten_US.UTF-8Compiler.cmake files. In the message, print the full path to the tested compiler only for the Makefile generators. For Xcode and Visual Studio generators, print the generator instead so that users are not misled with the full path to a compiler that the generator may not even use. Xcode and Visual Studio have their own mechanisms for choosing the compiler to use during try_compile and build...
* 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.
generated by cgit v0.12 at 2025-01-09 15:04:32 (GMT)