diff options
| author | Brad King <brad.king@kitware.com> | 2014-06-10 15:33:19 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2014-09-29 20:05:53 (GMT) |
| commit | ef0fd4f0ced850edd049bb05b527c3bd234f441f (patch) | |
| tree | 366acc7b075f91b4cf3706f22f2b56f6e10923da /Tests/JavascriptCoverage/test3.js | |
| parent | d09b60f563902bd2197d88a3e83b119c09e62428 (diff) | |
| download | CMake-ef0fd4f0ced850edd049bb05b527c3bd234f441f.zip CMake-ef0fd4f0ced850edd049bb05b527c3bd234f441f.tar.gz CMake-ef0fd4f0ced850edd049bb05b527c3bd234f441f.tar.bz2 | |
VS: Teach vcxproj generation about the Tegra-Android platform
Complete the basic implementation of the VS Tegra-Android generators
by replacing parts of vcxproj files that are specific to MS tools
with settings defined for the NVIDIA Nsight Tegra tools.
Current limitations include:
* We have no "flag table" so flags will be passed in the additional
options fields instead of mapped to the vcxproj elements defined
by Nsight Tegra msbuild platform definition files.
* We have no interface to set the AndroidArch, AndroidStlType, or
AndroidTargetAPI fields so defaults will be used.
* The Nsight Tegra msbuild platform definition files do not provide
a working "Utility" target type so for add_custom_target we need
to use a "StaticLibrary" target type and leave out ClCompile rules.
* There is also no target type for plain command-line executables
so for add_executable we need to use a "DynamicLibrary" target.
Full application bundles will likely require new CMake target
properties (like WIN32_EXECUTABLE for Windows GUI executables).
Diffstat (limited to 'Tests/JavascriptCoverage/test3.js')
0 files changed, 0 insertions, 0 deletions