| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
3fd9f4ab Xcode: Add test for schema generation
cf13e495 Xcode: Control schema generation via variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !577
|
| |
| |
| |
| | |
Issue: #15441
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
65481a60 CUDA: Work around VS limitation in CudaOnly.WithDefs test
8cae24a1 VS: Add more CUDA flag table entries
6ca4f222 VS: Add support for the CUDA_SEPARABLE_COMPILATION property
94255511 VS: Select CUDA code generation architectures
253594d0 VS: Select the CUDA runtime library
4def02a3 VS: Place CUDA host compiler options in proper project file fields
29f07b08 VS: Do not pass CUDA compile options to C compiler
b966f489 VS: Do not use absolute paths to CUDA sources
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !566
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Parse the `-gencode=`, `-arch`, and `-code` flags and generate a
`CodeGeneration` field in the project file.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Parse the `-cudart=` option and add a corresponding `CudaRuntime`
field to the generated project file. Also add a matching `.lib`
to the list of libraries linked.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The CUDA Toolkit's VS integration provides abstractions for host
compiler options for `nvcc` to pass through `-Xcompiler` to the host
MSVC. Populate our secondary flag table and use it to remove flags from
the `AdditionalCompilerOptions` in favor of their abstractions.
Unfortunately a bug in the CUDA 8.0 VS integration prevents us from
passing anything in `AdditionalCompilerOptions` reliably. After taking
out the flags that have dedicated abstractions, drop the rest.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The CUDA Toolkit's VS integration does not properly compute the
intermediate files directory location when the path to the source
file is absolute.
|
| | |
| | |
| | |
| | | |
Generate the `CudaCompile` elements in `.vcxproj` files.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The CUDA Toolkit's VS integration defines abstractions for both options
to `nvcc` and options to pass through `-Xcompiler` to the host MSVC.
We need a separate flag table to parse each set of flags into the
corresponding abstractions. Add empty placeholders for these tables.
|
| | | |
|
| | |
| | |
| | |
| | | |
Remove a flag from the map and return its value.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This will allow a client to parse flags, replace the flag tables, and
then re-parse a field in which flags for a secondary tool were
collected.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
If `CMAKE_GENERATOR_TOOLSET` does not have a `cuda=...` field then
find available CUDA toolsets and choose the highest version.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The NVIDIA CUDA Toolkit provides MSBuild toolset files for integration
with Visual Studio. Multiple versions may be installed so we need a way
to tell our VS generators which CUDA toolset to use. Extend the
`CMAKE_GENERATOR_TOOLSET` specification to provide a `cuda=...` field
specifying the version number.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Run MSBuild on a simple `.vcxproj` file to extract the location of the
toolset definitions. This will later be useful for looking at available
BuildCustomizations.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f36eaf6a Refactor WINDOWS_EXPORT_ALL_SYMBOLS implementation
25d261ef Refactor module definition file selection
1e0a9ac4 Refactor module definition source enumeration
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !570
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use `cmGeneratorTarget::ModuleDefinitionInfo` to combine the
implementation of `WINDOWS_EXPORT_ALL_SYMBOLS` with that of using a
`.def` file as a source. Only one of these could be used within a
single target before anyway.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Create a `ModuleDefinitionInfo` structure for each configuration of a
target to hold corresponding information about the selected module
definition file (`.def` source).
|
| |/ /
| | |
| | |
| | | |
Add a `cmGeneratorTarget::GetModuleDefinitionSources` method.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
83be64d9 Merge branch 'upstream-KWSys' into update-kwsys
8ba8b553 KWSys 2017-03-07 (5da8cfe0)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !576
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* upstream-KWSys:
KWSys 2017-03-07 (5da8cfe0)
|
| |_|/
|/| | |
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
d9bdcf34 Tests: Add x32 tests to test suite
5b6d354f Help: Add notes for topic 'x32-abi'
bed9c73d Modules: Add x32-abi support to hard-coded paths
462cf254 Add support for x32-abi
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !532
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Detect x32-abi through CMakeCompilerABI infrastruture and use this
information at runtime to determine the correct library paths with
`FIND_LIBRARY_USE_LIBX32_PATHS`.
Fixes: #15994
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
bd8b5401 VS: Do not treat custom targets as CSharp targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !557
|
| | |
| | |
| | |
| | | |
Fixes: #16697
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
322425fa cmStateTypes: document that the ordering of targets is important
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !560
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The ordering is assumed in many places throughout the code and
modification of the enumeration should be done carefully.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
f5c4dada cmFileMonitor.h: Include cmConfigure.h first
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !562
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We need this to make Large File Support definitions consistent with
other translation units.
|
| |/ / /
|/| | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
485685fd Revert "Remove CTestTestfile.cmake when BUILD_TESTING is OFF"
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !553
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
This reverts commit v3.8.0-rc1~305^2 (Remove CTestTestfile.cmake when
BUILD_TESTING is OFF, 2016-11-14). It breaks projects that never enable
testing but create their own `CTestTestfile.cmake` manually instead.
|
| | | | |
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \ \ \ \ |
|