Iyyappa Murugandi authored 8 years ago and Brad King committed 8 years ago

The Visual Studio Setup team releases a `Setup.Configuration.h` header
under the MIT License for use by external applications to interact with
the Visual Studio Installer tool [1].  Import it into our source tree
for use by CMake.

[1] https://github.com/microsoft/vs-setup-samples

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

caeb6d1d FindGit: Fix check for Windows host

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

c59811a2 CUDA: Tests now state why they are failing when no CUDA card is found.

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

a12d8a03 FindPythonLibs: Tolerate call with PYTHON_LIBRARY already a list

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

6271df8f Makefile,Ninja: De-duplicate MSVC compiler PDB path selection

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

5c6c0344 C# support: add compiler detection for MSVC

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

40e56149 Copyright.txt: Update year range to end in 2017

Add a helper to cmCommonTargetGenerator instead of duplicating it
in cmMakefileTargetGenerator and cmNinjaTargetGenerator.

José Simões authored 8 years ago and Brad King committed 8 years ago

When cross-compiling to or from a Windows platform we should still
find a Git for the host environment.

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

9fdad82c FindPNG: Fix small typo fix in module help

Francois Budin authored 8 years ago and Brad King committed 8 years ago

`PYTHON_LIBRARY` may contain a list because of `SelectLibraryConfigurations`.
If it is the case, the list can be:

    optimized;<FILEPATH_TO_RELEASE_LIBRARY>;debug;<FILEPATH_TO_DEBUG_LIBRARY>

Instead of directly using the value of `PYTHON_LIBRARY` in the CMake
function `get_filename_component()`, we loop over the content of the
relevant parts of `PYTHON_LIBRARY` and `PYTHON_DEBUG_LIBRARY` whether
they are lists or not.

Suggested-by: Brad King <brad.king@kitware.com>

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

f1739418 CodeLite: Make build/clean/rebuild operations optionally target-centric

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

58f02aaa Help: Clarify meaning of CMAKE_CL_64

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

da03e2d6 Merge branch 'upstream-KWSys' into update-kwsys
a9ea66bd KWSys 2016-12-14 (95a7e234)
24130757 update-kwsys: Update repository URL

* upstream-KWSys:
  KWSys 2016-12-14 (95a7e234)

Kitware Robot authored 8 years ago and Brad King committed 8 years ago

Code extracted from:

    https://gitlab.kitware.com/utils/kwsys.git

at commit 95a7e234ffd0c6bdfaa8b21c59a119198c050164 (master).

Upstream Shortlog
-----------------

Ben Boeckel (1):
      e0967411 Add a script to help update third-party sources

Brad King (10):
      98505f79 Add script to update GitSetup from upstream
      365edba8 GitSetup: Tell Git not to export .gitattributes
      41a7fe5b Add pre-commit hook to check whether SetupForDevelopment must re-run
      17a1200c Convert developer setup scripts away from Gerrit Code Review
      5f206c3a Tell Git to use a distinct conflict marker size in `.rst` files
      33f828d4 README: Convert from `.txt` to `.rst` markup
      56b707dd README: Add section about reporting bugs
      140357ea CONTRIBUTING: Document contribution through the Kitware GitLab Instance
      4b7bf8e4 Tell Git not to export any `.sh` or `.bash` scripts
      e25eb8dc CONTRIBUTING: Add step for running developer setup script

GitSetup Upstream (3):
      fed3d191 GitSetup 2012-09-27 (341043cf)
      a0144297 GitSetup 2016-12-13 (8af10838)
      868c1e68 GitSetup 2016-12-13 (cd5ada6d)

KWSys is now hosted on Kitware's GitLab instance.

Closes: #16504

Minze Zwerver authored 8 years ago and Brad King committed 8 years ago

When `CMAKE_CODELITE_USE_TARGETS` is enabled, these operations should
be target-centric too.

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

e3f404fe CUDA: Implement nvcc implicit link line extraction more robustly

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

c5df1f16 Regenerate lexer source code

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

55da7e50 VS: add support for .NET references with hint paths

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

53b5d634 GNUInstallDirs: Set UNINITALIZED cache properties to type PATH
c968213d GNUInstallDirs: Unify path logic into helper macros

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

23a35edf pre-commit: Update KWSys rejection message for new upstream location

Daniel Pfeifer authored 8 years ago and Brad King committed 8 years ago

Revise the manual procedure in the `*Lexer.in.l` files.  Some of our
post-processing steps are no longer necessary with the current set of
supported compilers.  Some steps changed with newer versions of flex.

Then regenerate all lexers with flex version 2.6.1.

Do not assume that the implicit link line is the last line of the output
from `nvcc -v`.  Instead first find the `LIBRARIES=` line, and then look
for that content on a later line.  It appears twice.  First on a call to
`nvlink`, which we ignore.  Later it appears on the implicit link line.
Extract the latter line.  On failure, abort with a `FATAL_ERROR` so that
the user does not try to build without proper link information.

Once we have the line, parse it with `separate_arguments` using the
`UNIX_COMMAND` option just like `CMakeParseImplicitLinkInfo` already
does.  This robustly parses the command line and removes quoting.
Then extract the first argument as the host link launcher.

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

1371eec4 try_compile: extend CMP0067 to honor language standards for CUDA.

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

1d1f29f4 GetPrerequisites: Fix call to find_program for `ri` tool

Also convert the path to a cmake path

- Unify path handling: Rather than repeat the same logic for each
  individual path create two macros which can be used throughout
  the module.
- Capitalise helpstrings to match the conventions used by the
  standard CMake properties