On Saturday 11 April 2009, Richard Quirk wrote:
...
I'd just like to plug my lint script for CMake files at this point.
http://code.google.com/p/cmake-lint/
Among other things, it checks exactly the convention described above.
Running it on cmake/Modules/*.* results in 7826 bad practices,
On Wed, Apr 15, 2009 at 4:21 PM, Alexander Neundorf a.neundorf-w...@gmx.net
wrote:
On Saturday 11 April 2009, Richard Quirk wrote:
...
I'd just like to plug my lint script for CMake files at this point.
http://code.google.com/p/cmake-lint/
Among other things, it checks exactly the
On Friday 10 April 2009 2:59:11 pm Alexander Neundorf wrote:
On Friday 10 April 2009, Robert Dailey wrote:
I'm reading the guidelines for find package modules here:
http://www.cmake.org/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMakevi
ew =markup
No where in here do I see any mention
On Sat, Apr 11, 2009 at 1:36 PM, Daniel Nelson tor...@connect2.com wrote:
When you call find_package(), variables can be set inside the find script for
arguments such as QUIET or REQUIRED. For FindFoo.cmake, these variables would
be Foo_FIND_QUIETLY and Foo_FIND_REQUIRED respectively. I
On Friday 10 April 2009, Robert Dailey wrote:
I'm reading the guidelines for find package modules here:
http://www.cmake.org/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMakeview
=markup
No where in here do I see any mention of uppercase variable names. For
example, if my find package is:
I'm reading the guidelines for find package modules here:
http://www.cmake.org/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMakeview=markup
No where in here do I see any mention of uppercase variable names. For
example, if my find package is:
FindFoo.cmake
My return variables are:
