On Tue, Aug 10, 2010 at 5:39 PM, Brad King wrote: > On 08/10/2010 05:14 PM, Alexander Neundorf wrote: >> I think it is still true for most find-modules, I think there are only a few >> exceptions, mostly Boost and Subversion. >> Checking... ok, also PostgreSQL, LibArchive (they are both new, right ?), >> ImageMagick and Java set the exact-case _FOUND variables. >> All others (more then 100 ?) use the UPPERCASE_FOUND. >> >> No matter which version I personally like better, I really do think that the >> big majority uses UPPERCASE_CASE found, and now declaring that >> ExactCase_FOUND is the standard would be wrong. > > I think the subversion patch in question is a step backwards. > Somehow we need to move toward the Right Thing. At least the > documented FOO_FOUND variable should match the case of the > rest of the Foo_XXX variables in the same module. This is why > I think the fphsa should just set both, or that each module > should translate the result to match its documentation.
This issue goes way back... I remember trying to find consensus about it on the list and stating that we needed to clarify this and other issues about the FindXXX modules (maybe select a few "good written" examples, etc.), but backwards compatibility will always render many of the modules (independent of which direction we settle on) "wrong". So, what I have done is I set them both and document the ExactCase_FOUND one... --Miguel _______________________________________________ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
