[CMake] rules for writing cmake modules

[William A. Hoffman]

See the file Modules/readme.txt for the current documentation on
modules.

http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/readme.txt?rev=1.5&root=CMake&view=auto

-Bill

At 02:48 PM 1/1/2006, Alexander Neundorf wrote:
>Hi, 
> 
>I think it would be a good idea if the cmake wiki would contain a page  
>with rules how a good cmake module file should behave. 
>Like: 
> 
>If you write a FindLibFOO.cmake, then the following variables should be 
>defined: 
>FOO_FOUND 
>FOO_INCLUDE_DIR 
>FOO_LIBRARY 
>FOO_LINK_DIR (?) 
> 
>Should it print some status messages on success/failure ? 
>Should it MESSAGE(FATAL_ERROR "Foo not found") on failure ? 
>Should it use ADD_DEFINITIONS() or just SET(FOO_DEFINITIONS -Dwhatever) ? 
>Or more general, should it use commands, which affect the build or should 
>it just set variables which can then be used from the outside ? 
> 
>What do you think ? 
>How should a good cmake module work ? 
> 
>Bye 
>Alex 
> 
>
>-- 
>Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
>Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
>_______________________________________________
>CMake mailing list
>CMake at cmake.org
>http://www.cmake.org/mailman/listinfo/cmake