[cmake-developers] Making Config.cmake files safer

[David Cole]

On Sat, Nov 12, 2011 at 12:23 PM, Alexander Neundorf <neundorf at kde.org> wrote:
> On Saturday 12 November 2011, Alexander Neundorf wrote:
>> Hi,
>>
>> I added a branch CheckImportedFileExistenceInConfigDotCMakeFiles cmake
>> stage.
>
> This is the commit:
> http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=1b12babe0cef55a0d5531a9d0d453a15598eb467
>
> 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
>

I think it's a good idea, but I'm not 100% happy with the error message.

  "Imported file \\\"" << filename << "\\\" does not exist. Your
installation is broken"

is less helpful than I'd like to see...

How about something like:

  "File 'filename' for imported target 'targetname' does not exist.
Try re-installing 'projectname' or contact 'projectname's' developers
(or mailing list)"


Thx,
David