Brad King ca39c5cdd1 Optionally allow IMPORTED targets to be globally visible
Consider the case motivating commit e01cce28 (Allow add_dependencies()
on imported targets, 2010-11-19).  An imported target references a file
generated at build time by a custom target on which it depends.  Had the
file been built directly using add_library or add_executable its target
name would have been visible globally.  Therefore the imported target
representing the file should be globally visible also.

Teach the IMPORTED signature of add_(executable|library) to accept a new
"GLOBAL" option to make the imported target visible globally.
2012-01-25 14:42:31 -05:00
..
2012-01-25 00:05:06 -05:00
2011-12-16 10:15:39 -05:00
2011-10-23 22:15:30 +02:00
2011-08-25 15:40:49 -04: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
2011-10-23 22:18:08 +02:00
2010-11-12 10:47:28 -05:00
2011-10-23 22:15:30 +02:00