| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
compilers without having to specifiy it in the intel compiler files
|
| |
|
|
|
|
|
|
| |
We teach the FindPackageTest to build a sample project that stores its
build tree in the user package registry using export(PACKAGE), and then
find it with find_package.
|
|
|
|
|
|
|
| |
We define the export(PACKAGE) command mode to store the location of the
build tree in the user package registry. This will help find_package
locate the package in the build tree. It simplies user workflow for
manually building a series of dependent projects.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A common user workflow is to build a series of dependent projects in
order. Each project locates its dependencies with find_package. We
introduce a "user package registry" to help find_package locate packages
built in non-standard search locations.
The registry explicitly stores locations of build trees providing
instances of a given package. There is no defined order among the
locations specified. These locations should provide package
configuration files (<package>-config.cmake) and package version files
(<package>-config-version.cmake) so that find_package will recognize the
packages and test version numbers.
|
|
|
|
|
|
| |
The commit "Split Intel compiler information files" moved some Linux
specific flags into the platform-independent Intel compiler info files.
This moves them back.
|
|
|
|
|
|
|
| |
The verification program entry point (main) is defined in a C source
file, so the C compiler should be used to link when only Fortran and C
are involved. The C++ compiler should still be used when the CXX option
is enabled.
|
| |
|
|
|
|
|
|
|
| |
We test that LINK_INTERFACE_MULTIPLICITY propagates through export() and
install(EXPORT) into dependent projects. A simple cycle of two archives
that need to be scanned three times ensures that the importing project
uses the multiplicity correctly.
|
|
|
|
|
| |
This tests the LINK_INTERFACE_MULTIPLICITY property for a cycle of three
static libraries that must be scanned three times to link properly.
|
|
|
|
|
|
|
|
|
| |
We create target property "LINK_INTERFACE_MULTIPLICITY" and a per-config
version "LINK_INTERFACE_MULTIPLICITY_<CONFIG>". It sets the number of
times a linker should scan through a mutually dependent group of static
libraries. The largest value of this property on any target in the
group is used. This will help projects link even for extreme cases of
cyclic inter-target dependencies.
|
|
|
|
|
| |
We enable verbose build output in the try_compile of the simple project.
This makes valuable information available in the case of failure.
|
| |
|
| |
|
|
|
|
|
|
| |
We need to do this KWSys configuration test in the CMake bootstrap
script to create a proper cmsys/Configure.hxx file. This fixes the
bootstrap script which was broken by the addition of the test to KWSys.
|
|
|
|
|
|
|
|
| |
The 'binary' openmode does not exist on all compilers. We define macro
<kwsys>_ios_binary, where <kwsys> is the KWSys namespace, to refer to
std::ios::binary if it exists and 0 otherwise. Sample usage:
kwsys_ios::ifstream fin(fn, kwsys_ios::ios::in | kwsys_ios_binary);
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
coming soon...
|
| |
|
|
|
|
| |
for ctest
|
| |
|
|
|
|
| |
specified, defaults to a MP level of 1 (non parallel)
|
| |
|
| |
|
| |
|
|
|
|
| |
duplicates when HDF5 is not found.
|
|
|
|
|
|
|
| |
In cmComputeLinkInformation::Compute we add implicit link information
from languages other than the linker language to the end of the link
line. This factors out that code into separate methods to improve
readability and organization.
|
|
|
|
|
| |
This removes the QUIET option from FortranCInterface_VERIFY in the
Fortran test to really test the detected interface everywhere.
|
| |
|
|
|
|
|
| |
This global property disallows cycles in the inter-target dependency
graph even among STATIC libraries. See issue #9444.
|
|
|
|
|
|
|
| |
This function builds a simple test project using a combination of
Fortran and C (and optionally C++) to verify that the compilers are
compatible. The idea is to help projects report very early to users
that the compilers specified cannot mix languages.
|
|
|
|
|
|
|
|
| |
We split the main detection logic into a Detect.cmake support module and
load it only when detection results are not already available. This
allows results computed by the main project to be used in try-compile
projects without recomputing them. The call to try_compile() need only
to pass FortranCInterface_BINARY_DIR through the CMAKE_FLAGS option.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This moves platform-independent SunPro compiler flags into separate
"Compiler/SunPro-<lang>.cmake" modules. Platform-specific flags are
left untouched.
|
|
|
|
|
|
| |
This moves platform-independent Intel compiler flags into separate
"Compiler/Intel-<lang>.cmake" modules. Platform-specific flags are
left untouched.
|
| |
|
|
|
|
|
| |
This module requires both C and Fortran to be enabled, so error-out if
they are not.
|
| |
|