- 29 Apr, 2016 7 commits
-
-
Brad King authored
Sort include directives within each block (separated by a blank line) in lexicographic order (except to prioritize `sys/types.h` first). First run `clang-format` with the config file: --- SortIncludes: false ... Commit the result temporarily. Then run `clang-format` again with: --- SortIncludes: true IncludeCategories: - Regex: 'sys/types.h' Priority: -1 ... Commit the result temporarily. Start a new branch and cherry-pick the second commit. Manually resolve conflicts to preserve indentation of re-ordered includes. This cleans up the include ordering without changing any other style. Use the following command to run `clang-format`: $ git ls-files -z -- \ '*.c' '*.cc' '*.cpp' '*.cxx' '*.h' '*.hh' '*.hpp' '*.hxx' | egrep -z -v '(Lexer|Parser|ParserHelper)\.' | egrep -z -v '^Source/cm_sha2' | egrep -z -v '^Source/(kwsys|CursesDialog/form)/' | egrep -z -v '^Utilities/(KW|cm).*/' | egrep -z -v '^Tests/Module/GenerateExportHeader' | egrep -z -v '^Tests/RunCMake/CommandLine/cmake_depends/test_UTF-16LE.h' | xargs -0 clang-format -i This selects source files that do not come from a third-party. Inspired-by:
Daniel Pfeifer <daniel@pfeifer-mail.de>
-
Brad King authored
Each source file has a logical first include file. Include it in an isolated block so that tools that sort includes do not move them.
-
Brad King authored
In `detect_nsis_overwrite.cpp` we include windows.h first, and we must preserve that. Place the include in an isolated block so that tools that sort includes do not move it.
-
Brad King authored
These tests use a precompiled header that must be included first. Include the header in an isolated block so that tools that sort includes do not move it.
-
This test generates a header file which is not self-contained. Include it in a separate block of includes so that tools that sort includes do not move it.
-
-
Brad King authored
This file has not been used since commit v2.8.10~218^2~7^2 (Watcom: Simplify compiler version detection, 2012-08-13).
-
- 28 Apr, 2016 12 commits
-
-
21b1fa5c Help: Add notes for topic 'intel-compiler-features' 9addce99 Features: Record standard flags for Intel C/C++ on Windows 15a6c950 WCDH: Add Intel to list of supported compilers 36f32ede Features: Record standards and features for Intel C on UNIX d028b948 Features: Specify minimum version Intel C++ 12.1 be910f00 Features: Record standards and features for Intel C++ on UNIX 7f401ae4 Features: Detect C default dialect on MSVC-like compilers
-
2d7d33ec Help: Hyperlink properties
-
04d74a7f Clang-Tidy: copy stdout to sterr; ignore original stderr
-
Brad King authored
-
Brad King authored
Select the `-std=` or `-Qstd=` flag based on whether Intel is GNU-like or MSVC-like, respectively.
-
-
Record features for Intel C 12.1 and above. Skip this for now on Windows (where Intel C simulates MSVC).
-
Versions below 12.1 do not provide enough information to properly detect if compiling with c++98 or c++0x enabled so remove them from the supported list.
-
Skip this for now on Windows (where Intel C++ simulates MSVC).
-
Brad King authored
These compilers default to C 90 but do not define __STDC__. While MSVC itself has no option to change the dialect, compilers that document compatibility with MSVC and define _MSC_VER may (e.g. Intel).
-
Kitware Robot authored
-
- 27 Apr, 2016 7 commits
-
-
Gregor Jasny authored
-
Brad King authored
Inspired-by:
Ilya Kulakov <kulakov.ilya@gmail.com>
-
Clang-Tidy writes the number of warnings, the number of suppressed warnings, and instructions on how to suppress warnings to stderr. Since each source file is checked individually, this repetitive information is disturbing and should be suppressed. The actual warning messages are written to stdout. Some IDEs (eg. QtCreator) analyze only stderr for issues. Redirecting Clang-Tidy's stdout to stderr makes sure the warnings are correctly displayed.
-
Kitware Robot authored
-
- 26 Apr, 2016 3 commits
-
-
Brad King authored
Solution folders are supported on VS 8 and above in the full versions and on VS 11 and above in the express versions.
-
Brad King authored
-
Kitware Robot authored
-
- 25 Apr, 2016 4 commits
-
-
Green Hills MULTI project files must specify explicitly distinct object file names for source files with the same name.
-
-
To avoid Race conditions with other processes writing to stdout/stderr compose the whole message in a std::stringstream then submit the single complete message.
-
Kitware Robot authored
-
- 24 Apr, 2016 1 commit
-
-
Kitware Robot authored
-
- 23 Apr, 2016 1 commit
-
-
Kitware Robot authored
-
- 22 Apr, 2016 5 commits
-
-
84946c73 Tests: QtAutogen: Same source name in different directories test 9c6fa684 Autogen: Generate qrc_NAME.cpp files in subdirectories 488ea8c7 Autogen: Generate not included moc files in subdirectories (#12873) 66caae45 Autogen: Check added for name collisions of generated qrc_NAME.cpp files 663d093d Autogen: Check added for name collisions of generated ui_NAME.h files 8295d437 Autogen: Check added for name collisions of generated moc files d350308a Help: Improve AUTOMOC documentation layout
-
2263949b cmGlobalXCodeGenerator: do not pass char* to cmSystemTools::CollapseFullPath() 2b25ce30 make cmGlobalXCodeGenerator::XCodeEscapePath() take a std::string& ffedf352 make cmGlobalXCodeGenerator::BuildObjectListOrString::Add() take a string& 6100bdff cmGlobalXCodeGenerator: directly call CreateString() with std::string
-
068358e1 cmMakefile::AddCacheDefinition: avoid conversions between char* and string
-
The test features multiple .cpp and .qrc files with the same name in different subdirectories. This requires AUTOMOC and AUTORCC to generate files with names that respect the path information of the source files.