summaryrefslogtreecommitdiffstats
path: root/Tests/VSWinStorePhone/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* VS: Add genex support to VS_SHADER_FLAGSJeremiah van Oosten2021-01-051-2/+2
|
* Genex: $<CONFIG:> now supports multiple configurationsRobert Maynard2020-06-241-1/+1
| | | | | Instead of having to do $<OR:$<CONFIG:Release>,$<CONFIG:MinSizeRel>> you can do $<CONFIG:Release,MinSizeRel>
* VS: Test VS_SETTINGS and VS_SOURCE_SETTINGS_<tool> properties.Matt Davies2020-03-261-1/+6
|
* Tests: Teach VSWinStorePhone to verify the content of generated appx/msixVedran Vujinovic2019-09-241-1/+2
| | | | | | Add a test to verify the content of generated UWP app package - appx/msix. MSIX format was introduced Visual Studio 2017 version 15.9.0 and Windows SDK version 17763.
* VS: Fix WinRT component referencesGilles Khouzam2019-02-011-2/+3
| | | | | | | | | | | WinRT components need to be referenced in a similar way that managed code libraries are referenced. Validate that the library reference is a WinRT component and reference it through the project. Add test coverage for `VS_WINRT_COMPONENT`. While at it, fix the IOT reference failing on Win10 SDK 17763 which doesn't include it anymore. Fixes: #18846
* Tests: Fix VSWinStorePhone test with Windows 10 SDK 17763Gilles Khouzam2019-02-011-1/+5
| | | | The Windows 10 SDK no longer includes IOT.
* VS: Add VS_SHADER_OUTPUT_HEADER_FILE and VS_SHADER_VARIABLE_NAME properties.Kevin M. Godby2017-09-271-2/+4
| | | | | | | | | | 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>
* Merge topic 'vs-tool-override'Brad King2016-06-231-1/+5
|\ | | | | | | | | ed05f11d VS: Add a VS_TOOL_OVERRIDE source file property
| * VS: Add a VS_TOOL_OVERRIDE source file propertyGilles Khouzam2016-06-201-1/+5
| | | | | | | | | | | | | | | | 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.
* | VS: Add VS_SDK_REFERENCES target property to reference external SDKsGilles Khouzam2016-06-221-0/+3
|/ | | | | Allow one to specify external SDK references such as `Microsoft.AdMediatorWindows81, Version=1.0`.
* VS: Add support for Windows 10 Universal (Store) ApplicationsGilles Khouzam2015-10-051-2/+15
| | | | | | | | | | | | | | | | Teach the VS 2015 generator to support WindowsStore 10.0 applications. Add target properties to customize them: * VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION: Specifies the minimum version of the OS that the project can target. * VS_DESKTOP_EXTENSIONS_VERSION, VS_MOBILE_EXTENSIONS_VERSIONS, VS_IOT_EXTENSIONS_VERSION: Add a reference to the version of the SDK specified to the target allowing to target the extended functionality in a universal project. * VS_IOT_STARTUP_TASK: Specifies that the target should be built as an IOT continuous background task.
* VS: Add source file property to set extra hlsl shader flagsRobert Goulet2015-01-281-0/+2
| | | | | Create a VS_SHADER_FLAGS source file property so that we can set all other Visual Studio .hlsl shader file compilation flags.
* VS: Add source file property to specify Windows App deployment locationGilles Khouzam2014-12-031-1/+6
| | | | | | | | | | 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.
* VS: Add source file properties to set the hlsl shader entry point and modelCedric Perthuis2014-12-031-0/+6
| | | | | | 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.
* VS: Add test case for Windows Phone and Windows StoreGilles Khouzam2014-09-021-0/+114
Add tests to build for each version of each system when the corresponding tools are available.