summaryrefslogtreecommitdiffstats
path: root/Source/cmExtraSublimeTextGenerator.h
Commit message (Collapse)AuthorAgeFilesLines
* Use C++11 override instead of CM_OVERRIDEBrad King2017-09-151-1/+1
| | | | | | | | We now require C++11 support including `override`. Drop use of the old compatibility macro. Convert references as follows: git grep -l CM_OVERRIDE -- '*.h' '*.hxx' '*.cxx' | xargs sed -i 's/CM_OVERRIDE/override/g'
* clang-format: format all code as Cpp11Daniel Pfeifer2017-08-301-1/+1
|
* IWYU: Mark cmConfigure.h with pragma: keepDaniel Pfeifer2017-08-261-1/+1
| | | | Also remove `#include "cmConfigure.h"` from most source files.
* Use quotes for non-system includesDaniel Pfeifer2017-04-111-1/+1
| | | | | | | | | | | | | Automate with: git grep -l '#include <cm_' -- Source \ | xargs sed -i 's/#include <\(cm_.*\)>/#include "\1"/g' git grep -l '#include <cmsys/' -- Source \ | xargs sed -i 's/#include <\(cmsys\/.*\)>/#include "\1"/g' git grep -l '#include <cm[A-Z]' -- Source \ | xargs sed -i 's/#include <\(cm[A-Z].*\)>/#include "\1"/g'
* Sublime: Add option to specify env vars for the .sublime-projectBruno Pedrosa2016-10-271-0/+1
| | | | | | | Create a `CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS` variable to control addition of env vars in the `.sublime-project`. Closes: #16387
* Sublime: Exclude build tree from source tree project only optionallyBruno Pedrosa2016-10-121-0/+2
| | | | | | | | Create a `CMAKE_SUBLIME_TEXT_2_EXCLUDE_BUILD_TREE` variable to control addition of the build tree to `folder_exclude_patterns` in the `.sublime-project`. Change the default of this behavior to OFF. Closes: #16351
* Simplify CMake per-source license noticesBrad King2016-09-271-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Per-source copyright/license notice headers that spell out copyright holder names and years are hard to maintain and often out-of-date or plain wrong. Precise contributor information is already maintained automatically by the version control tool. Ultimately it is the receiver of a file who is responsible for determining its licensing status, and per-source notices are merely a convenience. Therefore it is simpler and more accurate for each source to have a generic notice of the license name and references to more detailed information on copyright holders and full license terms. Our `Copyright.txt` file now contains a list of Contributors whose names appeared source-level copyright notices. It also references version control history for more precise information. Therefore we no longer need to spell out the list of Contributors in each source file notice. Replace CMake per-source copyright/license notice headers with a short description of the license and links to `Copyright.txt` and online information available from "https://cmake.org/licensing". The online URL also handles cases of modules being copied out of our source into other projects, so we can drop our notices about replacing links with full license text. Run the `Utilities/Scripts/filter-notices.bash` script to perform the majority of the replacements mechanically. Manually fix up shebang lines and trailing newlines in a few files. Manually update the notices in a few files that the script does not handle.
* fix a load of include-what-you-use violationsDaniel Pfeifer2016-09-031-3/+9
|
* Refactor extra generator registration to use factoriesTobias Hunger2016-08-031-13/+1
| | | | | | | | | | | This will allow additional information about the availability and capabilities of extra generators to be queried without actually creating them. Instead of a static NewFactory() method like the main generator factories have, use a static GetFactory() method to get a pointer to a statically allocated extra generator factory. This simplifies memory management.
* mark functions with CM_OVERRIDEDaniel Pfeifer2016-06-271-4/+4
|
* Revise C++ coding style using clang-formatKitware Robot2016-05-161-19/+17
| | | | | | | | | | | | | 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.
* Sublime: Port API to cmGeneratorTarget.Stephen Kelly2015-10-241-2/+1
|
* Sublime: Port some API to cmGeneratorTarget.Stephen Kelly2015-10-121-2/+1
|
* stringapi: Use strings for generator namesBen Boeckel2014-03-081-3/+3
|
* stringapi: Use strings in target nameBen Boeckel2014-03-081-2/+2
|
* Remove ability to generate sublime clang files.Robert Maynard2013-02-191-3/+1
| | | | | | | | | | | | | | | SublimeClang is a optional plugin to SublimeText and I felt it shouldn't be part of the generator for the following reasons: 1. Reduces the amount of sublime and sublimeClang specific code we have to maintain inside CMake. 2. In testing the SublimeClang commands generated did not work for the VTK project. For people that do want this feature I recommend that they looking into https://gist.github.com/robertmaynard/4724705 for a way to use CMAKE_EXPORT_COMPILE_COMMANDS to generate JSON files that can be used by SublimeClang.
* SublimeText 2 Gen: Set the sublimeclang_options_script property.Morné Chamberlain2012-11-241-0/+1
| | | | | | | The sublimeclang_options_script property is now set in the project file. It is set to execute a python script that reads the JSON options file to get options per source file. Python must be installed and in the path for this feature to work from Sublime Text.
* Sublime Text 2 Gen: Per-source Compile flags are now saved in a separate file.Morné Chamberlain2012-11-111-8/+18
| | | | | | We no longer write sublimeclang_options to the project file, but instead write a separate .sublimeclang-options JSON file that contains a map of source file paths to compile flags for that file.
* SublimeText2 Gen: Improved use of define, include flags from CMAKE_C(XX)_FLAGSMorné Chamberlain2012-11-041-3/+6
| | | | | | | | Both define and include flags from CMAKE_C(XX)_FLAGS are now included in SublimeClang options. Include directories are now used with absolute paths instead of relative paths since CMake generated build trees cannot be moved anyway.
* Define flags in CMAKE_C(XX)_FLAGS are now included in SublimeClang settings.Morné Chamberlain2012-10-181-2/+4
| | | | | | | | Changed the the SublimeText2 generator name to Sublime Text 2. Fixed a minor issue where if the build directory was outside of the source directory an unnecessary folder_exclude_pattern was generated in the Sublime Text 2 project file.
* The generator no longer generates an explicit list of source files.Morné Chamberlain2012-10-141-15/+0
| | | | | Now the source directory is simply added to the project file, with the output/build directory excluded.
* Added and cleaned up some comments.Morné Chamberlain2012-10-131-0/+13
|
* Cleaned up the Sublime Text 2 Generator code a bit.Morné Chamberlain2012-10-131-1/+16
|
* Added some support for sublimeclang_options in the generated project file.Morné Chamberlain2012-10-131-1/+2
| | | | | | | | | This adds -I include path flags and -D define flags for sublimeclang. The current problem with this is that these flags cannot be set per target (build_system in sublime text), it can only be set project wide. Currently all of the include paths and compiler definitions from ALL of the targets are used (with duplicates removed). This could be problematic in some cases (conflicting compiler definitions among targets).
* Added a generator for Sublime Text 2 project files.Morné Chamberlain2012-10-131-0/+61
The generator adds all list and source files for each defined project. The generated project files also include build_system entries that run the platform-specific make on the generated Makefiles. A build_system entry is created for each target that was defined in the CMakeLists.txt files. At the moment this has only been tested with C/C++ projects.
generated by cgit v0.12 at 2024-09-03 02:49:24 (GMT)