Brad King b684b39581 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.
2013-01-07 11:42:53 -05:00
..
2012-12-22 12:47:54 +01:00
2013-01-07 00:01:16 -05:00
2011-09-15 16:20:33 +02:00
2011-10-23 22:18:08 +02:00
2010-09-10 14:42:09 -04:00
2012-09-28 17:00:52 -04:00
2012-09-28 17:00:52 -04:00
2011-10-23 22:18:08 +02:00
2012-02-02 23:40:21 +00:00
2012-07-18 12:17:39 +02:00
2012-02-21 15:33:31 -05:00