[CMake] how to modify scope of imported library

[Alexander Neundorf]

On Friday 09 March 2012, Petr Kmoch wrote:
> Hi,
> 
> I was solving a similar problem in our setup at work. The problem was
> that the parent couldn't know in advance which libraries will be
> imported by children. Conceptually speaking, I solved this by creating
> my own set of global properties which contain all necessary details
> about the libraries imported. These properties are appended to when a
> child imports a library, and then scanned once more in the parent and
> imported again:

I need to check, but I think with the upcoming 2.8.8 release there will be a 
new GLOBAL option for add_library(.. IMPORTED), to make the imported target 
globally visible.

Alex