summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* KWSys Nightly Date StampKWSys Robot2010-02-081-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-071-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-061-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-051-1/+1
|
* Fix HPUX issue with test, by doing the query to cdash for its version before ↵Bill Hoffman2010-02-051-1/+3
| | | | any test is started.
* Support for relative paths to executables in MemCheck tests. Also fixed a ↵Zach Mullen2010-02-041-1/+3
| | | | bug causing memcheck args to be overwritten repetitively.
* KWSys Nightly Date StampKWSys Robot2010-02-041-1/+1
|
* Re-enabled Scheduler test and fixed the underlying problem.Zach Mullen2010-02-032-11/+11
|
* Disable Scheduler test until underlying problem is resolved.Zach Mullen2010-02-031-10/+10
|
* Add unit test to ensure that CTestCostData scheduling works correctlyZach Mullen2010-02-035-0/+79
|
* KWSys Nightly Date StampKWSys Robot2010-02-031-1/+1
|
* 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.
* KWSys Nightly Date StampKWSys Robot2010-02-021-1/+1
|
* Fix line length style issue.David Cole2010-02-021-1/+2
|
* Add alternate per-vendor compiler id detectionBrad King2010-02-013-0/+72
| | | | | | | 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.
* KWSys Nightly Date StampKWSys Robot2010-02-011-2/+2
|
* KWSys Nightly Date StampKWSys Robot2010-01-311-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-01-301-1/+1
|
* Fix issue #10155 - default value of CMAKE_OSX_DEPLOYMENT_TARGET should ↵David Cole2010-01-297-34/+47
| | | | 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.
* KWSys Nightly Date StampKWSys Robot2010-01-291-1/+1
|
* 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
|
* KWSys Nightly Date StampKWSys Robot2010-01-281-1/+1
|
* -remove unnecessary debug outputAlexander Neundorf2010-01-271-1/+0
| | | | Alex
* KWSys: Remove $Id$ from MD5.cBrad King2010-01-271-1/+0
| | | | | This CVS keyword was copied into the file with the rest of the implementation. It has no meaning outside its original project tree.
* KWSys Nightly Date StampKWSys Robot2010-01-271-1/+1
|
* COMP: remove exporting String as VS10 attempts to export its parents ↵Dave Partyka2010-01-261-1/+1
| | | | (basic_string) which causes all kinds of multiply defined symbols at link time.
* KWSys Nightly Date StampKWSys Robot2010-01-261-1/+1
|
* Avoid PathScale cmd-line bug in TryCompile testBrad King2010-01-251-2/+8
| | | | | | | | | | | | | | | | | | | | The PathScale compiler silently accepts unknown options that start in more than one '-': $ touch foo.c $ pathcc -c foo.c --junk $ echo $? 0 $ pathcc -c foo.c ---junk $ echo $? 0 $ pathcc -c foo.c -junk pathcc ERROR parsing -junk: unknown flag $ echo $? 2 We teach the TryCompile to pass a bogus flag with only one '-' instead of three '-'s for this compiler.
* Skip Fortran module mangling test on PathScaleBrad King2010-01-251-1/+1
| | | | | | We disable this test because PathScale Fortran mangles module symbols as "MYSUB.in.MYMODULE" so we cannot interface with it from C. We already did this for SunPro and MIPSpro.
* KWSys Nightly Date StampKWSys Robot2010-01-251-1/+1
|
* -make paths with spaces work in the CodeBlocks generator with MinGW (#10014)Alexander Neundorf2010-01-241-6/+10
| | | | Alex
* KWSys Nightly Date StampKWSys Robot2010-01-241-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-01-231-1/+1
|
* 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
* KWSys Nightly Date StampKWSys Robot2010-01-221-1/+1
|
* 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.
* KWSys Nightly Date StampKWSys Robot2010-01-211-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-01-201-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-01-191-1/+1
|
* -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
* KWSys Nightly Date StampKWSys Robot2010-01-181-1/+1
|
* -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
* KWSys Nightly Date StampKWSys Robot2010-01-171-1/+1
|
generated by cgit v0.12 at 2025-09-07 23:07:44 (GMT)