On Tuesday 19 February 2013, Brad King wrote:
> On 02/18/2013 08:23 AM, Brad King wrote:
> > Another approach is to just add an extra property to imported targets
> > that list their dependencies that are expected to be targets.  If when
> > following the link interface out of that target and a library name is
> > not a target, check the extra property on the very same target to see
> > if it should have been one.
> 
> Any comment on this idea?  It may be simpler to implement and produce
> better error messages.

I had the same idea, but went with the directory property first.
The target property would avoid any scope-issues, it looks quite elegant.

I haven't worked on the link-dependency-calculation much, so I wasn't sure how 
this code exactly works, so I went with the (for me) easier way, checking 
directly in FindTargetToUse().

Can you give me a pointer where the member of the link interface are checked ?

Alex
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers

Reply via email to