| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
use it for them.
|
| |
|
|
|
|
|
|
| |
These compilers warn and return 0 for unrecognized flags. We fix the
compiler flag check macros by looking for a warning in the output. We
also update the regex for GNU on older Macs. See issue #9516.
|
|
|
|
|
|
| |
This compiler warns and returns 0 for unrecognized flags. We fix the
compiler flag check macros by looking for a warning in the output.
See issue #9516.
|
|
|
|
|
|
| |
These compilers warn and return 0 for unrecognized flags. We fix the
compiler flag check macros by looking for a warning in the output.
See issue #9516.
|
|
|
|
|
|
| |
This teaches the CHECK_C_SOURCE_COMPILES and CHECK_CXX_SOURCE_COMPILES
macros to recognize a FAIL_REGEX option. If they see the regular
expression in the output of the test compilation, the check fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit improves formatting and style of the documentation for the
general-purpose compiler check macros:
CHECK_C_COMPILER_FLAG
CHECK_C_SOURCE_COMPILES
CHECK_C_SOURCE_RUNS
CHECK_CXX_COMPILER_FLAG
CHECK_CXX_SOURCE_COMPILES
CHECK_CXX_SOURCE_RUNS
This sytle is more consistent with CMake command documentation.
It also looks nicer in the generated documentation text files.
|
|
|
|
| |
Alex
|
|
|
|
| |
ARCHs are specified by the user then no flags are set. We no longer use CMAKE_OSX_ARCHITECTURES_DEFAULT.
|
|
|
|
|
|
|
|
|
| |
Now gcc is queried also for the builtin definitions, and they are then added
to the .cproject file. This should make the preprocessor highlighting in
eclipse work better (#9272)
Patch mostly from Miguel.
Alex
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In Platform/Linux.cmake we add GNU flags as default for the platform
which breaks non-GNU compilers. Later we should refactor these flag
files to put compiler-specific flags only in files loaded for each
compiler. Until then this commit fixes the XL C++ compiler flags on
Linux by erasing the GNU flags. See issue #9469.
|
| |
|
|
|
|
| |
Alex
|
|
|
|
| |
backwards compatible
|
|
|
|
|
|
|
|
|
| |
-now supports specifying minimum required version
-now supports ruby 1.8 and 1.9
-uses find_package_handle_standard_args() now
-fix #6212 and using a lot of ideas from the file attached there
Alex
|
|
|
|
|
|
| |
built by default)
Alex
|
|
|
|
|
|
| |
they must be preprocessed
Alex
|
|
|
|
|
|
|
|
|
| |
When CMAKE_Fortran_COMPILER and ENV{FC} are not defined CMake searches
for an available Fortran compiler. This commit teaches the search code
to look for compiler executables next to the C and C++ compilers if they
are already found. Furthermore, we bias the compiler executable name
preference order based on the vendor of the C and C++ compilers, which
increases the chance of finding a compatible compiler by default.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CMakeExportBuildSettings and CMakeImportBuildSettings modules used
to export compiler paths and flags from one project and import them into
another. The import process would force the settings on the including
project.
Forcing settings helped long ago when compiler ABIs changed frequently
but is now just a nuisance. We've deemed the behavior harmful so this
commit simply removes it. The modules and macros now error out if
included or called from a project that requires CMake 2.8 or higher.
|
|
|
|
| |
ExternalProject.cmake module. Follow the cmake function naming convention, using a ModuleFileName_ prefix. Locate stamp files under a CMAKE_CFG_INTDIR subdir of the stamp dir so that debug and release builds have separate stamp files for Visual Studio builds. If no CMAKE_GENERATOR argument is given to ExternalProject_Add, default to using the parent project's cmake generator.
|
| |
|
|
|
|
| |
better automatically on Windows. Thanks to Dave Partyka for developing the patch.
|
| |
|
|
|
|
| |
since it is a more accurate name.
|
|
|
|
| |
number of tests. Also some preliminary changes for batching ctest jobs
|
| |
|
| |
|
| |
|
|
|
|
| |
compilers without having to specifiy it in the intel compiler files
|
|
|
|
|
|
| |
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 enable verbose build output in the try_compile of the simple project.
This makes valuable information available in the case of failure.
|
| |
|
| |
|
| |
|
|
|
|
| |
duplicates when HDF5 is not found.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
search.
|
|
|
|
| |
Put functionality directly into ExternalProject.cmake itself so that these modules do not end up in the upcoming release of CMake.
|
| |
|
| |
|