summaryrefslogtreecommitdiffstats
path: root/CMakeLists.txt
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2009-09-07 14:12:18 (GMT)
committerBrad King <brad.king@kitware.com>2009-09-07 14:12:18 (GMT)
commit4e16813f63bae65dd3eeec0a326e9a4926aff1c5 (patch)
tree27eb0f6207480c3b6bccb335bcf4d1be0df2ceca /CMakeLists.txt
parent4224513ccee04d540e89db5cf1ca531b6ef8e0e5 (diff)
downloadCMake-4e16813f63bae65dd3eeec0a326e9a4926aff1c5.zip
CMake-4e16813f63bae65dd3eeec0a326e9a4926aff1c5.tar.gz
CMake-4e16813f63bae65dd3eeec0a326e9a4926aff1c5.tar.bz2
Put custom commands in topological order for VS 10
Visual Studio 10 uses MSBuild to drive the build. Custom commands appear in MSBuild files inside CustomBuild elements, which appear inside ItemGroup elements. The Outputs and AdditionalInputs elements of each CustomBuild element are evaluated according to timestamps on disk. MSBuild does not use inputs/outputs to order CustomBuild steps within a single ItemGroup or across multiple ItemGroup elements. Instead we must put only unrelated CustomBuild elements in a single ItemGroup and order the item groups from top to bottom using a topological order of the custom command dependency graph. This fixes CustomCommand and ExternalProject test failures, so we remove the expectation of these failures.
Diffstat (limited to 'CMakeLists.txt')
0 files changed, 0 insertions, 0 deletions