| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Remove this content from the `cmake-developer(7)` manual because it
is relevant only to developers working on CMake itself. Move it to
a guide in the developer documentation.
|
| |
|
|
|
|
|
|
| |
We no longer add granular compile features. Only language standard
meta features like `cxx_std_##`` need to be added, and these can
be done by following existing patterns.
|
| |
|
| |
|
|
|
|
| |
Fixes: #16142
|
|
|
|
| |
Found via `codespell`
|
|
|
|
|
|
| |
Move the C++ subset rules from the `cmake-developer(7)` into our
dedicated coding guide since they do not need to be in user-facing
documentation.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Issue: #16616
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace use of cmsys::auto_ptr with a CM_AUTO_PTR macro that maps to
our own implementation adopted from the KWSys auto_ptr implementation.
Later we may be able to map CM_AUTO_PTR to std::auto_ptr on compilers
that do not warn about it.
Automate the client site conversions:
git grep -l auto_ptr -- Source/ | grep -v Source/kwsys/ | xargs sed -i \
's|cmsys::auto_ptr|CM_AUTO_PTR|;s|cmsys/auto_ptr.hxx|cm_auto_ptr.hxx|'
|
|
|
|
| |
Fix spelling mistake `sytem` => `system`.
|
|
|
|
|
|
| |
Use the __cplusplus and __STDC_VERSION__ macros to automatically
determine the default dialect for the compiler while determining its
id and version.
|
|
|
|
|
| |
Drop the comment on the purpose of PATH_SUFFIXES in our Find Module
example. It was incorrect.
|
| |
|
|
|
|
|
|
| |
Pre-C++98 compilers required that the template argument be
used in the function parameters. Those compilers are no longer
supported as hosts, so drop the workaround.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Define an empty string in CMAKE_<LANG>_STANDARD_DEFAULT to mean that
the toolchain has no notion of lanuage standard levels. In this case
the <LANG>_STANDARD[_REQUIRED] properties will have no effect.
Update the RunCMake.CompileFeatures test to exclude the
LinkImplementationFeatureCycle test when there is no standard default.
It can never fail because no use of specific features will adjust the
CXX_STANDARD level required for any target since the standard levels
have no meaning in this case.
|
| |
|
|
|
|
| |
The necessary conversion is supported by all CMake host compilers.
|
| |
|
|
|
|
|
|
|
|
|
| |
The use of FeatureSummary inside a find module is not a convention
yet used by upstream CMake modules. Drop the example from the
documentation about how to write find modules. If in the future
we add use of FeatureSummary to many of the upstream find modules
then this example can be restored as part of establishing the
convention.
|
| |
|
| |
|
|
|
|
|
| |
If this file is being executed, the user has the CMake version
providing it.
|
| |
|
|
|
|
|
|
|
| |
An IMPORTED target in either type of package can equally depend on
an IMPORTED target in a Find module, which must be found as a
dependency, which is presumably the problem being implied. This is
not a distinction of creating an IMPORTED target in a Find module.
|
| |
|
|
|
|
|
| |
The compilers introducing these limitations are no longer supported
as host compilers.
|
| |
|
| |
|
|
|
|
| |
A latex document can have its own TOC.
|
|
|
|
|
|
| |
Update the wording of some examples to avoid long lines in code blocks.
Otherwise the formatted documentation can exceed certain column width
limitations.
|
| |
|
|
|
|
|
| |
In order to be able to link to specific command signatures we need to
use a section header instead of a horizontal separator.
|
|
|
|
|
|
| |
Explicitly specify the sequence of underline characters we use in the
CMake documentation. It is the same sequence as that suggested in the
Sphinx documentation, but we have our own descriptions.
|
|
|
|
|
| |
Now that the style guidelines have section titles instead of numbers,
organize them into more well-defined sections.
|
|
|
|
| |
Give the style guides titles instead of numbers so we can link to them.
|
|
|
|
|
|
| |
This is the convention suggested in the Sphinx documentation and is
already used in several other places in the CMake documentation.
Update a few places where we were using other characters.
|
|\
| |
| |
| |
| |
| | |
d0b1d2a6 CPackWiX: Implement CPACK_NEVER_OVERWRITE and CPACK_PERMANENT properties
15a8af21 Add an "installed file" property scope
|
| |
| |
| |
| |
| |
| |
| | |
Teach set_property and get_property an "INSTALL" property type to be
associated with install-tree file paths. Make the properties available
to CPack for use during packaging. Add a "prop_inst" Sphinx domain
object type for documentation of such properties.
|
|/
|
|
|
|
|
|
| |
Link to it from the documentation of related properties, variables
and commands.
Extend the cmake-developer(7) documentation with notes on
extending feature support for compilers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As well as the traditional variables, providing imported targets is
suggested, and the relative advantages and disadvantages briefly
discussed.
A mini-tutorial walking through creating a simple find module is
provided.
This changes the recommended version variable from Foo_VERSION_STRING to
Foo_VERSION, because there is really no need to have different variable
names for package version files vs. find modules. It notes the old
variable name, though, and suggests setting it for compatibility.
|
|
|
|
| |
The type no longer exists within CMake.
|
|
|
|
| |
binary_find -> binary_search.
|
| |
|
|
|
|
|
|
|
|
| |
Psuedo -> Pseudo
behaviour -> behavior
CMake uses American spelling.
|
|
|
|
|
| |
As found in commit 519c0a5d (Can't use std::string::clear() in
cmake., 2012-09-15).
|
|
|
|
|
| |
As found in commit 8e7c207e (Use a manual loop to insert into
set::set., 2012-09-15).
|