summaryrefslogtreecommitdiffstats
path: root/Source/cmExtraSublimeTextGenerator.cxx
Commit message (Collapse)AuthorAgeFilesLines
* LocalGenerator: Add a string overload for AppendFlagsBen Boeckel2014-05-071-1/+1
|
* cmTarget: Make the source files depend on the config.Stephen Kelly2014-04-021-1/+2
| | | | | | | | | | | | | | | | | Disallow the use of config-specific source files with the Visual Studio and Xcode generators. They don't have any way to represent the condition currently. Use the same common-config API in cmQtAutoGenerators. While it accepts config-specific files, it doesn't have to support multiple configurations yet. Loop over the configs in cmTargetTraceDependencies and cmGlobalGenerator::WriteSummary and consume all source files. Loop over the configs in cmComputeTargetDepends and compute the object library dependencies for each config.
* Remove some c_str() calls.Stephen Kelly2014-03-111-5/+5
| | | | | | Use the clang RemoveCStrCalls tool to automatically migrate the code. This was only run on linux, so does not have any positive or negative effect on other platforms.
* stringapi: Use strings for generator namesBen Boeckel2014-03-081-5/+6
|
* stringapi: Pass configuration names as stringsBen Boeckel2014-03-081-2/+2
|
* strings: Remove cmStdString referencesBen Boeckel2014-03-081-1/+1
| | | | | | | | | | | Casts from std::string -> cmStdString were high on the list of things taking up time. Avoid such implicit casts across function calls by just using std::string everywhere. The comment that the symbol name is too long is no longer relevant since modern debuggers alias the templates anyways and the size is a non-issue since the underlying methods are generated since it's inherited.
* stringapi: Use strings in target nameBen Boeckel2014-03-081-2/+3
|
* stringapi: Use strings for the languagesBen Boeckel2014-03-081-7/+3
|
* Sublime: Pass language and config properlyBen Boeckel2014-02-111-1/+1
|
* cmTarget: Make GetSourceFiles populate an out-vector parameter.Stephen Kelly2014-01-091-1/+2
| | | | | In a future patch, this will also be populated with extra sources from the linked dependencies.
* Refactor tool selection for edit_cache (#14544)Brad King2013-11-121-20/+0
| | | | | | | | | Refactor edit_cache tool selection to ask each global generator for its preference. Teach the Ninja generator to always use cmake-gui because Ninja by design cannot run interactive terminal dialogs like ccmake. Teach the Makefile generator to use cmake-gui when also using an "extra" generator whose IDE has no terminal to run ccmake, and otherwise fall back to CMAKE_EDIT_COMMAND selection for normal Makefile build systems.
* Drop the 'Full' field from cmDocumentationEntryBrad King2013-10-161-7/+0
| | | | | We need only 'Brief' for usage documentation. We no longer have builtin 'Full' documentation, which is now in Help/*/*.rst files.
* Merge topic 'tid-system-argument'Brad King2013-07-161-1/+1
|\ | | | | | | | | | | | | | | | | | | 9cf3547 Add the INTERFACE_SYSTEM_INCLUDE_DIRECTORIES target property. 1925cff Add a SYSTEM parameter to target_include_directories (#14180) 286f227 Extend the cmTargetPropCommandBase interface property handling. 83498d4 Store system include directories in the cmTarget. f1fcbe3 Add Target API to determine if an include is a system include. 2679a34 Remove unused variable.
| * Add Target API to determine if an include is a system include.Stephen Kelly2013-07-021-1/+1
| | | | | | | | | | The implementation can be modified later so that system includes can be determined on a per-target basis.
* | Refactor cmTarget::GetCompileDefinitions to use an out-vector, not a string.Stephen Kelly2013-07-111-1/+1
|/ | | | Refactor to create AddCompileDefinitions.
* Refactor target COMPILE_OPTIONS and COMPILE_FLAGS handlingBrad King2013-06-271-28/+1
| | | | | | | | | | | | Replace the cmLocalGenerator GetCompileOptions method with an AddCompileOptions method since all call sites of the former simply append the result to a flags string anyway. Add a "lang" argument to AddCompileOptions and move the CMAKE_<LANG>_FLAGS_REGEX filter into it. Move the call sites in each generator to a location that has both the language and configuration available. In the Makefile generator this also moves the flags from build.make to flags.make where they belong.
* Add cmLocalGenerator::GetCompileOptions.Stephen Kelly2013-06-021-3/+5
| | | | | | Currently it only adds the contents of the COMPILE_FLAGS target property, but it can be extended to handle a new COMPILE_OPTIONS generator expression enabled property.
* Sublime: Honor source-level COMPILE_FLAGS propertyStephen Kelly2013-05-211-1/+1
| | | | Make the code match the comment.
* Fix the evaluation of per-config COMPILE_DEFINITIONS (#14037)Stephen Kelly2013-03-251-2/+1
| | | | | | | | | | | | | | The API for retrieving per-config COMPILE_DEFINITIONS has long existed because of the COMPILE_DEFINITIONS_<CONFIG> style properties. Ensure that the provided configuration being generated is also used to evaluate the generator expressions in cmTarget::GetCompileDefinitions. Both the generic COMPILE_DEFINITIONS and the config-specific variant need to be evaluated with the requested configuration. This has the side-effect that the COMPILE_DEFINITIONS does not need to be additionally evaluated with no configuration, so the callers can be cleaned up a bit too.
* Update generator to use new cmGeneratorTarget api.Robert Maynard2013-02-191-11/+14
|
* Remove ability to generate sublime clang files.Robert Maynard2013-02-191-98/+4
| | | | | | | | | | | | | | | 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.
* Correct missing parameter to CMP0018Flags call.Robert Maynard2013-02-191-1/+1
|
* SublimeText 2 Gen: Set the sublimeclang_options_script property.Morné Chamberlain2012-11-241-1/+28
| | | | | | | 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-152/+245
| | | | | | 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: Fixed the issue where include directory flags used -DMorné Chamberlain2012-11-071-1/+1
|
* SublimeText2 Gen: Improved use of define, include flags from CMAKE_C(XX)_FLAGSMorné Chamberlain2012-11-041-16/+20
| | | | | | | | 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-17/+40
| | | | | | | | 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.
* Fixed Sublime Text project generation for in-source buildsMorné Chamberlain2012-10-141-14/+26
| | | | | Fixed the issue where for in-source builds the source directory (which is also the build directory) was excluded from the project file.
* Added a CMAKE_SUBLIMECLANG_DISABLED variable that disables SublimeClang.Morné Chamberlain2012-10-141-1/+13
| | | | | | If the CMAKE_SUBLIMECLANG_DISABLED variable is on then SublimeClang is disabled in the generated project file. This is useful in large projects where SublimeClang might run slowly or perform poorly.
* The generator no longer generates absolute paths to the ninja.build/Makefiles.Morné Chamberlain2012-10-141-5/+4
|
* The generator no longer generates an explicit list of source files.Morné Chamberlain2012-10-141-139/+9
| | | | | 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-3/+0
|
* Fixed support for the Ninja build system.Morné Chamberlain2012-10-131-10/+31
|
* Cleaned up the Sublime Text 2 Generator code a bit.Morné Chamberlain2012-10-131-85/+114
|
* Changed SublimeClang include path generation to expand to absolute paths.Morné Chamberlain2012-10-131-3/+14
| | | | | Fixed an issue where compiler definitions for SublimeClang were not written to the project file.
* Added some support for sublimeclang_options in the generated project file.Morné Chamberlain2012-10-131-7/+114
| | | | | | | | | 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/+390
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-12-28 19:51:15 (GMT)