diff options
| author | Brad King <brad.king@kitware.com> | 2013-01-07 16:31:52 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2013-01-07 16:42:53 (GMT) |
| commit | b684b395812872184cbf10e0e0513e2a18546047 (patch) | |
| tree | 4d0ed6480e46a2577e0e2b91085991f36c53da38 /Tests/Tutorial/Step6/MathFunctions | |
| parent | c7550d5ef12d8185fad93d581ebd52474ae3d1b0 (diff) | |
| download | CMake-b684b395812872184cbf10e0e0513e2a18546047.zip CMake-b684b395812872184cbf10e0e0513e2a18546047.tar.gz CMake-b684b395812872184cbf10e0e0513e2a18546047.tar.bz2 | |
VS11: Simplify external object file handling (#13831)
Since commit 9a6ff950 (Fix for bug where VS2010 did not use .obj files as
part of the build, 2011-04-01) and commit b291d9e7 (VS10: Fix external
objects generated outside target, 2012-03-19) we try to detect whether an
external object file is also a custom command output in the same target.
This is because VS10 includes .obj custom command outputs on the link line
by default.
VS 11 supports a "<LinkObjects ...>false</LinkObjects>" setting in custom
command rules to tell VS not to link the outputs. From the VS help:
Specify whether the Inputs and output files with specific extensions (.obj,
.lib, .res, .rsc) are passed to the linker.
Treat all external object files the same and add "<Object>" settings for them.
Diffstat (limited to 'Tests/Tutorial/Step6/MathFunctions')
0 files changed, 0 insertions, 0 deletions