Inside `git filter-branch --tree-filter` we must format all tracked
files because formatting of the tree for each commit is independent
from earlier commits.

Now that our one-shot clang-format run is complete we rarely need to
filter the entire tree anymore.  Filter nothing if no options are given
and just print the usage message.  Offer options to specify selection of
some set of files from Git as needed for various workflows.

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

d9fd2f54 Revise C++ coding style using clang-format
82df6dea Empty commit at end of history preceding clang-format style transition
6a13f43f CONTRIBUTING: Add a section on coding style
bf451d9f Add a script to run clang-format on the entire source tree
1e90d78f Configure clang-format for CMake source tree
da60adc3 Tell Git to use a distinct conflict marker size in `.rst` files

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

c7006d2e cmGeneratorTarget: Protect macro code layout from clang-format

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

Run the `Utilities/Scripts/clang-format.bash` script to update
all our C++ code to a new style defined by `.clang-format`.
Use `clang-format` version 3.8.

* If you reached this commit for a line in `git blame`, re-run the blame
  operation starting at the parent of this commit to see older history
  for the content.

* See the parent commit for instructions to rebase a change across this
  style transition commit.

This is an empty commit that precedes an automatic application of
clang-format to update the C++ style of our entire source tree.
This may be helpful to rebase a topic branch that was originally
based on a commit preceding the transition.  One may first rebase
the topic on this commit.  Then use one of the following approaches.

*   Rewrite the topic, including this commit, using `git filter-branch`
    `--tree-filter` with `Utilities/Scripts/clang-format.bash` to update
    the style in every commit.  Rebase the revised topic, excluding the
    rewrite of this commit, on the style transition commit.

OR

*   Add a `.git/info/grafts` entry to change the parent of the first
    commit in the topic from this commit to the style transition commit.
    Rewrite the topic using `git filter-branch --tree-filter` with
    `Utilities/Scripts/clang-format.bash` to update the style in every
    commit.  Then remove the graft, which was resolved by the filter.

See `git help filter-branch` and `git help repository-layout` for
details.

Document that we now define our coding style with `clang-format`.

List all sources in version control and filter out those that we should
not format for various reasons.  Then run the clang-format tool to do an
in-place update.

After discussion among developers we settled on the Mozilla style
with a few tweaks:

* Do not align operator arguments.

* Do not always break after a function return type.

* Limit to 79 columns instead of 80 to fit edge cases
  better in 80-column terminals as CMake has always done.

* Format for C++98 instead of C++11 because CMake is written
  in the former language.

Co-Author: Daniel Pfeifer <daniel@pfeifer-mail.de>

Use a long conflict marker size that is unlikely to be in conflict
with a `=======` section header underline.

The `IMPLEMENT_VISIT_IMPL` macro must preserve a space before the `>`
character in case the `DATATYPE` is a template type ending in `>`.
Manually format the macro layout as clang-format would except for this
space.  Then add markup to tell clang-format not to format this macro.

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

c2e8d515 FindBoost: Add checks for component-specific headers

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

328eff90 FindBoost: Update dependencies for Boost 1.61

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

df97b979 FindPkgConfig: optionally create imported target for the found libraries

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

f5089cfc CPack/RPM adding dist to release tag test
f7003a60 CPack/RPM release dist tag support

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

44ee2d71 CPack/RPM different package names

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

4461e8bb CPack/Deb cpack-deb-improvements release notes
7e940bf7 CPack/Deb test changes due to breaking changes
3b648894 CPack/Deb package release number in file name
316dd613 CPack/Deb proper package file naming
271e03f0 CPack/Deb per-component package architecture
23baaf8d CPack/Deb inter package dependencies
3a55a0e7 CPack/Deb proper component packages file naming
c7f388e7 CPack/Deb generation of postinst and postrm ldconfig files
2d589653 CPack/Deb generation of DEBIAN/shlibs control file

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

9cb263d7 cmComputeLinkInformation: Do not mark interface library as a path

Roger Leigh authored 8 years ago and Brad King committed 8 years ago

This supplements the existing library checks, to
cater for the possibility that the libraries are
present but the headers are not.  This can happen
when the Boost collections is split up into
multiple packages and not all are installed,
and will avoid the checks silently passing when
the build would subsequently fail.

Packagers may now set their own rpm package
file names or request that rpmbuild tool
chooses one for them. It also supports handing
of situations where one spec file may produce
multiple rpm packages.

Tests and release notes

Harry Mallon authored 8 years ago and Domen Vrankar committed 8 years ago

Some Linux distros require Release tag
to be set to <ReleaseVersion><Dist>.

The empty string we add as a link item for an INTERFACE_LIBRARY target
is not a path, so do not mark it as such.  The generators currently
tolerate it either way, but only by accident.

Domen Vrankar authored 8 years ago and Brad King committed 8 years ago

New CPack/Deb tests and changes to old tests
as package file names and inter component dependency
detection was changed.

Domen Vrankar authored 8 years ago and Brad King committed 8 years ago

Debian packages file naming format must contain
revision number - package release number
(breaks compatibility with previous versions)

Domen Vrankar authored 8 years ago and Brad King committed 8 years ago

Proper Debian packages file naming for single package
setup (breaks compatibility with previous versions)

Alexander Smorkalov authored 8 years ago and Brad King committed 8 years ago

Allowed to set per-compoment Debian package architecture.
Useful, if you distribute documentation (should have
"all architecture").

Alexander Smorkalov authored 8 years ago and Brad King committed 8 years ago

In multi-component setup dependencies
between packages are set (breaking change)

Alexander Smorkalov authored 8 years ago and Brad King committed 8 years ago

Proper Debian packages file naming for multi-component setup
(breaks compatibility with previous versions)

Alexander Smorkalov authored 8 years ago and Brad King committed 8 years ago

DEBIAN/postinst and DEBAIN/postrm files generation if
the package installs libraries in ldconfig controlled
location (/lib/, /usr/lib/)

Alexander Smorkalov authored 8 years ago and Brad King committed 8 years ago

DEBIAN/shlibs control file generation if the package
contains libraries

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

fdfb0c06 HDF5: Rework component searching to correctly find HL for all bindings

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

6b0b0660 InstallRequiredSystemLibraries: Optionally install Windows UCRT (#16073)
bbf8c03b InstallRequiredSystemLibraries: Fix ENV{ProgramFiles(x86)} reference