- 07 Feb, 2014 1 commit
-
-
Kitware Robot authored
-
- 06 Feb, 2014 16 commits
-
-
cc46b702 Help: Adjust the QtAutogen properties to the common style. f371545d Help: Use ``True`` and ``False`` for IMPORTED values. 3879c847 Help: Document relation of properties to the rest of the buildsystem. ba4c2fa8 Help: Mark up the buildsystem commands documentation a683262a Help: Note that the compatible interface properties must not intersect. fbe01bed Help: Specify how to order and modify transitively set property values. 645500b4 Help: Add hyperlink targets to some manual sections. 85a4fad7 Help: Use ``inline-literals`` to mark generator expressions. a0fa0253 Help: Mark up references to NEW and OLD policy settings properly. 6c02e7f4 Help: Add a style guide. 91fbff88 Help: Fix typos
-
Link to the cmake-qt manual.
-
Only the first letter is capitalized. It is marked up.
-
-
Cross-link to the cmake-buildsystem manual.
-
-
-
These can be refered to from the command documentation and other relevant locations.
-
-
-
-
Psuedo -> Pseudo behaviour -> behavior CMake uses American spelling.
-
0f5dfd10 Help: Specify that qtmain.lib is only used for WIN32 executables.
-
8f8edeb0 QtAutogen: Only add source files to the target if AUTORCC is ON.
-
Kitware Robot authored
-
- 05 Feb, 2014 10 commits
-
-
Stephen Kelly authored
-
52e7beb6 Help: Expand documentation of CMAKE_VERSION and related variables
-
101057b5 Drop tweak version component from CMake Policies
-
635e96dd Help: Be clearer about which header files are considered for AUTOMOC
-
a6971f65 FeatureSummary: Don't list transitive package dependencies
-
Brad King authored
Describe the meaning of each version component in more detail in the documentation of CMAKE_VERSION. Simplify the per-component version variable documentation by referencing the main variable. Include information about how to compare version strings. Also add an historical note about the version scheme used prior to commit v2.8.2~105^2~4 (New version scheme to support branchy workflow, 2010-04-23).
-
Stephen Kelly authored
The qtx_add_resources() macro adds the resource file to the output list to maintain file-level dependencies. Having the qrc file in a target sources is a precondition for AUTORCC to function. When processing the source files of a target, only add the generated qrc_<file>.cpp to the target sources if AUTORCC is ON. This avoids pre-porting conflict with the macro. Reported-by: Micha Hergarden
-
Kitware Robot authored
- 04 Feb, 2014 9 commits
-
-
Brad King authored
Since commit v2.8.2~105^2~2 (Teach CMake Policies about tweak version component, 2010-04-23), cmPolicies has known how to handle a policy introduced in a tweak version. This was done back when we introduced policies with the current development date version and later updated it to the release version. Now we always introduce policies using the next expected release version and explicitly set the policy to test the NEW behavior. CMake Policies (or any other features) should never be introduced in a tweak (bugfix) release, so drop the infrastructure that allows this.
-
028a5285 OS X: Make sure RPATHs are unique to avoid possible corruption.
-
Modify the includedUis to store the path to the file which includes the ui file. Reuse that path to generate the output file from the uic process.
-
Brad King authored
Add a release/dev.txt file and include it from release/index.rst in development versions. Add a "Changes Since Release" section with a toctree that globs adjacent "dev/*" documents. Add a sample topic document explaining how topic-specific release note documents work. This approach will allow developers to write release notes for their changes as they are made. The release manager may then consolidate and organize the notes for a specific release version.
-
Brad King authored
Add a release/index.rst document titled "CMake Release Notes" to hold the toctree for release notes. Add a "Release Notes" section to the top-level html document index to link to the new document.
-
Brad King authored
Add SPHINX_TEXT to enable the Sphinx 'text' builder. Mark it as advanced and do not add install rules. This is intended for use by the release manager to build the release notes in text format suitable for email.
-
The old documentation stated that "all header files" were considered, which was not true for any sensible definition of "all header files". Only header files with certain names are considered. Document the filename patterns matched for parsing.
-
Kitware Robot authored
-
- 03 Feb, 2014 4 commits
-
-
Stephen Kelly authored
Set a global property in the find_package implementation. Track and reset that property in the find_dependency macro. Read the property in FeatureSummary when determining whether to print output. This means that packages which are found only as dependencies are not listed by FeatureSummary, but if a project uses find_package elsewhere directly, then it will be listed by FeatureSummary. Suggested-by: Alex Merry http://thread.gmane.org/gmane.comp.kde.devel.frameworks/10640
-
395881f7 README: Credit Kitware and community of contributors
-
dcd443d4 cmTarget: Clean up the InsertCompileDefinition implementation.
-