Brad King wrote:
>> The same commit generates cmake code with uppercasing, but with empty
>> endif commands.
> 
> I think all target export file code is still generated upper case.
> 
>> I think I saw that cmake code generated by cmake remains uppercase in
>> case anyone using an older cmake is processing files generated by a newer
>> cmake. Does the same apply to populating the end* commands?
> 
> We've supported empty end*() and case-insensitive commands for so long
> this shouldn't be a problem in generated code.

Right, I didn't think it made much sense, but I don't know why I thought I'd 
seen it somewhere.

I guess the generated code is harder to lower-case in an automated way, but 
it seems a good candidate for a post-2.8.10 cleanup. There is not very much 
of it.

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

Reply via email to