| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
7c29a0c8 CMakeDetermineCUDACompiler: Drop out-of-date comment
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
1c60231c CUDA: Link to standard system libraries when linking as CUDA
8d75d8dc Tests: Add case for CUDA with C but not C++
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On Windows with MSVC-like host compilers we must honor the standard
libraries chosen by the `Platform/Windows-MSVC` module. Otherwise C
code linked into the CUDA binary that expects to have these libraries
available may not link.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
59ed323d CUDA: Do not use non-existent -Os flag for nvcc
|
| | |
| | |
| | |
| | |
| | | |
Fix the CUDA MinSizeRel configuration flags to avoid using the `-Os`
flag that nvcc does not support.
|
| |\ \ |
|
|\ \ \ \
| | |_|/
| |/| | |
|
| | | | |
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
44f3acb2 CUDA: Detect the toolkit include directories
|
| |/ /
| | |
| | |
| | |
| | | |
The `nvcc -v` output provides what include directories need to be added
to use the CUDA toolkit from other languages ( C/C++ ).
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
5ba2c9e5 VS: Add support for ASM_NASM language
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #16469
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
9837ed96 GoogleTest: Add module to contain gtest_add_tests independently
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Extract the `gtest_add_tests` macro from `FindGTest` into a separate
module. GTest or GoogleTest can be used by a project in a several
different ways, including installed libraries in the system, from an
ExternalProject, or adding the GTest source directory as a sub directory
of the project. As not all of these uses are supported by the FindGTest
module the useful `gtest_add_tests` macro is separated to easily enable
reuse.
Issue: #14151
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
e2ee0971 g++ knows about C++98 selection flags since at least 3.4
|
| | | | |
| | | | |
| | | | |
| | | | | |
https://gcc.gnu.org/onlinedocs/gcc-3.4.0/gcc/C-Dialect-Options.html#C-Dialect-Options
|
|\ \ \ \ \
| |/ / / /
|/| | | /
| | |_|/
| |/| |
| | | |
| | | | |
30abf145 Help: Fix cmake code block warnings produced by Sphinx 1.4
97917900 Utilities/Sphinx: Port qthelp css workaround to Sphinx 1.4
971384c2 Utilities/Sphinx: Port cmake extension to Sphinx 1.4
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Some of our "cmake" code blocks do not use fully valid CMake syntax
because they have placeholders for human reference. Sphinx has
never been able to properly lex and highlight these, but now warns.
Fix each block's syntax or change to a non-cmake block as appropriate.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
72ed051b CMakeDetermineCompilerId: check with and without user-specified flags
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Clang may raise an error when passed a `-march=` option that doesn't
correspond to the current target triple. CMake cannot pass the target
triple when determining the compiler id because it doesn't know how yet,
but it does pass along user-specified flags. This breaks when those
user-specified flags include `-march=`. Fix this use case by also
trying to find the compiler id without the user-specified flags.
Fixes: #16587
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
a3f71349 FindProtobuf: Add option to find static libraries on UNIX
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Add a `Protobuf_USE_STATIC_LIBS` input variable to optionally restrict
searches to static library names. This follows the approach of
`FindBoost`.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
28e87033 FeatureSummary: Update release notes
6f62c66b FeatureSummary: Add FeatureSummary_<TYPE>_DESCRIPTION global properties
f9bc8cfe FeatureSummary: Add DEFAULT_DESCRIPTION option to feature_summary
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The global property FeatureSummary_<TYPE>_DESCRIPTION can be defined for
each type to replace the type name with the specified string whenever
the package type is used in an output string.
|
| |/ /
| | |
| | |
| | |
| | | |
If enabled and only one package type is selected, it will print the
default title for the selected package type.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new variable allows specification of a custom root folder ID.
The implicit default is "ProgramFiles<64>Folder".
The "<64>" token is replaced by "" for 32-bit and "64" for 64-bit builds.
Inspired-By: Eric Backus
Fixes: #16573
|
|/ |
|
|\
| |
| |
| |
| | |
48aad9cd CPackProductBuild: Add options to sign packages
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
8a5cb84b AndroidTestUtilities: do not require ExternalData unconditionally
9d34e51c AndroidTestUtilities: ignore exit status of ls
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Attempting to use AndroidTestUtilities to simply install some local
files on device can result in the following error:
Neither ExternalData_URL_TEMPLATES nor ExternalData_OBJECT_STORES is set
We no longer require these ExternalData-specific variables to be set if
no such remote data files are requested.
Fixes: #16529
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
adb used to suffer from a bug where `adb shell` would return 0 irrespective
the exit status of the underlying process that it executed. This is now
fixed for newer versions of Android (N+).
As a result, attempting to `adb shell ls` a nonexistent file can now result
in a non-zero exit status. Updating check_device_file_exists to ignore the
exit status of `adb shell` fixes this bug for newer Android devices.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
cf0d8f1f FindHDF5: Restore HDF5_INCLUDE_DIR in all code paths
5564c017 FindHDF5: Restore fallback to static libraries
4908969f FindHDF5: Fix search with HDF5_ROOT
77f6d22a FindHDF5: Use keywords in find_library calls
3d5ad723 FindHDF5: Initialize/finalize internal search options variable
ae89967f FindHDF5: Fix command-line parsing argument extraction order
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This compatibility variable should be set no matter which method was
used to find HDF5. Even if `HDF5_INCLUDE_DIRS` was set by copying the
`HDF5_INCLUDE_DIR` value from `hdf5-config.cmake` it will not hurt to
copy the same value back.
Issue: #16566
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since commit v3.6.1~6^2~2 (FindHDF5: Fix h5cc arg parsing to work with
homebrew on Mac, 2016-07-11) we treated `HDF5_USE_STATIC_LIBRARIES` OFF
as a requirement for shared libraries. It is just supposed to be a
preference. Even if `HDF5_USE_STATIC_LIBRARIES` is not set we should
still fall back to finding static libraries if shared libraries are not
available.
Issue: #16566
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Refactoring in commit v3.6.0-rc1~72^2 (HDF5: Rework component searching
to correctly find HL for all bindings, 2016-05-12) turned off a large
amount of its logic when HDF5_ROOT is set. This caused use of the hdf5
compiler wrapper to extract all needed libraries (e.g. z, dl as
dependencies of hdf5 static libraries) to be skipped when using
HDF5_ROOT.
Fix the search logic to honor HDF5_ROOT in all code paths. Restrict the
search for hdf5-specific components to this root, but allow external
libraries to be found anywhere.
Fixes: #16566
|
| | | |
| | | |
| | | |
| | | | |
Clarify the purpose of each argument.
|
| | | |
| | | |
| | | |
| | | | |
While at it, use a more private name.
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Re-implement our internal `_HDF5_parse_compile_line` helper to process
command line arguments all at once and in order. Otherwise the
libraries named by absolute path and those named by `-l` arguments are
not kept in order.
The new implementation will not handle separate arguments like
`-I /path/to/include/dir` but I have not seen the HDF5 compiler
wrappers produce this form. If necessary the parsing loop can
be extended with a state variable to keep track of such pairs.
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | | |
a2a73935 FindMPI: Remove leading spaces from flags
93f29be2 FindMPI: Reset MPI_INCLUDE_PATH_WORK before use
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
See https://gcc.gnu.org/onlinedocs/gcc-4.0.0/gcc/Option-Summary.html
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
645dd3ca FindCUDA: Fix typo in CUDA_DETECT_INSTALLED_GPUS doc string
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
88c4576b FindGSL: Fix gl_version.h extraction regex
|
| | |
| | |
| | |
| | | |
Fix the regex to match versions with only two digits, such as `2.3`.
|