Brad King wrote: > On 03/22/2013 07:14 AM, Stephen Kelly wrote: >> Would it be reasonable to issue an error at install(EXPORT)-time if the >> INTERFACE_INCLUDE_DIRECTORIES of a target contains paths in the source >> dir or binary dir, if the install prefix is not inside one of those >> itself? > > Yes, though it won't be able to work for all cases because some paths > may have generator expressions which won't be evaluated until the > consumer loads them.
Yes, exactly. > >> Also, in cmTarget::GetIncludeDirectories, if a path in a >> INTERFACE_INCLUDE_DIRECTORIES entry of an IMPORTED dependent does not >> exist, that could be made an error too. This would sort of be showing the >> error in the wrong place though (to the person using the package, rather >> than the one creating it). > > We already have similar errors in the exported "targets" files for > things like missing library files. The wording says something about > possible missing or broken packages. Right, I'll see if I can do something similar over the next few days. Thanks, Steve. -- 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
