On Mon, Oct 1, 2012 at 3:39 PM, Alexander Neundorf wrote:
> On Monday 01 October 2012, Stephen Kelly wrote:
> > Hi,
> >
> > In commit 6f50a04cc1c4584472f850e06daad7ae20af45c4, a
> > CMAKE_FIND_PACKAGE_NAME variable was introduced, but not documented.
> > Sometimes it is deliberate to not document
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 pro
On Monday 01 October 2012, Stephen Kelly wrote:
> Hi,
>
> In commit 6f50a04cc1c4584472f850e06daad7ae20af45c4, a
> CMAKE_FIND_PACKAGE_NAME variable was introduced, but not documented.
> Sometimes it is deliberate to not document things like that, but I thought
> I'd ask if it is.
Until now it is u
On 10/01/2012 03:27 PM, Stephen Kelly wrote:
> In commit 6f50a04cc1c4584472f850e06daad7ae20af45c4, a
For reference here is a link to the commit:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6f50a04c
> CMAKE_FIND_PACKAGE_NAME variable was introduced, but not documented.
> Sometimes it is
Hi,
In commit 6f50a04cc1c4584472f850e06daad7ae20af45c4, a
CMAKE_FIND_PACKAGE_NAME variable was introduced, but not documented.
Sometimes it is deliberate to not document things like that, but I thought
I'd ask if it is.
The same commit generates cmake code with uppercasing, but with empty en
Stephen Kelly wrote:
>
> This, from a Qt list, is probably of interest to CMake too.
>
I created a bug so the task is not lost:
http://public.kitware.com/Bug/view.php?id=13564
Thanks,
Steve.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13564
==
Reported By:Stephen Kelly
Assigned To:
