| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Apple's main Operating system changed their name from OS X to macOS:
https://www.engadget.com/2016/06/13/os-x-is-now-macos/
Revise documentation accordingly.
|
|\
| |
| |
| |
| |
| |
| | |
e15adbfed3 Help: Specify COMPILE_OPTIONS and COMPILE_FLAGS source properties usage
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2043
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
Add the support of per-source property COMPILE_OPTIONS,
including generator expressions support.
Related: #17507
|
|\
| |
| |
| |
| |
| |
| | |
118815f0 COMPILE_FLAGS: do not imply that the property is a list
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1640
|
| |
| |
| |
| |
| |
| | |
The "added to the list" language hinted that the property was
interpreted as a CMake list, but this is not correct. It is just a
string.
|
|/ |
|
|
|
|
|
|
| |
This allows users to specify different genex-based compile definitions for each file in a target.
Fixes: #17508
|
|
|
|
|
|
|
|
| |
Add `VS_SHADER_DISABLE_OPTIMIZATIONS` and `VS_SHADER_ENABLE_DEBUG`
source file properties to control these settings on `.hlsl` files in the
VS generator.
Fixes: #17406
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
49dab3eb VS: Add VS_SHADER_OUTPUT_HEADER_FILE and VS_SHADER_VARIABLE_NAME properties.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1319
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The VS_SHADER_OUTPUT_HEADER_FILE property is the name of the generated
header file containing the object code of the shader.
The VS_SHADER_VARIABLE_NAME property is the name of the variable
containing the object code in the above header file.
Signed-off-by: Kevin M. Godby <kevin@godby.org>
|
|/ |
|
|
|
|
| |
Describe how to get sources into IDE project files.
|
|
|
|
| |
Issue: #16680
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mainly <Link> and <DependentUpon> tags are added to connect generated
and manually edited files. Special file extensions that are take care
of are:
- .Designer.cs
- .xaml.cs
- .settings
- .resx
- .xaml
|
| |
|
|
|
|
|
|
| |
This allows users to specify different genex-based compile flags for
each file in a target, e.g. compiling just a single file with `Od/Ox` in
release builds on Visual Studio.
|
|
|
|
|
|
|
|
| |
This property allow to specify a specific Visual Studio tool for a
source file overriding the default tool behavior. For example, a
`.resw` file being processed as a `PriResource` file. This has the
advantage of being able to teach CMake to process new file types without
code modifications.
|
|
|
|
| |
This adds values to the ATTRIBUTES list in PBXBuildFile settings.
|
| |
|
|
|
|
|
|
| |
This generator has been deprecated since CMake 3.3. Remove it.
Update documentation, modules, and tests to drop content specific
to this generator.
|
|
|
|
| |
Many of our interfaces documented for OS X also work for iOS.
|
| |
|
|
|
|
|
|
|
|
| |
XAML files are by default of type Page in the vcxproj and can be
overriden by setting the VS_XAML_TYPE property. The .cpp and .h file
of the same name are automatically added as depending on the XAML file.
New VSXaml test builds a basic XAML WindowsStore 8.1 app with VS2013.
|
|
|
|
|
| |
Create a VS_SHADER_FLAGS source file property so that we can set all
other Visual Studio .hlsl shader file compilation flags.
|
|
|
|
|
|
|
|
|
|
| |
Add a VS_DEPLOYMENT_LOCATION source file property to specify where to
put files that are part of the package. For example:
set_property(SOURCE ${ASSET_FILES} PROPERTY VS_DEPLOYMENT_LOCATION "assets")
Without this, sources marked with VS_DEPLOYMENT_CONTENT cannot be
located properly.
|
|
|
|
|
|
| |
Create properties VS_SHADER_ENTRYPOINT and VS_SHADER_MODEL. Without
these many .hlsl source files may not be possible to use. Extend the
VSWinStorePhone test project to cover them.
|
|
|
|
|
| |
Enable the Sphinx 'nitpicky' option and fix the resulting warnings about
dangling references.
|
|
|
|
|
|
| |
Create a VS_SHADER_TYPE source file property.
Inspired-by: Gilles Khouzam <gillesk@microsoft.com>
|
|
|
|
|
|
|
|
|
| |
Create a VS_DEPLOYMENT_CONTENT source file property, supporting
generator expressions, to compute whether a source file should be marked
as DeploymentContent or ExcludedFromBuild in Windows Phone and Windows
Store projects.
Inspired-by: Minmin Gong <minmin.gong@gmail.com>
|
|
|
|
|
|
| |
Document the COMPILE_DEFINITIONS_<Config> properties as deprecated.
Add new sections for deprecated properties and move POST_INSTALL_SCRIPT
and PRE_INSTALL_SCRIPT there as well.
|
|
|
|
|
|
|
|
|
| |
Add source file properties to control Xcode file type attributes:
XCODE_EXPLICIT_FILE_TYPE => explicitFileType
XCODE_LAST_KNOWN_FILE_TYPE => lastKnownFileType
Add a RunCMake.XcodeProject test to verify generated project content.
|
| |
|
|
|
|
|
| |
This replaces the need to invoke qt4_add_resources by allowing
adding the source .qrc file directly to the target sources.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The source files are already processed by cmQtAutomoc to look for
moc includes, so extend that to also look for ui_ includes and
find corresponding .ui files to process.
This replaces the need to invoke qt4_wrap_ui().
As the ui files are not likely to be part of the SOURCES of the
target, store the options associated with them separately in the
cmMakefile for querying during the autogen run.
|
|
|
|
|
|
|
| |
The COMPILE_DEFINITIONS escaping disclaimer was represented in builtin
documentation using a preprocessor macro. Factor the duplicate content
out into a separate .txt file and include it in each document with the
reStructuredText include directive.
|
|
Run the convert-help.bash script to convert documentation:
./convert-help.bash "/path/to/CMake-build/bin"
Then remove it.
|