summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'ctest-no-manual-delete'Brad King2016-09-261-29/+18
|\ | | | | | | | | | | | | b941f3bf CTest::CompressString: Avoid manual delete a5a7771a CTest::CompressString: Reorder code to avoid unnecessary allocation 6ed56457 CTest::Base64EncodeFile: Avoid manual delete
| * CTest::CompressString: Avoid manual deleteDaniel Pfeifer2016-09-231-10/+5
| |
| * CTest::CompressString: Reorder code to avoid unnecessary allocationDaniel Pfeifer2016-09-231-8/+7
| |
| * CTest::Base64EncodeFile: Avoid manual deleteDaniel Pfeifer2016-09-231-12/+7
| |
* | Merge topic 'xcode-swift-version'Brad King2016-09-267-0/+31
|\ \ | | | | | | | | | | | | | | | b35568f3 Xcode: Add option to set Swift language version 49d50ad4 Xcode: Port rudimentary Swift support to Xcode 8
| * | Xcode: Add option to set Swift language versionBrad King2016-09-265-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create a new CMAKE_Swift_LANGUAGE_VERSION variable to specify the SWIFT_VERSION attribute in a generated Xcode project. Ideally this would be a `<LANG>_STANDARD` property but since Swift support is very minimal we should reserve that property for more complete treatment later. Issue: #16326
| * | Xcode: Port rudimentary Swift support to Xcode 8Brad King2016-09-233-0/+9
| |/ | | | | | | | | | | The `.pbxproj` file must now specify a `SWIFT_VERSION` value. Set it to the legacy value of "2.3" for now. Later this can be made configurable (e.g. to "3.0").
* | Merge topic 'FindMatlab-simulink'Brad King2016-09-262-5/+46
|\ \ | | | | | | | | | | | | | | | | | | | | | b36408a0 FindMatlab: Add notes for topic 'FindMatlab-simulink' 7274fd9c FindMatlab: Add EXECUTABLE, MODULE, and SHARED options to matlab_add_mex ccd1341a FindMatlab: Add SIMULINK component aaf4014c FindMatlab: Fix documentation
| * | FindMatlab: Add notes for topic 'FindMatlab-simulink'Brad King2016-09-231-0/+4
| | |
| * | FindMatlab: Add EXECUTABLE, MODULE, and SHARED options to matlab_add_mexJamie Snape2016-09-231-4/+24
| | |
| * | FindMatlab: Add SIMULINK componentJamie Snape2016-09-231-0/+16
| | |
| * | FindMatlab: Fix documentationJamie Snape2016-09-231-1/+2
| |/
* | Merge topic 'fortran-submodule-test'Brad King2016-09-265-0/+95
|\ \ | | | | | | | | | | | | b66bc660 Tests: Add Fortran submodule tests
| * | Tests: Add Fortran submodule testsBrad King2016-09-235-0/+95
| |/ | | | | | | | | Co-Author: Damian Rouson <damian@sourceryinstitute.org> Issue: #16234
* | CMake Nightly Date StampKitware Robot2016-09-261-1/+1
| |
* | CMake Nightly Date StampKitware Robot2016-09-251-1/+1
| |
* | CMake Nightly Date StampKitware Robot2016-09-241-1/+1
|/
* Merge branch 'release'Brad King2016-09-230-0/+0
|\
| * Merge branch 'qtdialog-lib-paths' into releaseBrad King2016-09-231-0/+2
| |\
* | \ Merge topic 'ninja-fortran'Brad King2016-09-2312-10/+910
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 33058150 Help: Document Ninja generator conditional Fortran support 59aae292 Ninja: Add dyndep rules for Fortran module dependencies 39ebfc79 Ninja: Add explicit preprocessing step for Fortran 9a77680e Ninja: Conditionally allow Fortran based on ninja 'dyndep' support 0f331d78 Ninja: Add internal tool to produce a ninja dyndep file for Fortran d3e0b64b Ninja: Add internal tool to scan Fortran code for module dependencies 8eca59a1 Ninja: Add comment with Fortran dependency design documentation a57d1bb7 Ninja: Add API to check for dyndep support 0488ae63 Ninja: Refactor ninja feature detection f0a23aa3 Ninja: Refactor Fortran rejection logic
| * | | Help: Document Ninja generator conditional Fortran supportBrad King2016-09-222-0/+16
| | | | | | | | | | | | | | | | Closes: #14215
| * | | Ninja: Add dyndep rules for Fortran module dependenciesBrad King2016-09-222-1/+174
| | | | | | | | | | | | | | | | | | | | Teach the Ninja generator to add dyndep rules and bindings as described in the design comment in `Source/cmGlobalNinjaGenerator.cxx`.
| * | | Ninja: Add explicit preprocessing step for FortranBrad King2016-09-225-1/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All Fortran sources need to be preprocessed before any source may be compiled so that module dependencies can be (later) extracted. Factor out an explicit preprocessing step preceding compilation. Use Ninja depfile dependencies on the preprocessing step and then compile the already-preprocessed source with a separate build statement that depends explicitly only on the preprocessor output. Later we will insert dynamic discovery of module dependencies between these steps.
| * | | Ninja: Conditionally allow Fortran based on ninja 'dyndep' supportBrad King2016-09-222-4/+40
| | | | | | | | | | | | | | | | | | | | Detect from the version of Ninja whether it supports the dynamically discovered dependencies (dyndep) feature needed to support Fortran.
| * | | Ninja: Add internal tool to produce a ninja dyndep file for FortranBrad King2016-09-223-0/+236
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Create an internal `cmake -E cmake_ninja_dyndep` tool to read the "ddi" files generated by `cmake -E cmake_ninja_depends` from all sources in a target and generate a ninja dyndep file that tells Ninja about Fortran module dependencies within the target and on target dependencies.
| * | | Ninja: Add internal tool to scan Fortran code for module dependenciesBrad King2016-09-222-0/+135
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create an internal `cmake -E cmake_ninja_depends` tool to scan an already-preprocessed Fortran translation unit for modules that it provides or requires. Save the information in a "ddi" file with a CMake-private format for intermediate dynamic dependency information. This file may the be loaded by another tool to be added later.
| * | | Ninja: Add comment with Fortran dependency design documentationBrad King2016-09-221-0/+78
| | | |
| * | | Ninja: Add API to check for dyndep supportBrad King2016-09-222-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Kitware maintains a branch of Ninja with support for dynamically discovered dependencies (dyndep) that has not yet been accepted upstream. Add an internal API to check whether the Ninja version in use for the build supports this feature.
| * | | Ninja: Refactor ninja feature detectionBrad King2016-09-222-6/+18
| | | | | | | | | | | | | | | | | | | | Check for features as soon as we know the ninja version. Save the results so we do not have to re-compare versions every time.
| * | | Ninja: Refactor Fortran rejection logicBrad King2016-09-224-3/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Delay rejection of Fortran until after we've determined the version of the `ninja` tool to be used. This will later allow us to enable Fortran support based on the version of ninja. While at it, make the rejection an immediate fatal error. Also provide a stack trace so readers know what code tried to enable Fortran.
* | | | Merge topic 'CheckFortranSourceCompiles-custom-ext'Brad King2016-09-232-5/+18
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | 4d3874d5 CheckFortranSourceCompiles: Add support for custom source extension 86d2e427 CheckFortranSourceCompiles: Fix FAIL_REGEX documentation typo
| * | | | CheckFortranSourceCompiles: Add support for custom source extensionBrad King2016-09-222-4/+17
| | | | | | | | | | | | | | | | | | | | | | | | | Fortran compilers interpret the source extension to decide whether to preprocess and what language level to use by default.
| * | | | CheckFortranSourceCompiles: Fix FAIL_REGEX documentation typoBrad King2016-09-221-1/+1
| |/ / /
* | | | Merge topic 'test-Fortran-split'Brad King2016-09-2324-89/+96
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | eb8cd356 Tests: Split Fortran module testing into separate FortranModules test a41c8724 Tests: Check if Fortran compiler supports F90 1ec5097d Tests: Use more generic variables in Fortran test d7bd2efb Tests: Remove trailing line from Fortran/External
| * | | | Tests: Split Fortran module testing into separate FortranModules testBrad King2016-09-2223-86/+91
| | | | | | | | | | | | | | | | | | | | | | | | | The main Fortran test is not granular enough. Split some into another test.
| * | | | Tests: Check if Fortran compiler supports F90Brad King2016-09-221-0/+3
| | | | |
| * | | | Tests: Use more generic variables in Fortran testBrad King2016-09-221-10/+10
| | | | |
| * | | | Tests: Remove trailing line from Fortran/ExternalBrad King2016-09-221-1/+0
| |/ / /
* | | | Merge topic 'fix-xcode-attribute-LOCATIONs'Brad King2016-09-234-1/+13
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 764775c4 Fix XCODE_ATTRIBUTE_..._LOCATION target property lookup
| * | | | Fix XCODE_ATTRIBUTE_..._LOCATION target property lookupBrad King2016-09-224-1/+13
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactoring in commit v3.5.0-rc1~272^2~16 (cmGeneratorTarget: Add API for property keys, 2015-10-25) changed the Xcode generator implementation of `XCODE_ATTRIBUTE_...` properties to use the target `GetProperty` method on each `XCODE_ATTRIBUTE_...` property listed by `GetPropertyKeys` instead of looping over the property entries directly. This made the lookup of property names of the form `XCODE_ATTRIBUTE_..._LOCATION` accidentally trigger the computed property logic for the undocumented/legacy `<CONFIG>_LOCATION` property. Of course the computed property value is not the same as the value stored in the `XCODE_ATTRIBUTE_..._LOCATION` property. Fix the computed property logic to avoid triggering on `XCODE_ATTRIBUTE_...` attributes. Closes: #16319
* | | | Merge topic 'cmake-server-signals'Brad King2016-09-237-51/+124
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | e22d30e2 server-mode: Allow for sending signals cc576c2c server-mode: Pass server into cmServerProtocol 277ffa28 server-mode: Move constants for server mode into its own file
| * | | | server-mode: Allow for sending signalsTobias Hunger2016-09-226-0/+33
| | | | | | | | | | | | | | | | | | | | Enable the server to send signals.
| * | | | server-mode: Pass server into cmServerProtocolTobias Hunger2016-09-224-4/+10
| | | | | | | | | | | | | | | | | | | | The information will be needed to send signals.
| * | | | server-mode: Move constants for server mode into its own fileTobias Hunger2016-09-224-47/+81
| |/ / / | | | | | | | | | | | | | | | | This removes some duplication and makes it easier to reuse the vocabulary.
* | | | Merge topic 'FindOpenSSL-path-order'Brad King2016-09-231-6/+6
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 0d8c5ba4 FindOpenSSL: Search in more-specific directories before less-specific
| * | | | FindOpenSSL: Search in more-specific directories before less-specificBrad King2016-09-221-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v3.6.0-rc1~182^2 (FindOpenSSL: Prefer libs early in search path regardless of name, 2016-04-04) we use the `NAMES_PER_DIR` option to `find_library` calls to consider all names in each directory before moving on to the next directory. Fix our library search directory ordering to place more-specific (e.g. VC/) directories before the general directories. Otherwise they may never be considered. Closes: #16320
* | | | | Merge topic 'qtdialog-lib-paths'Brad King2016-09-231-0/+2
|\ \ \ \ \ | | |_|_|/ | |/| | | | | | | | | | | | | 48624b3c cmake-gui: Do not remove library paths for Qt5 plugins.
| * | | | cmake-gui: Do not remove library paths for Qt5 plugins.Clinton Stimpson2016-09-221-0/+2
| | |_|/ | |/| | | | | | | | | | | | | | Not removing library paths is necessary for QFileDialog to function correctly on Linux when using Qt5.
* | | | CMake Nightly Date StampKitware Robot2016-09-231-1/+1
| |_|/ |/| |
* | | Merge topic 'test-fixtures'Brad King2016-09-2228-3/+646
|\ \ \ | | | | | | | | | | | | | | | | 73f47c9e CTest: Add support for test fixtures
generated by cgit v0.12 at 2024-12-27 13:15:46 (GMT)