| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
eb0cfd28 FindXMLRPC: handle QUIETLY and REQUIRED correctly
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !887
|
| |
| |
| |
| |
| |
| |
| | |
Use the built in FindPackageHandleStandardArgs.
Fixes: #16912
Signed-off-by: Niklas Simons <nsimons@abo.fi>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
d3034654 FindCygwin: Use find_program instead of find_path
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !883
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Cygwin's installation directory is mainly needed to use some programs
of it, irrespectively of the target architecture. However, find_path
does not consider cygwin with architecture different than the target
architecture. This is because cygwin's installation path is retrieved
from the registry. WOW64 view is not used by find_path if generating
for 32-bit architecture and vice versa, so cygwin is not found then.
find_program tries both views, this way a 64-bit cygwin may be used
for 32 bit build and vice versa.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
59ffabfe Improve Doxygen support
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !684
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Except Graphviz's `dot` Doxygen may use few other utilities like
`mscgen` (Message Sequence Chart) and `dia` (Diagram Editor).
Now this module allows to manage Doxygen settings from `CMakeLists.txt`
and forget about `Doxyfile`s. Also it provides a helper function
to add a target to generate documentation: `doxygen_add_docs`.
Implement code review notes:
- Introduce `COMPONENTS` to find: `dot`, `mscgen` and `dia`;
- Deprecate variables `DOXYGEN_SKIP_DOT`, `DOXYGEN_EXECUTABLE`,
`DOXYGEN_DOT_EXECUTABLE`, `DOXYGEN_DOT_FOUND` in favour of
`doxygen_add_docs ` usage instead;
- Properly handle paths to found tools in Windows;
- Prevent adding a custom target if Doxygen was not really found;
- Introduce exported (executable) targets for found components.
Co-Author: Craig Scott <craig.scott@crascit.com>
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
ab358d6a Improve find_dependency argument handling
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !872
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove highly specialized and totally positional argument handling in
find_dependency macro, and instead just pass arguments through to
find_package. This gives users access to the full suite of arguments
that find_package knows, and is backward compatible with the old
arguments.
Also, rewrite the unit tests for this, since the old tests are
exclusively focused on testing the old argument handling and are no
longer applicable, and add some success tests (the old tests did not
even set up the CMake state in a way that CMake had any hope of ever
finding the test package).
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
abe8a623 GNUtoMS: Add search path for VS 2017 environment scripts
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !875
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use `cmake_host_system_information` to query the VS Installer tool for
the locations of VS versions since VS 2017 does not provide registry
entries anymore. Add a loop to simplify addition of future versions.
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
68ea936f Added space after IAR response file flag
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !880
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Without the space between the flag and the filename, IAR will fail to
parse the arguments correctly.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4131d1b5 FindImageMagick: Update to work with v7
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !874
|
| |/ / / |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rename our recently added imported targets to match those provided by
the upstream's CMake-based build. That way a project using
`find_package(Protobuf)` can get the same target names no matter how
protobuf is found.
Suggested-by: Konstantin Podsvirov <konstantin@podsvirov.pro>
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
4eb15824 Windows-PGI: Add platform definitions
a94ae96e Windows-PGI: Adapt default compiler flags
c2c2d366 ImplicitLinkInfo: Add support for PGI on Windows
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !794
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
PGI on Windows should use the Visual C++ linker and librarian and not
the ar provided for legacy reasons. The compiler parameters themselves
are the same as their Linux parameters and not compatible to MSVC
however.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
PGI demands -Bdynamic (/MD equivalent) for linking together dynamic
libraries, so we should make it our default mirroring the settings of
e.g. Visual C++ and Intel C++.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since PGI does not write linker directives into objects, the necessary
libraries have to be parsed from commandline. PGI does however link the
Visual C++ runtime libraries, so they have to be filtered out to ensure
no collision with settings of other languages can occur.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
47732280 UseEcos: Fix for separate <DEFINES> and <INCLUDES> placeholders
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !871
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update the module to account for commit v3.4.0-rc1~342^2 (Factor an
<INCLUDES> placeholder out of <FLAGS> in rule variables, 2015-07-13)
and v2.6.0~537 (Create COMPILE_DEFINITIONS property for targets and
source files, 2008-01-14).
Fixes: #16904
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
37627217 Help: Add notes for topic 'FindProtobuf-targets'
e4e1d194 FindProtobuf: add tests
f29635b6 FindProtobuf: add targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !861
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
9e24af01 Use string(APPEND) in Modules
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !864
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Automate with:
find Modules -type f -print0 | xargs -0 perl -i -0pe \
's/set\(([a-zA-Z0-9_\$\{\}]+)(\s+)"\$\{\1\}([^"])/string(APPEND \1\2"\3/g'
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
9e06e97d CPack/Archive: per component filenames support
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !859
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Support for setting archive packager specific
per component filenames and monolithic package
filenames.
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
c02d4d2a GNUtoMS: Add search path for VS 2015 environment scripts
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !854
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
6edd1806 GoogleTest: Expand capabilities of gtest_add_tests()
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !839
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
Now has keyword-based arguments (old syntax form is still supported).
Discovered tests can have a prefix and/or suffix added to the test names
and the list of discovered tests is available to the caller. The working
dir can also be set and the dependency on the source files is now
optional instead of mandatory.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
72ac7ad9 CPackIFW: Internationalization Support
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !748
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes:
- DISPLAY_NAME and DESCRIPTION in CPackIFW module now is MULTI_ARGS;
- Added internationalization support for DisplayName and Description
properties in cmCPackIFWPackage class;
- Added documentation to CPackIFW module;
- Added release note.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
3c515e19 FPHSA: remove extra space
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !843
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Each missing variable is added to the string as " ${var}" which causes
the string to always have a leading space. Remove the duplicate space
due to this in the output.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
75accaae GCC: more patterns for ar/ranlib
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !838
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
a6b39a5a VS: Fix debugging of C++ executables if CSharp is enabled
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !844
|
| | |/
| |/|
| | |
| | | |
Fixes: #16867
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
8b410453 FindOpenSSL: Restore support for crypto-only result
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !846
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit v3.8.0-rc1~132^2 (FindOpenSSL: Check that both CRYPTO and
SSL libraries are present, 2017-01-03) we require both crypto and ssl
libraries to be present. This makes sense because `OPENSSL_LIBRARIES`
lists both and breaks when one is not found. However, prior to that
fix we supported finding only the crypto library and using it through
the imported target. Drop the requirement for ssl to restore support
for using crypto alone.
Later this module should be taught to support the `COMPONENTS` argument
of `find_package`.
Fixes: #16882
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
e8f0385f FindDevIL: Restore IL_FOUND result variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !845
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The fix in commit v3.8.0-rc1~257^2~1 (FindDevIL: fail properly when
library is not found, 2016-11-24) removed the previously-provided
`IL_FOUND` result variable. Set it for compatibility and update the
documentation to mention the new variable.
Fixes: #16881
|
| |\ \ |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This are searched for in the default installed location
C:/local/boost_${ver}
Cherry picked from commit 862482df274121e6f80dca925fb01d996710ed5e
for backport to CMake 3.8.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is to permit VS2017 to make use of the vc141 suffix or
fall back to the compatible vc140 to use Boost libraries built
with VS2015.
Cherry picked from commit 3ca6f70f8b27c08ad3470542705701e6e8e6ea05
plus a fixup from commit 6115875bf0faef61c558e46395e67bdfd4ad48e1
for backport to CMake 3.8.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Boost 1.64 now names the library directory `14.1`, not `15.0`.
|
| |\ \ \ \
| | |/ / /
| |/| | | |
|
| |\ \ \ \ |
|